yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] huunn:
Gamepad buttons mapped incorrectly

My Xbox One controller is paired in Bluetooth setting but some of its buttons do not work correctly. Left stick works but other buttons seem to be recognized as another buttons. Games are not playable in Xbox game streaming app & Geforce Now app due to the same reason.

In gamepad testing apps,

right stick is recognized as LT&RT (left&right triggers)

X is recognized as Y

Y is recognized as LB (left bumper)

RB is recognized as MENU (SELECT in android gamepad)

LB is recognized as VIEW (START in android gamepd)

LT, RT, L3, R3 (clicking sticks) & VIEW buttons don't seem to be recognized.

I haven't tested in a stock rom and don't know why it is like this. :confused:

Hopefully someone could fix this. :fingers-crossed:
[Pixel C Android Development] followmsi:
Pls install this kernel and try again ...

https://xdaforums.com/showpost.php?p=82739421&postcount=878
[Pixel C Android Development] LSS4181:
Magisk 20408 and onwards are currently broken due to missing kernel cmdline args.

A while ago I found Magisk 20408 and onwards stopped working on Pixel C Android 10 ROMs. Magisk 20407 and before were okay.

I recently did a bisection on Magisk and found the offending commit, and after the investigation on Magisk's side it appears there is a missing kernel cmdline argument which made Magisk unable to locate the fstab file the newer Magisk versions need to access. The issue is here.
[Pixel C Android Development] followmsi:
We never had this parameter in cmdline.

Normally I don't like to change kernel/device tree to make tools like Magisk working again.

Latest stable 20.4 works fine.

Pls make test kernel to verify missing parameter .. like done for permissive selinux.

https://github.com/followmsi/android_kernel_tegra/commit/0cb02e317df96a93eb0f61104b0c9e77b287b764

Does it solve the problem with latest Magisk beta/canary ?

EDIT:

Made a quick test kernel .. [MENTION=4542513]LSS4181[/MENTION] - Pls check on latest Magisk.

tegra-3.18_unified_dragon_kernel_10_v200910.zip

https://drive.google.com/drive/folders/18cqluw7lp1S720QdV0p-OtHfY9MNpSwn

https://github.com/followmsi/android_kernel_tegra/commit/72a33da3e3dc5a632e5bcb8f95d3c50e27a01dfe

Does latest Magisk work now ? .. Pls confirm !

Cheers
[Pixel C Android Development] LSS4181:
Just flashed this kernel and 20425 canary. It's working now. Thanks!
[Pixel C Android Development] Alxoom33:
I use stable Magisk for Android 10. Canary only needed on A11.

---------- Post added at 08:06 PM ---------- Previous post was at 07:57 PM ----------

Any idea if LOS will be updated to Android 11, now that it is an official build?
[Pixel C Android Development] followmsi:
The sources have been published this week !

Lineage Team has started to work on 18.0 .. https://review.lineageos.org/q/branch:lineage-18.0

I have no idea about dragon builds right now .. we will see how much time is left.

And how many problems we have on Android 11.

Cheers
[Pixel C Android Development] followmsi:
Android 10 - September 2020

lineage-17.1-20200911-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> September 2020

- Binderized DRM and added Clearkey 1.2

- Kernel: Added "androidboot.hardware=dragon" to cmdline -> installation issue on latest Magisk Canary/Beta versions.

- Patched framework/av to bring back "wifi-display" in android 10.

- Patched framework/base to support microG

- Latest LineageOS changes for Android 10

The ROM does contain it's own vendor.img !

Enjoy :p
[Pixel C Android Development] tabormeister:
[MENTION=5480152]followmsi[/MENTION] Thanks for all you do here!! I fresh flashed the 9-11 build and stock gapps, all worked fine until I set a pin. I thought the keymaster issue was gone? It works after a few minutes as expected with the older builds.

Additionally, the always-on display feature in lockscreen settings seems to work pretty well for an LCD screen, it clocks the backlight WAY down and doesn't seem to use too much power - will update with results. Makes it more in line feature-wise with like a Pixel 3.
[Pixel C Android Development] ScratMan38:
Netflix doesn't work anymore on my Pixel C using Lineage 17.1 from August 4th or September 11th.

First, I could not stream the videos, I checked the Widevine status in Netflix app, and it reported as L1. Then I tried to clear app's cache, no effect, so I cleared it's data, and now I can't even login to the Netflix service, it tells me the service can't be reached when launching the app (error code 1001).

