yashsingh1/xdaforums huggingface dataset:
[Pixel C Original Android Development] SonySteve:
Awesome, I executed the fix fastboot feature in TWRP, then boot into fastboot mode and was able to successfully flashed the vendor.img

No more update vendor.img message after reboot!!

---------- Post added at 05:39 PM ---------- Previous post was at 05:35 PM ----------

See if you wanna give this a try.

With USB cable connected to PC already, execute the fallowing operations.

Go Setting->Developer options-> Under Networking section-> Select USB configuration

By default it's checked at MTP already.

What I did was check to PTP, then back to MTP. Immediately then I see messages on my PC that new storage device was detected with MTP access and all.

I think only the initial boot up (after flashing) require such operation. Afterward when hooked up to PC, the storage device should be automatically detected as it suppose to.
[Pixel C Original Android Development] NYCHitman1:
It is this way across any device on marshmallow because of the way Google changed how devices mount storage.
[Pixel C Original Android Development] YevOmega:
How customizable is the kernel my friends? Also, are all eight cores available now, or just 4 still? Thanks!
[Pixel C Original Android Development] NYCHitman1:
Only 4 cores. I have no intention of looking into enabling the other 4. Nvidia did it this way for a reason.

Thus far, I've added some CPU gov's, I/O schedulers, and some other behind the scenes improvements.
[Pixel C Original Android Development] YevOmega:
Thanks. Would it hurt to try enabling them though? What's the worst that can happen? Like I'm not even being sarcastic. If they couldn't run, Nvidia wouldn't have put them into the SoC, am I wrong? (Hopeful Harry over here).
[Pixel C Original Android Development] NYCHitman1:
It's an architectural thing. They ran all the experiments and all that on their own. They must've figured that the additional cores don't contribute much by way of performance or battery life.
[Pixel C Original Android Development] dkryder:
not sure if the A53 on pixel c are set up like the nvidia tx1 but this is how the situation was explained on the nvidia forums awhile back,

This is all that should be listed. You've probably read about the A53 cores, but this is part of the low power mode.

The ARM CPUs tend to advertise the term "big.LITTLE"...which is a way to have both low power and high power without running out of battery. In essense, the A57 cores each have a "shadow" core...the shadow cores are extremely low power and great for detecting activity and then switching back to the A57 cores. The hardware in some computer architectures would require the operating system to glue these CPU cores together...big.LITTLE does this in hardware. Those "LITTLE" cores directly connect to some of the internals of the "big" cores, and do not have issues with software requirements to go back and forth between cores without programming support. Thus, they are invisible, and participate as something of a back end for the fast cores, while the fast cores are the front end. You can't stop processing to save power...if you did, then you can't wake up and do things like monitor for an incoming telephone call...A53 can do this with virtually no battery consumption.

There is also an ARM Cortex A9 in TX1, it is a dedicated audio processing core, and will not show up as a CPU.

so it seems the A53 are in use but just hidden and that how they interact with the A57 is done on a hardware level.
[Pixel C Original Android Development] YevOmega:
Alright, have it your way, but I don't buy it. A53 cores are low power and should help battery life.
[Pixel C Original Android Development] NYCHitman1:
I wasn't selling you anything. Read up on what Nvidia did on the X1. Discussion doesn't need to continue here as it doesn't contribute anything to the development of the ROM.
[Pixel C Original Android Development] YevOmega:
Very interesting and odd. Ok. Cool.

Edit: Sorry for the OT.
[Pixel C Original Android Development] beardymcgee:
[MENTION=2489052]NYCHitman1[/MENTION]

Are you able to confirm if DU Kernel has the owner change issue when making modifications to the governor, stock had issue where it changed from system to root when you changed it and broke some things....
[Pixel C Original Android Development] NYCHitman1:
No issues here, bud. None that I've noticed, anyway.
[Pixel C Original Android Development] beardymcgee:
Cool beans, time to resurrect my old thread and with more users maybe I can get more feedback if its an improvement or not
[Pixel C Original Android Development] NYCHitman1:
If what is an improvement?
[Pixel C Original Android Development] beardymcgee:
Sorry, this

http://xdaforums.com/pixel-c/general/reuse-advanced-interactive-governor-t3297783
[Pixel C Original Android Development] mrnovanova:
Enjoying the ROM [MENTION=2489052]NYCHitman1[/MENTION]. Love the versatility and really appreciate your effort bringing it to the pixel c. Thanks a million.
[Pixel C Original Android Development] NYCHitman1:
I'm glad you're enjoying it as much as I am.
[Pixel C Original Android Development] streilu:
Anyone got problems with battery charging? Also there's a huge play services battery drain on my device...

