Develop Bugs

[Discontinued][ROM][4.2.2][G Pro] ColorOS 2.0 Based on CM10.1 [F240x/F220K/E980/E988]

ColorOS 2.0 for G Pro by WS008​
Based on CM10.1 (4.2.2) and ColorOS Patchrom​
Please take note that although this ROM is based on CM10.1, it is not merely a modification to the CyanogenMod. It uses a similar method to MIUI in building the ROM. You will get a ColorOS experience instead of a CM one by flashing it.
About ColorOS
ColorOS is a firmware based on Android with intensive modifications. It was created by Oppo and originally ran only on Oppo devices such as the Oppo Find 7. In 2014, Oppo started its Patchrom Open Source Project and allowed the ROM to be ported to other Android devices.
The ROM is ported by the Chinese developer WS008. The development of the ROM has stopped (for a long time...)
Features
ColorOS features
Added SmartMax to the kernel.
Zipaligned.
Rooted, SuperSU.
Smooth as CM10.1.
Improved battery life.
Double tap to wake.
Slide to wake.
Included Aroma Installer. You may choose which variant you have and whether you want GApps when flashing.
Screenshots
How to install
Install custom recovery (PhilZ Touch recovery recommended) (There are issues with TWRP.)
Wipe Data/Cache/System (Important)
Flash zip -> Select Your variant -> Select GApps
Downloads
From ColorOS official server.
Known Issues
NFC not working.
FAQs
1. Why 4.2.2?
The ColorOS Patchrom currently only supports Android 4.2.2. The update can only made by Oppo. We will try to update to KitKat as quickly as we can once Oppo releases the KitKat update to the Patchrom.
2. Why Chinese?
The ROM is in Chinese by default (Sorry, we cannot change it unless Oppo does something.) You may switch to English in Settings (设置).
If you like this ROM, please click the "Thanks" button. We will also appreciate a lot if you connect to the Internet at least once after flashing for statistical purposes.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Thank you very much @JTJTJ.
Eventhough you are not the developer, but your action helps us very much as we do not have that great assortment of roms.
Cheers.

TNX :good:
For some reason i couldn't connect to my WiFi network. Also i was able to choose Hebrew language but the interface changed to English.

olorin said:
TNX :good:
For some reason i couldn't connect to my WiFi network. Also i was able to choose Hebrew language but the interface changed to English.
Click to expand...
Click to collapse
Which variant are you using? I will feedback to the developer and see what we can do.

g0at1 said:
Thank you very much @JTJTJ.
Eventhough you are not the developer, but your action helps us very much as we do not have that great assortment of roms.
Cheers.
Click to expand...
Click to collapse
More than happy to bring ROMs here

Did you know is is Possible change the 4G icon to LTE i on T-Mobile
any help?
Sent from my LG-E980 using Tapatalk

We need to at base 4.1.2 in order to flash this rom right bro?

going to try just backed up dho commtio 4.4.3 and flashed cmw

Not working on F220K
Sorry, but i've tried to install it several times on F220K, the installation process completes well and then it does'nt boot, then i tried F240k variant and it installed and booted well, but it had some graphics glitches on F220k, any help would be appriciated,

It doesn't boot on my phone
Flashed the E988 variant

ROM installed fine but everything is in Chinese. Color OS looks beautiful. I wish they added more steps in English for initial set up. This thread will be hard to maintain in English unless we are able to install in English.

pramod1969 said:
ROM installed fine but everything is in Chinese. Color OS looks beautiful. I wish they added more steps in English for initial set up. This thread will be hard to maintain in English unless we are able to install in English.
Click to expand...
Click to collapse
Can i happen to ask what rom where you on when you flashed this rom? I tried installing this and MIUI on kitkat but it won't boot past lg logo after installation. Were you able to test he battery life?

blitzkriegger said:
Can i happen to ask what rom where you on when you flashed this rom? I tried installing this and MIUI on kitkat but it won't boot past lg logo after installation. Were you able to test he battery life?
Click to expand...
Click to collapse
Any update with this Rom? I am very interesting to install. But I need NFC too