When using DRM Info app to check the DRM status, it doesn't even mention Widevine CDM !!
[Pixel C Android Development] tschmid:
Check Post #1883

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] ScratMan38:
I already know that, but my tablet should show L3 and Netflix should still work with SD content ! So why it doesn't work at all ?
[Pixel C Android Development] followmsi:
Pls use root explorer and rename "/vendor/lib/liboemcrypto.so" to "/vendor/lib/liboemcrypto.so-not_used"

Reboot your device and login into Netflix again .. now you have L3 in System and Netflix .. and no more HD content.

But login works this way .. Netflix will keep L3 settings stored on data partition.

Even you rename liboemcrypto.so again and System is L1 again you should still run L3 Netflix without problems nor relogin.

Like mentioned before if you run L3 on boot the system will not use Nvidia HW codecs anymore.

Cheers
[Pixel C Android Development] Alxoom33:
It appears that with this build you have included your latest 3.18 Unified kernel, so there is no need to flash it here.

Is that correct?

Thank you [MENTION=5480152]followmsi[/MENTION]!
[Pixel C Android Development] ScratMan38:
It worked, thanks.
[Pixel C Android Development] Markeee:
I'm wondering if anyone else if having this issue on YouTube and if theirs any fix for it ?

I'm constantly getting this below error and the videos won't run.

I only seem to be getting it on my Pixel C I'm running LineageOS 17.1 (shamu) on my Nexus 6 I never get it
[Pixel C Android Development] tabormeister:
Is there a reason you're trying to play videos in chrome?
[Pixel C Android Development] Markeee:
You lost me here I always watch videos in chrome on my Pixel whats so unusual about that ? :confused:
[Pixel C Android Development] tabormeister:
Oh I just feel like most people use the YouTube app for YouTube videos since it's smoother and more full-featured
[Pixel C Android Development] Markeee:
Yeah thanks for taking the time to reply

No I don't usually install the Youtube app I was just wondering why I'm constantly getting this issue but only on my pixel ?

I'm running LineageOS on my Nexus 6 and I never got the issue there not even once
[Pixel C Android Development] tabormeister:
I'll try this later and see if I can reproduce

---------- Post added at 08:49 PM ---------- Previous post was at 08:02 PM ----------

Huh, did the same thing for me. No problems in youtube app though! Video quality is better too,.
[Pixel C Android Development] Markeee:
Yeah guess I"ll have to use youtube popup city even with Adaway
[Pixel C Android Development] frauhottelmann:
Maybe try NewPipe instead: https://newpipe.schabi.org/
[Pixel C Android Development] tabormeister:
I forget that YouTube has ads - I have YouTube music and YouTube premium
[Pixel C Android Development] Markeee:
Yeah I've used that app before thanks

The problem i have with it is I don't see any way to sort your subscriptions once you export them into the app it just throws them in a pile with no way to organize them,

Thats what I like about chrome I have all my subscriptions organized as bookmarks the way i like
[Pixel C Android Development] huunn:
It works well after reflashing kernel&lnos(Sept. ver.). Didn't know flashing could cause an error like that.

Thank you!
[Pixel C Android Development] frauhottelmann:
You can create groups in your subscriptions.
[Pixel C Android Development] frauhottelmann:
I circled it, since it's in German ?
[Pixel C Android Development] Markeee:
Yeah I see now its a pretty nice app its going to take a a bit to setup the groups thanks
[Pixel C Android Development] :
Tnx for the builds. I'm using the builds already forever.

But I have a question. Do you push your changes to the official Lineage repository or where can I found your source code?
[Pixel C Android Development] tabormeister:
Noticed with the magnetic keyboard that the search button no longer pulls up assistant - is this everybody or just me? I can still trigger with voice, but shortcuts to assistant seem to be broken.
[Pixel C Android Development] tschmid:
Check Post #4 - #8 its on github followmsi theres the manifest

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] tabormeister:
Confirmed with buttonmapper pro that search button is working, Assistant isn't being triggered by anything other than voice though - I can set the button to do other stuff (open settings etc.) but when set to Assistant trigger it does nothing. I've cleared data on the Google app, uninstalled + re-updated, any thoughts? I'd like to still be able to trigger the Assistant with a button...