Gesendet von meinem Pixel C mit Tapatalk
[Pixel C Original Android Development] NYCHitman1:
No issues here.
[Pixel C Original Android Development] drewski_1:
No drain issues either.

My battery did get pegged @ 100% all day yesterday (unplugged and after a couple hours use), but a reboot fixed that.
[Pixel C Original Android Development] choder:
Thanks for this Rom!
[Pixel C Original Android Development] SonySteve:
Hi, with flashing the rom & gapps only.

During browsing via Chromium the app keep close with message "Unfortunately, Chromium has stopped."

Do I need to install any additional component to have Chromium running fully here?

Thanks
[Pixel C Original Android Development] NYCHitman1:
Nope.
[Pixel C Original Android Development] SonySteve:
Thanks for the quick reply, much appreciated.

Me fiddle around to see what's causing the crash then. (since all is there)
[Pixel C Original Android Development] NYCHitman1:
Grab a logcat of the FC. That should tell us what's up.

There had been some previous sporadic reports of FC's while browsing in Chromium -- but we had fixed that by reverting back to the LKGR version, which this build uses (assuming you're on the official or anything thereafter).

As an aside, Chromium is quite delicate. It needs permissions granted for a few things to stop the annoying notifications, etc.. I personally just nuke it and use Chrome. Saves me a headache lol.
[Pixel C Original Android Development] Mike02z:
I've been running this for 2 days with heavy use. This ROM is rock solid for me. Great work!
[Pixel C Original Android Development] streilu:
So a short update for now. No more battery drain of play services (since updating it manually).

But there is some strange behaviour with battery status display. Sometimes it's jumping to 100% and staying there until the battery is empty.

There's also some problem when plugging or unplugging the charger. Not showing that it's charging or showing that it's charging while unplugged.

Otherwise great rom with useful features, thank you!

Gesendet von meinem SM-G925F mit Tapatalk
[Pixel C Original Android Development] Freak07:
Mine shows the same behaviour. I have battery percentage inside the battery Icon enabled. When plugging Charger in it shows suddenly the percentage inside the icon plus additionally the percentage outside in the status bar. When unplugged it stays this way. Sometimes I see the charging "flash" when plugging the Charger in for a splitsecond.

Would a logcat or anything be helpful?
[Pixel C Original Android Development] NYCHitman1:
No. We're in the process of reworking how battery icons will be represented in the status bar -- so all of this is just going to go on the back burner until further notice.
[Pixel C Original Android Development] brando56894:
I love the ROM, but the only (major) issue that I have is with the keyboard. When I have my physical keyboard connected via bluetooth the softkkeyboard still shows up when I click on a text field and type with the physical keyboard. Also when I have the keyboard in portrait and click on the text field, the soft keyboard opens with the landscape orientation, so half of it is cut off.
[Pixel C Original Android Development] NYCHitman1:
I disabled the KeyboardLayout because Google FUBAR'd the source and without one for me to test -- I wasn't going to waste time on it.
[Pixel C Original Android Development] pjdick:
I do not think it is a battery icon issue. It seems to be much deeper rooted. When I plug in to charge and unplug, Better Battery Stats is saying it is on charge when it is not, and vice versa. It seems to get messed up if I use a Type C (fast charge). When I reboot and use a USB A to C charge it works fine. Even in settings, the "Charging" and "Discharging" gets mixed up when I introduce the Type C Fast Charge....
[Pixel C Original Android Development] NYCHitman1:
I didn't say it was. I merely said that it was hitting the back burner until the aforementioned stuff was completed.
[Pixel C Original Android Development] brando56894:
I was on the official build when this was happening, but I flashed the latest nightly and the keyboard doesn't pop up in hangouts, but it does here in Tapatalk, at least its in the correct orientation this time in portrait mode lol
[Pixel C Original Android Development] greco2003:
Prolly a newb question but i want to flash this rom my question is the vendor.img does it have to be done through fastboot or can it be done through twrp. Thanks for your help
[Pixel C Original Android Development] NYCHitman1:
It can be done through TWRP if you're using a version that supports flashing vendor images. If not, you'll need to use fastboot.
[Pixel C Original Android Development] DarthDestroyeis:
Chainfire's flashfire app can also be used to flash the vendor.img
[Pixel C Original Android Development] greco2003:
Thank you guys for your help. And thank you to the op for making this rom and supporting our device. Im gonna flash it later when i get off work have it downloading now so it will be ready when i get off.
[Pixel C Original Android Development] NYCHitman1:
Kernel issue that prevented the battery from properly displaying the correct percentage has now been squashed. Should be implemented in time for the next weekly build.
[Pixel C Original Android Development] pjdick:
Great news. Thanks for taking care of that (and for the ROM)!
[Pixel C Original Android Development] Legendaria:
How is the battery life on this ROM? Would anyone recommend using the Xceed kernel with this or should I not bother? Also, once this rom has another update will I be able to dirty flash it or I'd have to flash it like it was a brand new rom?
[Pixel C Original Android Development] NYCHitman1:
You can dirty flash official builds and weekly builds over each other, but like always -- if you run into issues, clean flash before reporting anything. Also, read the flashing instructions from the OP for an answer to your kernel question.
[Pixel C Original Android Development] YevOmega:
Hey. How would you recommend I go about going from DU to N DP3?
[Pixel C Original Android Development] NYCHitman1:
Fastboot flash the images.
[Pixel C Original Android Development] YevOmega:
Thanks!
[Pixel C Original Android Development] brando56894:
Is there anyway to disable the soft keyboard? It's really annoying that it takes up half of the screen realestate when I'm using a physical keyboard.
[Pixel C Original Android Development] Istvan_86:
Hello guys,