fariznur said:
Any update with this Rom? I am very interesting to install. But I need NFC too
Click to expand...
Click to collapse
I have just installed the rom. It works pretty well. NFC seems to work (didn't try with another phone though).
You can flash it with CWM in Freegee.
There is a tutorial to get english on Youtube:
Thanks to let us try ColorOs

UPDATE: It's not too bad, I'm not 100% sure what the OTA does but I'm on the 06/16 build. I'll try and see if I can get the double-tap wake to work in a bit. Just seeing if I can change the Chinese keyboard to an English one since installing Google Keyboard from the Playstore FC's. Overall: not bad at all.
EDIT: Forgot to mention, the speaker sounds noticeably better on here. I'm not sure what's different but the quality is great.

May I know how to disable NFC function? I click disable but it still keeping enable. Is it a bug?

So, I tried this before, and I loved the features. I couldnt however get wifi and stuff to work. I want to try it again, but the zip wont download correctly :/ It is "invalid"
EDIT: If anyone has the same problem, download and use DAp. It downloaded it without making it invalid, lol.
'

Anyone else have problems with getting stuck a LG logo upon first booting after install? I found that it can be fixed by copying 'wcd9310_mbhc.bin' and 'wcd9310_anc.bin' into '/system/etc/firmware/wcd9310/' (files available from here). I packed them into the ZIP, reinstalled, and am now having a colorful os.
The non-existence of those files causes this error upon install, though it wasn't reported by the installer--it claimed success!:
Code:
symlink: failed to symlink /system/etc/firmware/wcd9310/wcd9310_mbhc.bin to /data/misc/audio/mbhc.bin: No such file or directory
symlink: failed to symlink /system/etc/firmware/wcd9310/wcd9310_anc.bin to /data/misc/audio/wcd9310_anc.bin: No such file or directory
Which, I think, caused a nasty loop of '[CAM/E][ERR] ce1702_i2c_rxdata failed!' errors upon first boot, keeping me from advancing past that mocking LG logo.

[ROM] [6.0.x] Official CyanogenMod 13.0 Nightly Builds Oppo N3

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe system, data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Broken Features / Known Issues
- fingerprint sensor will likely never work in CM
- camera is less features than stock colorOS
- ?
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking or ask the same question over and over again.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Please also provide instructions to reproduce your issue.
Downloads
CyanogenMod 13.0 for Oppo N3: ROM @http://get.cm/?device=n3
Recovery Links
TWRP
Google apps addon:
Recommend GAPPS but there's plenty of options here.
XDA:DevDB Information
Cyanogenmod 13.0 Oppo N3, ROM for the Oppo N3
Contributors
jrior001
Source Code: https://github.com/cyanogenmod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Current Beta Version: Nightly
Created 2016-02-22
Last Updated 2016-03-01

Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!

SufiSam said:
Hey there bud. Great to know that there's still people out there working for the N3. This is a hopeless device, not even Lollipop support from Oppo despite being a flagship device once, so thanks a lot.
I'm currently on CM12.1 although the camera doesn't perform as well as on ColorOS and the fingerprint sensor doesn't work either, although pressing the button on the sensor does brightness up the screen and turn the capacitive buttons' light on when pressed.
Anyway, I'd love to try CM 13.0, but I'd want to know the major bugs on this release from you. Also, do let me know if I can be of any help. This is a beast of a device, let down by the abysmal software from Oppo. Will surely give it a shot if the bugs are bearable Thanks again for working on the N3!
Click to expand...
Click to collapse
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).

jrior001 said:
Fingerprint/camera are mostly the same issues from cm12.1. I have not attempted device encryption yet, and I doubt our available twrp build would be able to decrypt. Other than that this build is pretty much fully functional. I have had a few intermittent issues with audio and touchscreen wakeup but mid kernel rebase so that will all get cleaned up shortly. I've actually been running this for 2 months trying to get camera working (just fixed a few days ago).
Click to expand...
Click to collapse
Okay, great to hear. I've done my bit of research on the N3's fingerprint sensor and I'm not sure if it would be helpful in trying to fix it or not, but do let me know if you'd want to hear about it

good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.

How about the battery life? I am getting a worst battery life on CM 12.1
Sent from my m2 using Tapatalk

cheeze.keyk said:
good to see that the device still gets cm13. Thanks for your great work.
you can check also the source for Lenovo ZUK Z1 they have the same processor and it has FS too.
Click to expand...
Click to collapse
Both devices may have the same processor, but I doubt they use the same fingerprint sensor. The N3 uses the FPC1021, also used in the Gionee E8 and maybe the Lenovo Vibe X3 too. I wish we could somehow help OP in finding the sources/drivers for the FPC1021 fingerprint sensor

Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!