side note, button mapper pro is awesome. I can now trigger voice typing with a hardware button, before I'd have to re-enable the soft keyboard to do that!!
[Pixel C Android Development] :
Encryption is working just fine. Encrypted my tablet a week ago. Twrp can decrypt it and the rom is working like before. Tnx for the great work. If you need some help on the Developments you can ask me, I'm willing to help.
[Pixel C Android Development] tabormeister:
From Widevine news- does this mean we could maybe obtain an override?:

Device Revocation Override

A new API has been added to allow license generation for revoked devices (response status code = 127).

Widevine devices may be revoked due to non-compliance with our device robustness rules and rendered inactive. This feature is a prelude to the introduction of device security profiles, coming later in 2020.

This API is added to both the cloud license service and the license SDK, please refer to the latest documentation (v16.3.1) where specific use-cases are allowed to override revocation.
[Pixel C Android Development] j04nd03:
Apologies if I'm a bit dense, but does that mean that with the inclusion of ClearKey in the new build you already found and implemented the workaround for the hardware graphic acceleration you wrote about here? In other words, does HW acceleration for games still work with the new build, just not for Netflix (and other video streaming services like Disney+ or amazon Prime Video, I pressume)?

Thanks for your great work,

JD
[Pixel C Android Development] frov:
Well, this is unexpected: this works like a charm. Did not know of this and today started to dive a little deeper for my 'all stopped working PixelC':

now my TV works again (Ziggo in Netherlands) and Netflix. Thanks !!
[Pixel C Android Development] followmsi:
Unfortunately Widevine revocation needs to be triggered by device producer/vendor .. and not by "us".
[Pixel C Android Development] followmsi:
No .. still the same problem.

Clearkey is different DRM solution .. the last change was just an upgrade from version 1.0 to 1.2.

It's not used by Netflix and Co. - they use Widevine DRM.

Yes. HW acceleration is still working - I will not remove "liboemcrypto.so" lib from next lineage-17.1 builds.

For Netflix login process you will go for L3 .. and switch back to L1 later on.

This way you will keep HW acceleration working.
[Pixel C Android Development] followmsi:
Have made AOSP 11 test build for dragon some days ago .. still no time test it.

Not sure if it will boot at all .. and what is working.

You may like to play .. ?

aosp11_dragon-ota-eng.followmsi.zip

Cheers :p
[Pixel C Android Development] schoerb:
Thanks for the build. Unfortunately, the Pixel C does not boot up. But I tried to install it over LineageOS 17.1.

Also TWRP was replaced by the Google Recovery.
[Pixel C Android Development] Alxoom33:
Try factory wiping data.
[Pixel C Android Development] schoerb:
That does not help.

Unfortunately, the Android 11 ROM also flashed the Google Bootloader & Recovery.

I flashed the old Bootimage and TWRP and LineageOS 17.1 back...
[Pixel C Android Development] Alxoom33:
Thanks! I was planning on giving it a try.
[Pixel C Android Development] Alxoom33:
Anyone know of an Android 11 gapps package?
[Pixel C Android Development] lalala987:
Hi

Will just installing the zip Work, when coming from "pixelexperience-rom"?

I want to avoid deleting Data Partition...
[Pixel C Android Development] followmsi:
Thanks for report.

Only AOSP recovery will be installed .. Magisk normally prevents this kind of stuff.

Need to check logs for boot problems.

Custom dragon bluetooth implementation and custom drm_hwcomposer do have build issues on Android 11.

This are the known issues today .. maybe there are more problems when testing.

Not sure if I will spent time on AOSP.

Lineage started to merge several (important) changes for 18.0.

Maybe soon it's time for lineage-18.0 test build.

Cheers
[Pixel C Android Development] Alxoom33:
I should have just listened to your experience. Instead I wiped everything but internal storage and flashed. It bootlooped, never booted up. Went to reflash 17.1 and found it had aosp recovery. Adb/ fastboot is not recognizing my tablet. So I'm a brick until I can boot up TWRP.
[Pixel C Android Development] schoerb:
I had the same problem with Windows 10. So I used Linux Mint to get connected in fastboot mode:

https://qastack.com.de/android/46142/fastboot-doesnt-see-device
[Pixel C Android Development] Alxoom33:
Well I don't know how to work with linux. I am going to try and update the drivers. My computer still seeing my Pixel2 XL but not my Dragon?
[Pixel C Android Development] tabormeister:
I gave up on Windows and used MacOS, couldn't find a driver for fastboot.
[Pixel C Android Development] Alxoom33:
Didn't you need fastboot drivers for mac os?

---------- Post added at 09:50 PM ---------- Previous post was at 09:16 PM ----------

I still have an ancient iMac what do I do?
[Pixel C Android Development] tabormeister:
Download the Android sdk platform tools for Macos, then just cd to that unzipped location in terminal. Or you could use a Linux live boot if you don't want to install Linux
[Pixel C Android Development] followmsi:
Android 10 - October 2020

lineage-17.1-20201007-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> October 2020

- Switched to "unified" kernel.

- Patched framework/av to bring back "wifi-display" in android 10.

- Patched framework/base to support microG

- Latest LineageOS changes for Android 10

The ROM does contain it's own vendor.img !

Enjoy :p
[Pixel C Android Development] Alxoom33:
I am stuck with stock recovery and no TWRP. I can sidloade using adb from stock recovery. But I am not able to flash using fastboot. Is there a zip file available that I can sidload to install TWRP?

Thanks
[Pixel C Android Development] followmsi:
The first lineage-18.0 (test) build for dragon ..

There are quite some changes for Android 11 .. also kernel changes and new requirements.

https://source.android.com/setup/start/android-11-release

For the moment our kernel is still using "DebugFS" .. which is not "allowed" in Android 11.

I had to switch back to kernel based android lowmemory killer .. too many changes for userspace lmkd in Android 11.

Lineage has deprecated GCC compiler and forces CLANG compiler .. hope they bring back GCC compatibility again.

For the moment I do use dirty workaround to build kernel sources for boot.img.

Not sure about 3.4 kernel devices .. maybe Android 11 requirements are showstopper for some legacy devices.

As well I had to use a few more small hacks to make the build working .. lineage still needs to apply tons of fixes and changes.

This ROM has not been tested !

No idea what's working and if the system will boot at all.

lineage-18.0-20201009-UNOFFICIAL-dragon.zip

The Lineage installer does include "backuptools" already .. existing Gapps and Magisk installation should be restored.

Maybe you have to update to Magisk 21.x and maybe gapps for 10 will not be happy to be restored on 11.

The ROM does contain it's own vendor.img !

Happy testing !
[Pixel C Android Development] EnginEAR:
Tried... Didn't boot...

I tried installing and it didn't boot.