Actually I´m using DU in my 1+1 and I must say that it´s an amazing ROM, so I want to try it in my Pixel C

but I´m a bit confussed.

If I´m not wrong I must follow these steps:

1-First of all I should check the OEM unlock option under developer settings in order to unlock bootloader

2-Flash TWRP from this post: http://xdaforums.com/pixel-c/orig-development/unofficial-twrp-2-8-7-0-pixel-c-dragon-t3288243

3-Full WIPE

4-Flash ROM

5-Flash GAPPS

6-Reboot

Is that correct?

Also the ROM is rooted as usual?

Thanks in advance.
[Pixel C Original Android Development] NYCHitman1:
Yes, you have to use the OEM unlock switch in developer settings -- otherwise you can't unlock. Also, the build is rooted.
[Pixel C Original Android Development] Istvan_86:
Really thanks for your fast answer, I flash the ROM in a few hours and I post my first impressions.

I have another question, usually I don´t care about unlock bootloader in my devices but I want to know if this void the warranty or it´s allowed like Nexus devices.

Thanks again bro and good job.
[Pixel C Original Android Development] NYCHitman1:
When you go to unlock your bootloader, there's some text associated with it on the display -- I suggest that you read it to understand what you're getting yourself into.
[Pixel C Original Android Development] Istvan_86:
Hehe, thanks again. I not even click on that button yet :D
[Pixel C Original Android Development] Istvan_86:
Hi again mates,

I start all the process to unlock BL, install TWRP and flash ROM. All goes fine but after install TWRP I can´t boot again into the factory ROM. I just can enter into the recovery or power off the device.

What can I do? I never have a problem like this installing a recovery....

Thanks in advance.
[Pixel C Original Android Development] NYCHitman1:
Try this: https://www.androidfilehost.com/?fid=24545065934258539
[Pixel C Original Android Development] Istvan_86:
Thanks for your help but the problem still persists...

You know other method to try to solve the bootloopp?

EDIT: Forgot to say that I try the 3.0.2.0 version of TWRP before posting xD
[Pixel C Original Android Development] NYCHitman1:
Are you flashing DU or trying to get back into system after the factory reset?
[Pixel C Original Android Development] drewski_1:
I had this issue twice where it kept booting to recovery.

Both times booting to Bootloader and then issuing "Fastboot Reboot" command got it to boot to system. I don't fully understand why, but it worked. :confused:
[Pixel C Original Android Development] Istvan_86:
First of all, really thanks for help me,

I even try to flash DU yet.

OMFG bro,

I did taht and works for me (I should do it twice)

And second...... Now it´s time to flash DU!!!

Thanks again for all your help.
[Pixel C Original Android Development] Istvan_86:
Hi again guys,

When I boot into recovery I can´t select the zip files that I put in the tablet storage. I can´t find them. What can be the problem now?

Thanks in advance.
[Pixel C Original Android Development] redukt:
Well first - which recovery? It make sense to put your flashable files in a seperate folder in /sdard/. If you´re on TWRP you´ll have a data explorer to find your files. Make sure your files are flashable. BTW - your signature is broken ;)
[Pixel C Original Android Development] NYCHitman1:
He probably didn't decrypt.
[Pixel C Original Android Development] siloportem:
I'm using the weekly builds of DU for 3 days now and everything works really nice, thanks for the work porting this to the pixel c.