SufiSam said:
Okay, here's something very weird that happened yesterday. I started the camera by pressing the power button twice and the phone shut down by itself and then reboot. The phone was stuck in a bootloop. I could access TWRP, and I tried everything, right from factory resetting the phone to reflashing both, CM13 and CM12.1. Absolutely nothing helped, as the phone just couldn't go beyond the Oppo logo.
I had to install the stock Oppo recovery again in Fastboot mode, wipe the internal storage and reflash a boring ColorOS stock rom again. I'm still not sure what happened. 5 years of flashing experience and I've never known any simple system app function that could soft brick a phone so badly.
Looking forward to hearing from OP about this before I can get back to CM13, it would be great. Btw, CM13 was absolutely fantastic in the 20 minutes I could use it for before ending up with that vicious brick. Really looking forward to a more stable version. Keep up the great work, dev! Thanks!
Click to expand...
Click to collapse
Not happy to hear this but I've also never experienced it. Please keep in mind we are working off a massive kernel rebase to support 6.0 and things may not be ideal at times. I have been running 6.0 on N3 for a few months now but only in the last week have I had the camera functional.
Also fwiw the stock colorOS rom should flash in the newer TWRP builds, I made sure that worked myself.
Without some kind of log I'm at a loss as to what happened here. If any randomish reboot happens I need /proc/last_kmsg to have any chance of deciphering why it rebooted.

Thanks a lot for your response, bud. The N3 is my daily driver, so I couldn't mess around too much. I waited for a bit, then flashed stock ColorOS right away, because I need the phone, especially on this busy weekend. I think I was using an older version of TWRP, so I'm not sure whether that could be a problem either. I'm going to try and get back on CM 13 sometime today, and see how it goes this time.
Once again, thanks a ton for working on this phone. I thought it was completely dead. Oppo are really bad at supporting any devices except the Find 7. Let me know if I can help in any way, I'd be more than happy to be of any help

This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?

SufiSam said:
This may be a silly question Jason, but I see all these new builds popping up on your website for the N3, but I can't seem to find any kind of a nightly changelog on either cmxlog.com or even review.cyanogenmod.org. Is there any way we could perhaps see what changes are being made?
Click to expand...
Click to collapse
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.

jrior001 said:
Ah, I never updated the thread here. I got official nightlies turned on so fresh builds should be hitting http://get.cm/?device=n3 now. Change log will be back w/ota in the built in updater.
Click to expand...
Click to collapse
Thanks for this, bud! You're the best!

SufiSam said:
the phone shut down by itself and then reboot. The phone was stuck in a bootloop.
Click to expand...
Click to collapse
Got the same problem here. There was CM12 before, and ColorOS. But after flashing CM13 and that error, i cant flash any AOSP roms. Just ColorOS. And got permanent wifi and proximity sensor issues. They doesn't work anymore, even after flashing stock clean chinese ColorOs rom. Don't even know, what to do...

Got the same problem, can't boot up now nor flashing cm 12.1 back, only coloros works now and without wifi. We need a fix as i can't stand the poor coloros.
---------- Post added at 01:22 PM ---------- Previous post was at 01:16 PM ----------
So guys I've found a temporary wifi fix, you need to copy some files from the coloros zip to the /persist folder using root Explorer, works for me, but still not a permanent fix.

Sounds good) What files?
And check please all sensors, such as proximity, light, and others. there are a lot of programms in google play for cheking that.

To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.

Man, you are the best! And what about sensors?
And where did you find this solution?

hussaination said:
To get wifi working, follow these steps :
**YOU NEED A ROOT **
1. Extract this file to get the 4 needed files.
2. Using root Explorer , copy the extracted files to /persist folder in root directory.
3. Select all the files after copying and select permission.
4. Make the permissions as rw-r-r--
5. Try to switch on wifi multiple times until it works.
**IMPORTANT**
Rebooting the device will deletes the files from /persist folder and wifi will not work again until you repeat the steps , don't know why, but it is a temporary fix and works with no issues.
Click to expand...
Click to collapse
Don.Archon said:
Man, you are the best! And what about sensors?
And where did you find this solution?
Click to expand...
Click to collapse
Are you guys saying wifi and sensors were not working for you? If so this is important and i need logs from a clean boot. These have always worked fine for me on these builds.

