Right now I feel really smooth rom and great
- Just fix one of the following functions:
* Autofocus may not work
* GPS positioning is location but not orientation is
* NFC toggle each restart must take effect
- Hopefully this will fix the error soon thanks!
The newest build 11/21 is very good. I think it is best 4.4 ROm right now
Sent from my Optimus G using Tapatalk
Hey guys, i have a problem with clock cpu...In 11/21 and 11/20 the max freq stay in 1026MHz in all 4 cores....i try the smocha kernel 11/21 and 11/22 but no fix...the clock issues are ok to yours. I realy like omni rom...but this make me crazy
gaming lag
Hardtron said:
Hey guys, i have a problem with clock cpu...In 11/21 and 11/20 the max freq stay in 1026MHz in all 4 cores....i try the smocha kernel 11/21 and 11/22 but no fix...the clock issues are ok to yours. I realy like omni rom...but this make me crazy
Click to expand...
Click to collapse
when I ran MIUI rom game I play is very smooth asphalt 8, but when installing the rom omni 8 games very jerky asphalt desire to overcome
I'm using it on a regular basis and loving it.
Obs.: I own a E977, a variation of the E975 with different LTE freqs.
Omni was my first 4.4 ROM and I enjoyed it greatly, however, I've moved on to PSX as its updated more often, has a bit less bugs.
Hardtron said:
Hey guys, i have a problem with clock cpu...In 11/21 and 11/20 the max freq stay in 1026MHz in all 4 cores....i try the smocha kernel 11/21 and 11/22 but no fix...the clock issues are ok to yours. I realy like omni rom...but this make me crazy
Click to expand...
Click to collapse
Hey,
I notice your problem with google services like gps localization or google now installed, my e975 runs 10G vodafone's stock rom, when I turned off the gps localization and freezed (with titanium backup) G+, GBook, GPlay my battery life is became great, until two days with 3 hours of display. :laugh::laugh:
regards
Problems
1. DSP recognise my bluetooth headset as phone speaker
2. Camera doesn't use autofocus in normal mode(i must tap the display to get focus), in HDR mode sometimes focusing, sometimes not, I must tap the display in this mode too.
3. If I use HDR mode and exit the camera app and then go back the display is green and noisy.
using the omni-4.4.2-20140125-geehrc-HOMEMADE on my LG-E975 International,
everything is good, but noticed the below issue
1) The Home, Menu and Return buttons are always lighting up when screen is used.
on further reading found that kitkat version always lights up the hardware buttons....
hope this can be fixed to behave as previous versions
Related
Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?
Crimson Ghoul said:
Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?
Click to expand...
Click to collapse
I do not experience this issue. When you flashed the rom, did you do a clean install? Have you formatting the device?
Yup.. I format everything.. I use the touch recovery and just use every option that it provides and wipe everything.. It even does it when there is nothing installed. I usually delete almost all the useless system apps that I don't use like the google music app and all of the ones civato provides... I even change the animation settings to .5 in the developer section.. should I turn them off all together?
Crimson Ghoul said:
Yup.. I format everything.. I use the touch recovery and just use every option that it provides and wipe everything.. It even does it when there is nothing installed. I usually delete almost all the useless system apps that I don't use like the google music app and all of the ones civato provides... I even change the animation settings to .5 in the developer section.. should I turn them off all together?
Click to expand...
Click to collapse
The animations should not have anything to do with it. Does this only occur on that rom? Have you tried other roms and experienced that issue?
not many other roms out there.. I have used stock and his.. had the same issue on both.. Also happens on my brother's a500.. it usually happens when unlocking and going into any app.. it sits there for a few seconds and then opens whatever it is i opened
Crimson Ghoul said:
not many other roms out there.. I have used stock and his.. had the same issue on both.. Also happens on my brother's a500.. it usually happens when unlocking and going into any app.. it sits there for a few seconds and then opens whatever it is i opened
Click to expand...
Click to collapse
This is starting to sound like a hardware issue. Before that is concluded, you could:
- Make sure the governor is not set to "conservative"
- Try a clean install of CM9
If the problem still arises, its most likely a hardware issue.
I'm using the OC kernel and have it to 1500.. I also always leave it on performance.. I figure it would kill my battery life but I don't use it much.. and i tried cm9 also.. too many issues as of right now
Crimson Ghoul said:
I'm using the OC kernel and have it to 1500.. I also always leave it on performance.. I figure it would kill my battery life but I don't use it much.. and i tried cm9 also.. too many issues as of right now
Click to expand...
Click to collapse
It doesn't seem it can be anything else but a hardware issue in that case.
NB. Overclocking to a high frequency can cause instability and bring about that issue (but since you experienced it on the stock rom, its quite likely not to be that).
the overclocking helps to speed it up a tad bit.. for the most part it just lags.. i did a clean install just now
Thought I would jump in. Stock ics would slow down and lag on me, jittery transitions poor performance in games or movies, but it took an hour not a few minutes. However testing the T20 kernel before the release kernel had that exact issue, bogging and lagging within minutes.
His release kernel doesnt do it, and flex extreme as well as my cm9 builds don't, even with T20 kernel. Consider flashing that kernel to see what happens.
Side note...what issues did you have with cm9? And what release? My build 1 has been running for 3 days no reboots stable as can be undervolted and OC when needed. Something to maybe think to try to see if it persists. T20 kernel works fine with it too.
Tapatalked from my Galaxy S II.
Crimson Ghoul said:
Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?
Click to expand...
Click to collapse
Yup, EVERYTIME I turned on my screen then unlocked it to laggggggg for a lil while. I'm now using CM9 n that issues gone. Try CM9
forum.xda-developers.com/showthread.php?t=1705554
A100 Running CM9 Nightly ROM n ezT20 OC Kernel :-D
To prevent the lagg after unlock, I set the governor to ondemand and the minimum frequency to 312.
eww245 said:
To prevent the lagg after unlock, I set the governor to ondemand and the minimum frequency to 312.
Click to expand...
Click to collapse
That reminds me...setting a screen off profile with the same min/Max speed can cause issues with that, give Max a notch or two higher. And don't have it change the governor leave it the same. So like interactive screen on Myst nit be conservative screen off, doesn't work that way.
Tapatalked from my Galaxy S II.
I had the same issue on stock. I noticed there are 2 weather applications installed (version 1 and version 2) immediately after I disabled the old weather application (version 1) this stopped happening. I used the ICS GUI to do the disable.
This might not be the case in custom rom, but is true for stock. Post reply and let me know if this fixed it for you also.
Crimson Ghoul said:
Does any one else's a100 become super laggy after a few minutes of being on.. I am running the latest flex reaper I even overclock it all the way but I get this huge lag after the first few minutes of being on.. anyone else experience this or have a fix for this?
Click to expand...
Click to collapse
Do you have a micro SD card plugged in? Try reformatting the card with a computer. Worked for me.
Sent from my A100 using XDA
I felt the need to add my two cents in this....this has been happening to me for the longest with the flex reaper rom ONLY. I've used stock and ZN's rom and those did not lag after unlock...only flex reaper. I'm currently using flex reaper and still experience it from time to time but doesn't destroy my day at all...
Give the CM9 nightly ROM's a go. No Bluetooth n no HDMI audio, but everything else is fine n damn smooth. Those issues will be fixed though
A100 Running CM9 Nightly ROM n ezT20 OC Kernel :-D
eww245 said:
To prevent the lagg after unlock, I set the governor to ondemand and the minimum frequency to 312.
Click to expand...
Click to collapse
I installed Flex 100 Reaper with stock and it it seemed to run smooth enough. Then I installed the OC kernal, and started to get lag. I was looking around to find the OC settings, but can't see it anywhere in settings..
Can anyone direct me to where can I adjust the governor/max/min CPU settings?
Sorry for the noob question.
htc_softbank said:
I installed Flex 100 Reaper with the OC kernal, and started to get lag. I was looking around to find the OC settings, but can't see it anywhere in settings..
Can anyone direct me to where can I adjust the governor/max/min CPU settings?
Sorry for the noob question.
Click to expand...
Click to collapse
Setcpu from the play store.
The overclock settings are not integrated like CM.
Hi,
I've got a Tegra One X running SlimBean 4.2.2 WEEKLY 5.7 and n3okernel.
So far so good but there are still some things I'm not really sure about.
First there's something very annoying compared to other phones and even to Sense One X's.
From pressing the lock button to the screen coming on it takes about 1-2 seconds (which is still quite slow but acceptable to me), but sometimes the phone just takes a little bit longer. Sometimes it takes up to 20 seconds (haven't stopped it but it's my impression).
Does anyone have an idea why this could be? Is it possible to disable the fade on animation? I don't need it. I'd rather have the screen just coming on.
And otherwise I've been playing around with Pimp My Rom Beta from the Play Store and fiddled around with some settings and the results seemed quite good to me. Can someone tell me if it's recommended to turn these settings on:
Hardware acceleration (Pimp My Kernel - Android Features)
Lock Launcher In Memory (Pimp My Kernel - Android Features)
Call Ring Delay 0 (Pimp My Kernel - Telephony)
Proximity Sensor Delay 0 (Pimp My Kernel - Telephony)
AMR Wideband (Pimp My Kernel - Telephony)
Optimize sqlite3 Databases (Pimp My Kernel - Miscellaneous)
Ext4 File-Systems Tweaks (Pimp My Kernel - Miscellaneous)
Internal SD-Card I/O Tweaks (Pimp My Kernel - Miscellaneous)
Zipalign all APKs at each boot (Pimp My Kernel - Miscellaneous)
Battery savings (Pimp My Kernel - Miscellaneous)
Quick Power-On (Pimp My Kernel - Miscellaneous)
Adjust GPS config to my country
Wifi Scan Interval 180 (System Tweaks - Internet)
It doesn't have anything to do with speed but I discovered that my battery drains quite fast if I have mobile data enabled. If I disable it there's nearly any drain.
Is this normal and is there a way to make the drain a bit less extreme?
Thanks in advance!
land.apfel
Change kernel would probably fix screen on delay
Sent from my HTC One X using xda app-developers app
This is the reason why I've chosen n3okernel. It seems to be better now but still not completely cured.
Which one would you recommend?
I've got the same problem on my Nexus 7 also.
I've flashed Faux there.
land.apfel
Oh boy, where to even start. First it's a known issue with higher end mobile processor's (like tegra 3) that fstrim is not correctly adjusted. To take care of that go to play store and download lagfix and run it, you'll probably notice an immediate difference. I would also download cache mate, clean master (has a broom icon) and also clean master pro (has a little ying/yang icon). Download all 4 of those apps and run them all and you should notice a huge difference. If your SD card space is getting low, that can also slow down your phone. Again, I would go to the playstor and download SD maid and use that to clan up your SD card. This should all make a huge difference. Like I said though I would start with the lagfix app.
I tried lag fix but it made everything worse I suppose.
So I didn't try the other tools.
My SD still has some gigabytes of space so this shouldn't be a problem.
My main problem really is the slow unlocking at the moment.
And the battery drains pretty fast too, but unlocking is really what's annoying me at the moment.
Thanks anyway!
land.apfel
You gotta remember too, the Rom your running is basically a constant beta if you're using weeklies, these issues may pop up. Might wanna try a different Rom and see if it persists.
from my Viped out one x
A few apps could help alot
Download greenify, and seeder
< Coming to you live from the planet One X >
I was running the official build 5 until yesterday but then I thought I should maybe try a newer build. Maybe it's better.
As Build 6 came out today, I've upgraded to this one.
Does Seeder really help?
I've read that it does not help at all because entropy is not really needed so often.
Is there no simple solution for faster unlocking?
land.apfel
Hi everyone. Is the heat persist for everyone. Mine in average 65 degree centigrade and going to Max 73 degree centigrade (through cputemp in status bar xposed module). I'm using telsa rom latest build (based on CM11 R17). I have also tried many custom roms and kernels, mods, underclock but same heating problem. Is there anything I'm missing out. Is there anything really working heat problem solution .
Please help let me know any information to be provided further.
try latest carbon rom... mine doesn't go above 38 deg, 45 deg n 60 deg while idle, while using phone n while playing games resp...
Try Latest Carbon or CM11.
I didn't noticed any heating issues in the latest CM11 builds!
I believe that the price of the phone tells us we should NOT have great expectations.Still,it turned out to be an amazing phone,with a great camera,good performance,no major issues(trust me,i owned an xperia L.that phone has obvious issues and Sony does nothing to fix them.I would sue them if I could for selling that on the market).The heating problem can't be avoided.I'm using latest CM11 and I use mostly balanced profile(1401 mHz top frequncy),and when using the phone to send texts,a little browsing,calls and so on it doesn't get heated up,or it gets a little warmer if you watch youtube videos for example,but when I play games,that's a whole new story.It is obviously that the phone is very hot,way above average.And that's it,we have to deal with it.We can't do anything,that's how the phone was build,the materials they used and so on.On stock the phone has some thermal engine control,if the phone got too hot it dropped the CPU frequency.Now on CM11,there's nothing similar,so we have to be careful to not let it stay hot as hell for too long,it might burn the CPU.I will ask the rom developer about this concern.Hope I helped you.All the best !
The best solution for "Heating Problem And Faster Battery Draining":
1)Flash latest Carbon Rom RC6 4.4.4 (it has its own kernel which is very much optimized and has some more governers)
2)After flashing Carbon Rom click go to settings>about phone> click build number 5 to 6 times to activate Developer options and Performance menu.
3)In performance menu Set maximum speed to 998 Mhz and minimum to 300 Mhz, Set the Governer to "conservative" and I/O Scheduler to "cfq".(If you play games alot then set max frequency to 1190)
4)Install Xposed framework
5)Install Greenify app, now activate its module in Xposed Framwork.
6)Add all applications to greenify list and greenify them. Set the Working mode to Boost. Also check auto hibernation mode.
7)Also create a hibernate now shortcut to homescreen to greenify apps frequently when you dont use them.
Now your phone will never heat and it will increase your battery by 50%
Enjoy
cm11
try cm 11 with xcelerate kernel for better batt and heat control
Kernel
FOR STOCK BASED ROMS ONLY
features :
- kexec-hardboot(multirom support)
- CPU governor - smartmax
- other stuff which I don't remember
SmokeKernel+ProfilesApp+LiveDisplayApp(new updates always will be here)
Performance profiles App
Description :
Power profiles for Smoke kernel
The monitoring window is closed by double-tapping on it
Requirements:
Root access
Necessary actions for the full work of the performace profiles application in android 4.4
1) add app to autostart
2) allow the application to display pop-ups
3) Delete the file power_mode.sh, which lies on the path /bin/
LiveDisplay App
Description :
The application allows you to change the color temperature of the screen
at 8:00 a daily value is set
at 20:00 the night value is set
Requirements:
Root access
Instruction:
1) Install zip via recovery
2) Install Performance profiles and LiveDisplay apps
Changelog:
30.05.2017
31.05.2017
03.06.2017
11.06.2017
16.06.2017
18.06.2017
23.06.2017
06.07.2017
10.05.2018
XDA:DevDB Information
Smoke, Kernel for the Xiaomi Mi Pad
Contributors
Artemka2008, DbIm4pda
Kernel Special Features: Custom performance profiles App, custom powerHAL
Version Information
Status: Testing
Current Stable Version: 1.3.4.1
Stable Release Date: 2017-07-06
Created 2017-05-26
Last Updated 2017-07-06
reserved
Will work on Lineage OS 14? (Oops: didn't see "boot.img for LineageOS14.1(7.1.2)")
Update 1: Works on Lineage OS 14. Testing to see if battery is better on this kernel and performance profile app (only browsing, no gaming)
Coule you make a flashable .ZIP please?
vickdu31 said:
Coule you make a flashable .ZIP please?
Click to expand...
Click to collapse
I'm lazy. I have already completely described the installation. May be later
Thank you for effort. Could anybody compare with F1xy kernel?
Thanku @Artemka2008 and @Dblm4pda
.
.
.
.
Btw Anyone tried antutu with this kernel ?
So far, so good.
I did not yet install the custom powerhal or whatnot. What does it even do?
FYI: You have to reroot the tablet after installing this boot.img.
Anyway, of the performance profiles the high is the only useful if one watches youtube. All other profiles results in occasional jerk/lag in the video.
Deep sleep battery consumption so far has been minimal for me. Usage battery consumption might be a tad higher, at least with the high profile, which is the only useful one unfortunately.
This kernel like f1xy and Foxy all suffer from the same wifi problem that when you wake the tablet from deep sleep and wifi is turned off (wifi option Keep awake: never), it takes 30+ secs for the wifi to activate and reconnect. You can't even enable the wifi by yourself during this time, you basically have to just wait...
I haven't run any antutu etc test cos I don't care what the numbers say. All I care is how it works and feels and how the battery lasts.
I'll keep testing.
I am running LOS14 with the new blobs. Which reminds me, I think I get more of the graphical glitches now than I did before. But this all too subjective atm. to say conclusively if it is the kernel or not.
Tautologica said:
So far, so good.
I did not yet install the custom powerhal or whatnot. What does it even do?
FYI: You have to reroot the tablet after installing this boot.img.
Anyway, of the performance profiles the high is the only useful if one watches youtube. All other profiles results in occasional jerk/lag in the video.
Deep sleep battery consumption so far has been minimal for me. Usage battery consumption might be a tad higher, at least with the high profile, which is the only useful one unfortunately.
This kernel like f1xy and Foxy all suffer from the same wifi problem that when you wake the tablet from deep sleep and wifi is turned off (wifi option Keep awake: never), it takes 30+ secs for the wifi to activate and reconnect. You can't even enable the wifi by yourself during this time, you basically have to just wait...
I haven't run any antutu etc test cos I don't care what the numbers say. All I care is how it works and feels and how the battery lasts.
I'll keep testing.
I am running LOS14 with the new blobs. Which reminds me, I think I get more of the graphical glitches now than I did before. But this all too subjective atm. to say conclusively if it is the kernel or not.
Click to expand...
Click to collapse
Problems with wi-fi are not due to kernels, these are the problems of the system
Artemka2008 said:
Problems with wi-fi are not due to kernels, these are the problems of the system
Click to expand...
Click to collapse
I am not sure what you mean by "system" in this context.
The particular wifi issue I mentioned above does not happen with a stock kernel, only with custom kernels. And it is the only wifi issue I have encountered. No breaking off, nothing else, just a slow reconnection after deep sleep. But if it is a necessary evil while changing the kernel, so be it cos with stock kernel I have much bigger problems and I rather use a custom kernel to get more fluidity of use.
Spassiba for the kernel komrad!
does this kernel support vulkan API?
I ran into a same kind of issue I have with stock kernel; After waking from deep sleep the mipad is usually slow as hell for a minute or 2. Like everything is lagging. A bit like a cold engine which is warming up.
Anyway, I moved back to F1xy cos of this which doesn't suffer from the same issue.
Does this kernel support MIUI?
Richard20000321 said:
Does this kernel support MIUI?
Click to expand...
Click to collapse
all miuis run on Android 4.4.4, do you really think this kernel can run on Android 4.4.4?it only works on Android 7.1.2
---------- Post added at 08:11 AM ---------- Previous post was at 08:08 AM ----------
Richard20000321 said:
Does this kernel support MIUI?
Click to expand...
Click to collapse
there's a "miui smoke rom"using this kernel, maybe you can try that rom, it's also using this kernel
Update
cameras works now
Artemka2008 said:
Update
cameras works now
Click to expand...
Click to collapse
Does this mean camera will work on ROM with new blobs?
maccafan said:
Does this mean camera will work on ROM with new blobs?
Click to expand...
Click to collapse
It's not a kernel problem
maccafan said:
Does this mean camera will work on ROM with new blobs?
Click to expand...
Click to collapse
No
Please make it a flashable zip... Cheers...
Update
Update for performance profiles application
Changelog:
- application was rewritten with Kotlin
- added current RAM freq displaying
- increased low power mode performance
You do not need to reflash the kernel(if u use SmokeKernel), just update the application
This morning my Pixel C felt slow and sluggish.
Rebooted and removed recently installed apps but no difference.
Installed a CPU monitoring app and see that the CPU stays at 204Mhz even under load.
Any ideas before I try a full wipe?
Full reset seems to have fixed though notice cpu maxes at 1326
This right?
I'm not sure most CPU monitors know what to do with the X1, I know CPU-Z doesn't recognize it beyond a general "Nvidia Tegra" chip. What app are you using?
I switched from AOSP for acbit but yesterday had the same issue. Tablet felt slow and sluggish.
CPU monitor app showed CPU not scaling.
Went back to stock Oreo and still "feels" slow.
Geekbench4 says single core 926 and multi 2561
This is wrong?
My Pixel C performance is strange still the OREO update. I know this going to sound weird but when in splitscreen, the app on the left in landscape or on the top in portrait is lagging a lot. Scrolling, page swiping, etc.. takes a distinct longer time than expected. The app in the other half of the screen is acting normally.
Could this be related to the same issue?
With the pixel C now discontinued, Google is unlikely to fix a bug, especially if nobody reports it.. Bit of a worry, what to do?
I'm facing this issue as well. Already wiped cache and did factory reset, with no results.
It's now a very fancy digital picture frame.
There is no such problem. I used the first available monitoring program (cpufloat) and the CPU frequency change is shown adequately.
https://play.google.com/store/apps/details?id=com.waterdaaan.cpufloat
Vartom said:
There is no such problem. I used the first available monitoring program (cpufloat) and the CPU frequency change is shown adequately.
https://play.google.com/store/apps/details?id=com.waterdaaan.cpufloat
Click to expand...
Click to collapse
Thanks - in that case, the issue is less obvious to spot but I have definitely noted a lag in split screen mode refreshing the app on the left (yes, I know how strange it sounds..).
In addition, there have been quite a few report of the new January patch release affecting Pixel (phones) users. I can't help thinking our Pixel C issue with the last update and these new issues are too much of a coincidence..
I am hoping Jan patch might fix my Pixel C issue...
L
laurentbon said:
Thanks - in that case, the issue is less obvious to spot but I have definitely noted a lag in split screen mode refreshing the app on the left (yes, I know how strange it sounds..).
In addition, there have been quite a few report of the new January patch release affecting Pixel (phones) users. I can't help thinking our Pixel C issue with the last update and these new issues are too much of a coincidence..
I am hoping Jan patch might fix my Pixel C issue...
L
Click to expand...
Click to collapse
At the moment I'm using the kernel I've modified, and I have no problem with scrolling on the left side of the screen in split screen mode.
you can try it.
Install Kernel Auditor and deselect CPU Multi-core power saving option in CPU tab, that was on for some reason.
MrPhilo said:
Install Kernel Auditor and deselect CPU Multi-core power saving option in CPU tab, that was on for some reason.
Click to expand...
Click to collapse
For what? if the frequency control and so works normally
Just updated January-ota and nothing has been solved... What can we do to make google solve it. The bug with the navbar continues and the split-screen is impossible to use
I started a thread when I noticed this bugs
https://forum.xda-developers.com/pixel-c/help/bugs-android-8-1-t3718156
AlfreGarcia98 said:
Just updated January-ota and nothing has been solved... What can we do to make google solve it. The bug with the navbar continues and the split-screen is impossible to use
I started a thread when I noticed this bugs
https://forum.xda-developers.com/pixel-c/help/bugs-android-8-1-t3718156
Click to expand...
Click to collapse
https://issuetracker.google.com/issues?q=componentid:190923+ Click "Create Issue" Report the bugs in detail how to replicate etc Someone from the dev team should get back to you
liam_davenport said:
https://issuetracker.google.com/issues?q=componentid:190923+ Click "Create Issue" Report the bugs in detail how to replicate etc Someone from the dev team should get back to you
Click to expand...
Click to collapse
I dont know why, but the blue buttons are unclickable for me, so I cant create the issue.
Bringing back from dead.
So if you use Kernel Auditor to turn off some of the cores when this is occurring, the clock speed goes up for the primary core. It's as if they set a total limit, then divide by total core count. When battery charge is above 67%, you get the full max speed. No reboot or anything, just charge it up and you unlock the speed again. I suspect the Oreo kernels have bad throttling algorithm for this CPU.
My Pixel C was lagging quite bad when the battery fell below 67% using stock 8.1 (locked bootloader, everything untouched). I tried reflashing the factory images, but the problem stuck around. I rooted (magisk 18.1) and installed Kernel Adiutor. The problem was obvious, the CPU would heavily throttle (under 67% battery) depending on the amount of core active (with 4 cores, they would all run at ~200 mhz, with 2 cores, about 700 mhz and with 1 core about 1100 mhz). It wasn't so terribly laggy with 1 core running at 1100 mhz, but it was still pretty slow.
To try and troubleshoot the problem I then installed LineageOS 15.1 and followmsi's kernel (https://forum.xda-developers.com/pi...p-flashable-monthly-update-zip-pixel-t3375591). To my surprise the problem remained, despite the custom ROM and custom kernel. I think there is something wrong with the 8.1 oreo kernel and the Pixel C (see google forum post here: https://productforums.google.com/forum/#!msg/nexus/x7izNIUIHeI/VO4n9l_DCAAJ ). So I tried a second solution. This time I did the following:
1. Flashed TWRP: twrp-3.2.3-0-dragon.img
2. Flashed in TWRP: Followmsi's unoffical lineageOS 16.0: lineage-16.0-20190206-UNOFFICIAL-dragon.zip
3. Flashed in TWRP: (same session, before booting into LineageOS): OpenGAPPS Arm64 Pico package: open_gapps-arm64-9.0-pico-20190302.zip (m
4. Flashed in TWRP: (same session, before booting into LineageOS): Followmsi's Android 9 custom kernel: tegra-3.18_kernel_pie_dragon_v190205_unicorn-xceed-followmsi.zip
And voila, back to full speed. In fact the tablet seems to run better than ever. After some testing I installed Magisk 18.1 (for root and to pass safetynet), and everything is running great. The CPU's now appear to be managed properly by the 9.0 kernel. I'd recommend anyone experiencing this problem to go ahead with what I outlined above. Alternatively, if you're not comfortable with custom roms, you can install the last Android 7.1 build (ryu-n2g48c-factory-0bc0ee15.zip - guide here: https://mmikowski.github.io/pixelc-revert-nougat/).
Hope this helps.