I also had the problem with always rebooting to recovery when first installing DM but a "fastboot reboot" fixed this.

I'm using DU for the first time now after always using CM on my phones/tablets and I really like that it's not so "bloated". The only thing I'm missing is something to manage permissions like "privancy guard" on CM. Is there something like that in DU?
[Pixel C Original Android Development] NYCHitman1:
No, we haven't added Privacy Guard -- nor do we have any intent to do so right now.
[Pixel C Original Android Development] Istvan_86:
Hello guys,

Finally after install TWRP 3.0.2.0 and wipe data in TWRP I can read my sdcard and install DU.

Really thanks for all your help, now it´s time to try this amazing ROM and post some feedback.

EDIT 26/05/2016:

Hi again mates, after the strange initial probles with the bootloop in TWRP (thanks all that help me :D ) The ROM is totally stable and smooth for me.

Now I´m testing battery life and SOT. I try to give some screenshoots in the next days.

Really good job, like all DU ROMs.
[Pixel C Original Android Development] GonzoKSV:
Flashed DU yesterday. Runs completely smooth and fast and of course stable, too. But there is one bigger problem I have got when I'm using the hardware keyboard (German Layout): I can't write the ü (instead it does an ` accent) and the signs # * + ' do not work, too. Ä and ö are no problem, only the ones I told. I chose German keyboard in the options. Do you have any suggestions?

Here's a photo of the hardware keyboard. Thanks a lot!
[Pixel C Original Android Development] NYCHitman1:
Please read prior to posting -- thanks!
[Pixel C Original Android Development] GonzoKSV:
Sorry, I thought I read everything but I didn't read this posting.

Will there be any possibility in future to get it work?
[Pixel C Original Android Development] NYCHitman1:
Maybe, but I don't have a keyboard for testing and do not intend to purchase one either right now. So there are no guarantees.
[Pixel C Original Android Development] GonzoKSV:
Hmm... okay, thanks for your fast answers and help. Maybe I decide later to stay or go back sadly to stock for a while because I'm using the pixel c for working.
[Pixel C Original Android Development] NYCHitman1:
http://gerrit.dirtyunicorns.com/#/c/29524/
[Pixel C Original Android Development] Myst3rion09:
https://github.com/Myst3rion09/android_device_google_dragon/commit/7edc52b008226d1ff0d5f1d15915c5ed9bd692e9

This fixt it for me. Testet on german keyboard.
[Pixel C Original Android Development] NYCHitman1:
The issue with that is that the code in AOSP for the IME stuff is in res/* not lib/*.
[Pixel C Original Android Development] GonzoKSV:
Thanks! I'm going to test it for my device in the weekend!
[Pixel C Original Android Development] NYCHitman1:
Well, I was just showing it to you. You won't be able to test it unless you compile DU on your own (for now, anyway).
[Pixel C Original Android Development] Myst3rion09:
Oh sorry. My fault :rolleyes:

Tested your commit on a personal build. Works perfect. Thanks.
[Pixel C Original Android Development] drewski_1:
[MENTION=2489052]NYCHitman1[/MENTION] is the option for the Stock Pixel C have layout (buttons on the side vs centered) somewhere in the settings?

And if not, is it "on the list" for a future releas
[Pixel C Original Android Development] NYCHitman1:
Negative [MENTION=4752026]drewski_1[/MENTION] on both accounts.
[Pixel C Original Android Development] NYCHitman1:
As an aside, I've bumped up TWRP a bit -- hoping that I've got the encryption sh*t down pat for those who are still encrypted.

https://www.androidfilehost.com/?fid=24566466246344884
[Pixel C Original Android Development] followmsi:
Interessting .. hope you fixed it. :)

How did you relink libkeymaster_messages.so ?
[Pixel C Original Android Development] NYCHitman1:
Compiled the modules and made sure that the libs got directed to their proper directories. Unfortunately, I'm decrypted -- so I have no way of testing this theory, but it should work.
[Pixel C Original Android Development] followmsi:
[/COLOR]

Me too .. it's not planned to encrypt for testing.

I did compile libkeymaster_meesages.so as well .. but not sure regarding linking.

Did you use the following build flag ?

TW_RECOVERY_ADDITIONAL_RELINK_FILES := libkeymaster_messages.so

This one gives me compiling errors .. missing target.

If I remove the flag the libs get produced later, but no proper link ?

I need soooo much to learn :)
[Pixel C Original Android Development] NYCHitman1:
Yes, I did have that flag. You might be missing the remainder though.

TW_INCLUDE_CRYPTO := true
TARGET_RECOVERY_DEVICE_MODULES := libc++ libkeymaster_messages
TW_RECOVERY_ADDITIONAL_RELINK_FILES := $(OUT)/system/lib64/libc++.so $(OUT)/system/lib64/libkeymaster_messages.so
[Pixel C Original Android Development] followmsi:
Thanks .. Tested this as well .. this is actually my version v8 :)

But without the last line ..

TARGET_RECOVERY_DEVICE_MODULES := libc++ libkeymaster_messages

Here no problems .. both libs will be compiled and recovey.img will be created.

My problem is the last line .. if I add this line too ..

TW_RECOVERY_ADDITIONAL_RELINK_FILES := $(OUT)/system/lib64/libc++.so $(OUT)/system/lib64/libkeymaster_messages.so

Then I get always compiling error ...

make: *** No rule to make target '/pixelc/out/target/product/dragon/system/lib64/libc++.so', needed by 'out/target/product/dragon/obj_arm/SHARED_LIBRARIES/libbmlutils_intermediates/teamwin'. Stop.

Tested libkeymaster only because I saw "libc++" will be already included anyway.

make: *** No rule to make target '/pixelc/out/target/product/dragon/system/lib64/libkeymaster_messages.so', needed by 'out/target/product/dragon/obj_arm/SHARED_LIBRARIES/libbmlutils_intermediates/teamwin'. Stop.

How to fix this ? :)
[Pixel C Original Android Development] NYCHitman1:
What source do you have synced? AOSP? If so, you're likely missing some dependencies.
[Pixel C Original Android Development] followmsi:
Yep , AOSP .. r43.

As I understood, if the libs get created later on, the dependencies are fine.

On what do you build omnirom ?

Pls no big discussions again :)

But do you have your current TWRP sources published ?

I really like to learn .. Thanks !
[Pixel C Original Android Development] NYCHitman1:
The bootable_recovery is on my personal Github but my TWRP device tree commit is private on our Gerrit server as I only use it to compile TWRP (we don't build a custom recovery with DU)
[Pixel C Original Android Development] followmsi:
Thank you !

----- Made recovery image: out/target/product/dragon/recovery.img --------
#### make completed successfully (04:45 (mm:ss)) ####

With your TWRP sources :)

Looks good .. had to use my Device tree for now.

Including the fwtool .. nice.

https://github.com/nychitman1/android_bootable_recovery/blob/m/prebuilt/Android.mk

Here is the definition for my RELINK problem ... in omnirom / twrp sources as well.

ifneq ($(TW_RECOVERY_ADDITIONAL_RELINK_FILES),)
RELINK_SOURCE_FILES += $(TW_RECOVERY_ADDITIONAL_RELINK_FILES)
endif

Added the libkeymaster_messages.so manually into the Android.mk.

All good and linked inside the /sbin folder now.

But not using the Device BoardConfig.mk for the RELINK .. only the modified "prebuilt/Android.mk".

Will have a deeper look into your dragon device folder .. seems there are some good modifications.

Thanks for your help !!
[Pixel C Original Android Development] NYCHitman1:
New weekly build is up. Should have that keyboard fix built-in that some people were jonesing for. :highfive:
[Pixel C Original Android Development] greco2003:
Love the rom only problem im having is downloading from the play store get stuck in pending and have to restart the tablet to get downloads going. Also when the store is stuck in pending titanium backup wont restore apps from backup.
[Pixel C Original Android Development] NYCHitman1:
No issues here on that front. You should check your connection to make sure your network connection is solid.
[Pixel C Original Android Development] GonzoKSV:
Hey, great news, thanks a lot! I'm going to try it in a couple of days after I have found a solution for my recovery problem. You guys are fantastic!

The pixel is a great device but I had never have so many problems (HTC, Asus) to get everything work before.
[Pixel C Original Android Development] NYCHitman1:
Well, this is different. Dragon isn't your typical device. It has a lot of ChromeOS aspects that hinder the experience in some ways.
[Pixel C Original Android Development] GonzoKSV:
Yes, I hadn't expected that before I bought it and I didn't ask. I thought: hey, it's something like a Nexus device, everything is going to be easier than before. But nevertheless I like the tablet and I'm mostly satisfied with it - but that's because of the great work of the developers like you or followmsi or cheep. Without you guys maybe I would have already sold it. Thanks!
[Pixel C Original Android Development] needoZ:
Is it possible to calibrate the screen colors when using this ROM?