How to make this logs? i know nothing in programming (

Remix for Teclast x98 Plus...

It seems the files in the zip from Jide for x98 Plus are in reality for Cube i10, since the folder inside the zip has Cube i10 as name.
Does anybody have already flashed that rom ?

How to Flash the ROM? I tried. Unsuccessfully. Cant find any hints how to Flash it.

There are a couple of videos in youtube about installing but an official installation guide would be really appreciated, since it is a supported device.
Plus info would be useful about what is needed before anyone start flashing, eg. external keyborad, usb hub?
I hope jide team keeps up good work and support X98 Plus with later releases too!

You need the Intel Flash Tools :
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Select from the Tool the flash.json file from the Rom, set option to 'update' and flash.
But it will not work out of the box. You first need to flash mirek custom rom and after that, in place of record the device to google server as usually with new devices, flash directly with remix OS and Flash Tools.
I had an issue after that and had to flash again boot.img and recovery.img separatly with the help of a script .bat... Maybe a bug, i don't know. But i have been the only one from techtablet forum to have this issue.
The rom is amazingly smooth, very beautyfull and it solved the lagging issue i had with the custom rom and the hacker keyboard. Unfortunately, dolphin browser doesn't work on it. [Not bad since i'm a firefox user for privacy reason].
Unfortunately, there is no way to root from adb, since the rom is locked.
In the next weeks [when i'm done with school], i will root the system image with superSU before flashing it back in the device.
Hope this work.

w1nst0n sm1th said:
You need the Intel Flash Tools :
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
Select from the Tool the flash.json file from the Rom, set option to 'update' and flash.
But it will not work out of the box. You first need to flash mirek custom rom and after that, in place of record the device to google server as usually with new devices, flash directly with remix OS and Flash Tools.
I had an issue after that and had to flash again boot.img and recovery.img separatly with the help of a script .bat... Maybe a bug, i don't know. But i have been the only one from techtablet forum to have this issue.
The rom is amazingly smooth, very beautyfull and it solved the lagging issue i had with the custom rom and the hacker keyboard. Unfortunately, dolphin browser doesn't work on it. [Not bad since i'm a firefox user for privacy reason].
Unfortunately, there is no way to root from adb, since the rom is locked.
In the next weeks [when i'm done with school], i will root the system image with superSU before flashing it back in the device.
Hope this work.
Click to expand...
Click to collapse
Oh well, is there any way to flash Remix OS from Windows 10?
I have the Windows only version, and having Remix OS without upgrading to factory stock or any custom android would be nice.

Worked Fine, Thank You w1nst0n sm1th
Is it possible to Flash it to the whole 64 GB? I tried to replace the Original gpt.bin from Remix OS with the gpt.bin from Mirek ROM (1_GB_system_56.5_GB_data_gpt). Without success. Any Ideas?

Not sure about you guys but mine 98x plus A5C8 do have the wake problem after the display turn off something.

It is working on X98 Plus 3G ? (A6C9) ...

MTK6589 said:
It is working on X98 Plus 3G ? (A6C9) ...
Click to expand...
Click to collapse
Hi, yes but it's not working so fine for now, in my case, some apps don't work, the camera is not supported and sometimes i've got micro freeze (when i'm installing a app ont google play). I'm new on this OS, I don't know how to install on the micro sd apps.
I think, it needs optimizations.
Despite this issues, it's offering a good user experience ( i'm not sure i'lll stay on remix OS, it will depends on future improvments)

Hi. Does anybody have working 3G on Remix OS2.0? My tablet is A6C9, tried to install couple of times, can't find settings for 3G, only Wi-Fi.

Dobriak said:
Hi. Does anybody have working 3G on Remix OS2.0? My tablet is A6C9, tried to install couple of times, can't find settings for 3G, only Wi-Fi.
Click to expand...
Click to collapse
There is no Remix 2.0 for x98 plus 3g version. Only for x98 3g and only Remix 1.0.
But the remix 2.0 for plus version seems to have phone ability, according the packages in /system/app & /system/priv-app folder. I disactivated it with MyAndroidTools Apk.

Does it work on a Teclast X98 Plus II ID C2E3?
2gb +32GB model
Thanks

laggy pixel c after updates

Anyone else notice their pixel c getting sluggish and laggy after the most recent updates. Nothing seems to fix it. A reboot might make it appear better but a few minutes in it just stutters and lags like crazy. Already restored it once and that helped a bit but then it just started doing it again....
Just curious before I start looking into a rouge app. Any idea how I could search to see if an app is causing the problem?
Thanks