CM boot animation loop :(
[Pixel C Android Development] Grigori88:
I have the same problem.

Unknown device in fastboot mode.
[Pixel C Android Development] tabormeister:
Try Mac OS or Linux, wasn't able to get fastboot to recognize in Windows
[Pixel C Android Development] slash88:
Hi Followmsi,

Thanks for your work, i've installed it and everything is working like a charm!

---------- Post added at 03:24 PM ---------- Previous post was at 03:22 PM ----------

Same here, I had to use FWUL live iso (https://xdaforums.com/android/software-hacking/live-iso-adb-fastboot-driver-issues-t3526755) to get fastboot working.

Great tool btw, no linux knowledge is needed ;)
[Pixel C Android Development] tabormeister:
I need to make a flash drive of this, always forget until I need it lol
[Pixel C Android Development] _benedict_:
Hi!

I love the ROM and the successive versions have been my main driver for more than a year now :D

One issue that I have - and forgot to mention here ever since - is that the automatic brightness seems broken. Does anybody have the same experience?

Best,

benedict
[Pixel C Android Development] brackenhill_mob:
Most (all?) 3rd party Android 10 GSI's suffer from this. All my phones and Pixel C do.
[Pixel C Android Development] EnginEAR:
Retry

I'll try again sometime this week with:

https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-R/

I'll report if boot was successful.
[Pixel C Android Development] followmsi:
I have still not tested myself. ;(

Pls test if you can establish adb connection.

If possible, pls pull logcat when booting.

Thanks !
[Pixel C Android Development] bra1niac:
I finally got around to upgrading from the last official Lineage for dragon but I'm running into some issues. I downloaded the latest unofficial 17.1 image (lineage-17.1-20201007-UNOFFICIAL-dragon.zip). i'm following these steps for installing from another ROM just to start fresh with the new build.

Fresh Installation / Upgrade from any other ROM:

1. Boot into TWRP I'm using Lineage recovery

2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !) done, including formatting DATA

3. Install ROM.zip this goes fine

4. install gapps (arm64) here is where I fail, I get an error *** Incompatible Android ROM detected *** - This GApps pkg is for Android 10.0.x ONLY - Please download the correct version for your ROM; 11 (SDK 30)

So I never get to these steps...

5. install Magisk.zip (20.x+)

6. Wipe CACHE and DAVLIK

7. Reboot into system

I feel like I'm missing something here but I'm not sure what. Is using Lineage recovery an issue?

TIA!
[Pixel C Android Development] Peregr1ne:
trouble finding suitable USB drivers

Hi all,

After having run into the wrong-pattern-error and having had to reset my Pixel C I thought it was a good time to upgrade it to a more modern ROM, however I seem to get stuck rather early on: I have the impression that my windows pc does not recognise the tablet when in fastboot mode.

When (stock) Android is running on the tablet I can see and access the tablet from my pc, at this stage adb is working as well:

>adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully

This results in the tablet rebooting into fastloader, displaying the Google-coloured bar on top and saying "Waining for fastboot command...."

During the reboot, the PixelC usb device disppears from my device overview, and an Other Devices > Unknown Device (Location Port_#0009.Hub_#0001) appears in its place

When I give a command via the same shell on my pc that I used to reboot the tablet, I get:

>fastboot flash recovery twrp.img
< waiting for any device >

At this stage nothing happens anymore, I have the impression that both the pc and the tablet are waiting for eachother but cannot communicate.

I am running Win10x64 with an AMD CPU.

I have tried to install various drivers, all without result:

UniversalAdbDriver

Universal_Naked_Driver_0.73

usb_driver_r13-windows (downloaded from Google/Android dev pages)

usb_driver_r13-windows (via Android Studio)

None of these make the Unknown Device become more familiar to windows, also attempting to install the drivers from the Device Mgr > Other Devices > Unknown Device > Update Driver and pointing to the folders of above drivers did not work.

Searching the thread I found several suggestions (for instance ImjustSaiyan92, the download link doesn't seem to work anymore...) none have worked for me :mad::confused:

Is there an perhaps older version of the drivers that I need to use? Are the current versions not backward compatible?

Regards,

Peregr1ne
[Pixel C Android Development] bra1niac:
I'm having the same issue trying to replace the Lineage recovery with TWRP trying to resolve my issue in #1955 above. In addition to the latest Google USB driver (Windows 10) from the Google developer site as well as from Linux (Crostini) within two different Google Chromebooks. Windows 10 shows the tablet under "Other Devices" in Device Manager with no driver and trying to point it to the Google USB driver doesn't work. Linux/Crostini recognizes the Pixel C and lets you connect it to Linux, but fastboot just sits waiting to connect. Both gave the same results you described.
[Pixel C Android Development] Alxoom33:
Yes, I've been having the same issue for the last couple of weeks. Been able to sideload in stock recovery, but that's it! I was able to sideload LOS 17.1, but Icoulden't sideload Open Gapps for 17.1. So LOS is not working for me.

At least I've been able to run the Pixel C with a Dirty Unicorns A10 rom, kindly provided by [MENTION=5219016]Nych[/MENTION]itman, which included gapps that I was able to sideload. I'm planning to try to fastboot install or boot TWRP from my old iMac this weekend. I'll see if that works.
[Pixel C Android Development] schoerb:
I had the same problem. Please download a Linux Distribution like Mint or Ubuntu, make a live DVD or USB-Stick and follow this guide:

https://qastack.com.de/android/46142/fastboot-doesnt-see-device

This worked for me!
[Pixel C Android Development] bra1niac:
Thanks! While flashing to recovery didn't work for me from Crostini on a Chromebook, doing so from a Raspberry Pi that I had running next to me worked just fine. These are the relevant part of the instructions from that German page and should work fine from any Debian based distro (Raspbian or whatever its called now, Ubuntu, etc).

sudo apt-get update //updates apt get
sudo apt-get install android-tools-fastboot //installs fastboot
sudo apt-get install android-tools-adb //optionally get adb
sudo fastboot devices // should show the device, don't forget the sudo!!
sudo fastboot flash boot ~/pathto/boot.img //sudo is doing the trick here, which is missing on Windows !!