Same here, I have tried resetting the device with no effect, when I check with AIDA64 my CPU iss stuck on 204 mhz (all cores). Before all this happened it was not accepting my pin code (which I have been using for 3 years) so I done a resset. I am thinking to go back on Nougat now. Let me know if you find a solution. Thanks
---------- Post added at 11:23 AM ---------- Previous post was at 10:50 AM ----------
OK now seems to be fine, try disabling google chrome (uninstall updates from that app and dissable automatic updates from playstore), enable chrome again but don't install update for that. Its back to normal for me, we need to wait for fix for google chrome

damjan006 said:
Same here, I have tried resetting the device with no effect, when I check with AIDA64 my CPU iss stuck on 204 mhz (all cores). Before all this happened it was not accepting my pin code (which I have been using for 3 years) so I done a resset. I am thinking to go back on Nougat now. Let me know if you find a solution. Thanks
---------- Post added at 11:23 AM ---------- Previous post was at 10:50 AM ----------
OK now seems to be fine, try disabling google chrome (uninstall updates from that app and dissable automatic updates from playstore), enable chrome again but don't install update for that. Its back to normal for me, we need to wait for fix for google chrome
Click to expand...
Click to collapse
My C also stopped accepting my known-good PIN. No choice but reset , but the cause remains a mystery. Does anyone have a fix for a laggy external keyboard? Often (but not always) the kybd will be unavailable for login or filling form fields unless I'm quite patient. Seems to be infamous BT lag and is the only annoying thing about my C. If only there were a way to speed up BT … is there?

I´m having the same issue for a long time now.
Already unlocked the bootloader and installed LineageOS, but nothing seems to fix it.
I´m going to try the damjan006´s solution with chrome to see if I got lucky and report back. Thanks in advance.
Tested removing Chrome, still the same issue, not fixed for me.

RickRand said:
My C also stopped accepting my known-good PIN. No choice but reset , but the cause remains a mystery. Does anyone have a fix for a laggy external keyboard? Often (but not always) the kybd will be unavailable for login or filling form fields unless I'm quite patient. Seems to be infamous BT lag and is the only annoying thing about my C. If only there were a way to speed up BT … is there?
Click to expand...
Click to collapse
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...

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.

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.

Same happening here. Don't even chrome enabled.

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.

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.

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.

kingweee said:
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...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.
Click to expand...
Click to collapse
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.

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.

Mein Pixel C lag ziemlich schlecht, als der Akku mit Lager 8.1 unter 67% fiel (gesperrter Bootloader, alles unberührt). Ich habe versucht, die Werksbilder zu reflashieren, aber das Problem blieb bestehen. Ich habe rooted (magisk 18.1) und Kernel Adiutor installiert. Das Problem war offensichtlich, die CPU würde stark drosseln (unter 67% der Batterie), abhängig von der Menge des aktiven Kerns (mit 4 Kernen würden sie alle bei ~ 200 MHz laufen, mit 2 Kernen etwa 700 MHz und mit 1 Kern etwa 1100) MHZ). Es war nicht so schlimm, dass 1 Core auf 1100 MHz lief, aber es war immer noch ziemlich langsam.
Um das Problem zu lösen und zu beheben, habe ich LineageOS 15.1 und den Kernel von followmsi ( https://forum.xda-developers.com/pix...pixel-t3375591) installiert). Zu meiner Überraschung blieb das Problem trotz des benutzerdefinierten ROM und des benutzerdefinierten Kernels bestehen. Ich denke, dass mit dem 8.1 oreo-Kernel und dem Pixel C etwas nicht stimmt (siehe Google-Forum hier: https://productforums.google.com/for...I/VO4n9l_DCAAJ ). Also versuchte ich eine zweite Lösung. Diesmal habe ich Folgendes getan:
1. Flashed TWRP: twrp-3.2.3-0-dragon.img
2. Flashed in TWRP: Followmsis unoffical lineageOS 16.0: lineage-16.0-20190206-UNOFFICIAL-dragon.zip
3. Flashed in TWRP : (gleiche Sitzung vor dem Starten in LineageOS): OpenGAPPS Arm64 Pico-Paket: open_gapps-arm64-9.0-pico-20190302.zip (m
4. Flashed in TWRP: (gleiche Sitzung vor dem Booten in LineageOS): Followmsis Android 9-Custom-Kernel : tegra-3.18_kernel_pie_dragon_v190205_unicorn-xceed-followmsi.zip
Und voila, wieder auf vollen Touren. Tatsächlich scheint das Tablet besser zu laufen als je zuvor. Nach einigen Tests habe ich Magisk 18.1 (für root und passnet safetynet) installiert, und alles läuft bestens. Die CPU scheint nun korrekt vom 9.0-Kernel verwaltet zu werden. Ich kann jedem, der dieses Problem hat, empfehlen, mit den oben genannten Schritten fortzufahren. Wenn Sie mit benutzerdefinierten ROMs nicht vertraut sind, können Sie alternativ den letzten Android 7.1-Build installieren (ryu-n2g48c-factory-0bc0ee15.zip - Anleitung hier: https://mmikowski.github.io/pixelc-revert-nougat/ ).
Hoffe das hilft.
Click to expand...
Click to collapse
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?

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 !

Running lineage 15.1 with microg and had this problem. Flashed the unified oreo kernel and problem solved!

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

Ulunyth said:
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 !
Click to expand...
Click to collapse
This solved everything that I wanted to fix, I was so annoyed that wipes and different ROMs couldn't make a difference. Thanks!

Ulunyth said:
Hi,
Thank you for this tip !
I did the same, but with the latest Lineage 17.1 (Android 10). Here are the links :
...
Enjoy !
Click to expand...
Click to collapse
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.

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 : )

Development Pixel Experience Running On My Fold 3 | WIP / Development

Hi Guys,
I thought I'd post this here, I kind of hit something that can lead you guys /w fold 3 to excitement. Also need help and recommendation
Firstly I bought my Fold 3 a while back and is unlocked with O2 UK and Vodafone UK. It's currently rooted and no I'm not anally mad about Knox as I use an S22 ultra as my daily phone. I've managed to get Pixel Experience running on my Fold 3. However there are 2 noticeable problems listed in the table.
Hopefully this attracts a few devs who can help and sort out a few issues. Just for lols I've tried booting Android 12.1 but sadly it gets stuck in a boot loop.
Anyways I've attached several images.
Update - 05/02/23
Hi Thank you for all of your interest and suggestions. I am still working on this project but progress is slow. Please do not contact me directly!. I had a few Indian's nagging me on this project. I suggest you all wait until I get something out stable. I have bought an iPhone 14 Pro Max , moved to Cheddar in the south west of the UK and now working for a new company.
Ok for the fun stuff. I managed to get the outer screen working in conjunction with the inner screen. So when you finished with the inner screen and close it., all of the activities will push to the outer screen.
Wireless and reverse charge is now working.
Brightness is now working on both screens
RIL - working (3G, 4G, 5G, WiFi, Bluetooth) etc.
Camera Works
Still needs more testing - Please do not contact me until I fix a few more bugs. such as biometrics (Finger Print, Face Scanning) Flash light etc..
Here's a video of progress.
Cheers
Super291
What WorksWhat Doesn't WorkEverything...Flash light doesn't work, but who uses it though Biometrics ( Face Scanning, Finger Print Reader) - Screen pattern works.

nice i hope u get it to work.... but i dont think its an upgrade for ur fold ^^
(Just my opinion!) ^^

Immediately after I got my Fold 3 I tried various launchers to get it closer to a Pixel as I find the user experience on the Samsung to be quite poor compared to a Pixel. This project of yours looks promising and I hope you are able to get the remaining issues worked out.

surprised pixel experience works. What's the base made on? Maybe reach out to the developer and provide a logcat potentially to identify what the issue is.
They may be able to help but it is good progress.
I assume this isn't GSI based is it? I am curious because I would love to boot a GSI rom on my vivo x fold so I am curious about this

This isn't a GSI. Its a full port. As far as I know, I'm the only one who's working on AOSP port for now. But if devs with to help. Then I'm open to share my work.
You could try DSU loader.. If your brave that is. Basically DSU loader will allow you to some what dual boot. Essentially GSI on your phone but with your original OS. Bit like having a PC but you can dual boot with Windows and Mac.
Progress will be slow as I'm working full time but will post updates once I have everything fixed.
take a look on the link.... I'm not responsible if you phone turns into a nuclear bomb!
DSU Loader

Super291 said:
This isn't a GSI. Its a full port. As far as I know, I'm the only one who's working on AOSP port for now. But if devs with to help. Then I'm open to share my work.
You could try DSU loader.. If your brave that is. Basically DSU loader will allow you to some what dual boot. Essentially GSI on your phone but with your original OS. Bit like having a PC but you can dual boot with Windows and Mac.
Progress will be slow as I'm working full time but will post updates once I have everything fixed.
take a look on the link.... I'm not responsible if you phone turns into a nuclear bomb!
DSU Loader
Click to expand...
Click to collapse
Does it trip knox?

Super291 said:
This isn't a GSI. Its a full port. As far as I know, I'm the only one who's working on AOSP port for now. But if devs with to help. Then I'm open to share my work.
You could try DSU loader.. If your brave that is. Basically DSU loader will allow you to some what dual boot. Essentially GSI on your phone but with your original OS. Bit like having a PC but you can dual boot with Windows and Mac.
Progress will be slow as I'm working full time but will post updates once I have everything fixed.
take a look on the link.... I'm not responsible if you phone turns into a nuclear bomb!
DSU Loader
Click to expand...
Click to collapse
What device tree and kernel did you compile Pixel Experience with

cooldude20000 said:
Does it trip knox?
Click to expand...
Click to collapse
Custom roms or anything not officially made by samsung will ALWAYS trigger knox.

Super291 said:
This isn't a GSI. Its a full port. As far as I know, I'm the only one who's working on AOSP port for now. But if devs with to help. Then I'm open to share my work.
You could try DSU loader.. If your brave that is. Basically DSU loader will allow you to some what dual boot. Essentially GSI on your phone but with your original OS. Bit like having a PC but you can dual boot with Windows and Mac.
Progress will be slow as I'm working full time but will post updates once I have everything fixed.
take a look on the link.... I'm not responsible if you phone turns into a nuclear bomb!
DSU Loader
Click to expand...
Click to collapse
Hello
i saw your thread and im working also on a GSI for Galaxy Z Flip3
i build LineageOS 19.0 for this phone but i has a lot of bugs
for the low brightness (as i have this issue myself too) if you used treble gsi device tree you will know that TrebleApp has a feature called "use linear screen brightness" that will fix the low brightness for the screen, you can enable it also using props in system.prop (just apply treble patches)
for the second screen no clue , i manage to disable default screen mirroring to the second (you should not because fold screen have the same launcher for both of screens)
if you figure it out , to forgot me

Hi. Any activity of fixing bugs?

gis gibt es Neuigkeiten in Bezug auf Pixel Experience Rom für das installierte Fold. Es sieht gut aus. Schade, dass das Frontdisplay nicht reagiert würde euch sehr dankbar sein wenn es doch klappen könnte

I managed to install a working rom, almost everything works, only the brightness on the front of the display cannot be adjusted and unfortunately no google services, maybe someone has an idea how to install google services, otherwise the rom looks fine out
Andy Yan's personal builds // GSI
Download Andy Yan's personal builds // GSI for free. None
sourceforge.net
lineage-20.0-20221212-UNOFFICIAL-gsi_arm64_vS.img.xz

italo19811 said:
Ich habe es geschafft eine funktionierende Rom zu installieren, fast alles funktioniert, nur die Helligkeit auf der Vorderseite des Displays lässt sich nicht einstellen und leider keine Google-Dienste, vielleicht hat jemand eine Idee wie man Google-Dienste installiert, ansonsten sieht die Rom gut aus
Click to expand...
Click to collapse
wdys?

whassup1 said:
wdys?
Click to expand...
Click to collapse
Translated quote:
I managed to install a working rom, almost everything works, only the brightness on the front of the display cannot be adjusted and unfortunately no google services, maybe someone has an idea how to install google services, otherwise the rom looks fine out

whassup1 said:
wdys?
Click to expand...
Click to collapse
?

italo19811 said:
?
Click to expand...
Click to collapse
italo19811 said:
?
Click to expand...
Click to collapse
wdys = What Did You Say? .. lol

does anyone know of a way to install gapps later? even if the process has been installed via gsu sideloader? Tried to install twrp unfortunately I can't assign it a partition from where it should start to install the .ZIP

any new update here or a telegram channel?

Can anyone shot some photos or record a video how GSI working on Fold?
To install GSI we need to burn knox, so im afraid about use experience

russanandres said:
Can anyone shot some photos or record a video how GSI working on Fold?
To install GSI we need to burn knox, so im afraid about use experience
Click to expand...
Click to collapse
Yes because need open bootloader