[ROM][UNOFFICIAL][LineageOS][19.1][dragon] -> 2023-01-11 (DISCONTINUED)

[cognitivedesires]

DFS channels still don't work.
I've changed the region in system - advanced to US rebooted, checked, changed back to EU, rebooted.

But that's the only bad bug/feature.
The rom is fast and smooth.
Thank you for your time and effort.

Is the camera working on Pixel C

 

[BartKey]

Is the camera working on Pixel C

Camera doesn't work on Android 12 custom roms for pixel c

 

[cognitivedesires]

Camera doesn't work on Android 12 custom roms for pixel c

Should I wait for Android 13 ROM then?

 

[BartKey]

Should I wait for Android 13 ROM then?

Don't know, I'm only end user, no developer. Let's hope the developer can fix the camera.

 

[tabormeister]

Problem is proprietary Nvidia blobs. Basically needs redone from scratch .... @michie has been doing some magic porting things from Shield TV though, so you never know.

 

[ndrs81]

Hello fellow Pixel C fans,

I've installed the Rom on my trusty Pixel C and noticed the physical keyboard is not mapped correctly. I had the same probem running PixelExperience btw. I'm using the german keyboard layout and ö, ä and ü files are not mapped right. ü = ´, shift + ü = ` and alt gr + ü does nothing but should be +. Ö and Ä do work but their alt gr functions are missing (should be ' for ö and # for ä). Any chance this can be fixed somehow?

Thanks for keeping the Pixel C alive!

Regards

Andy

 

[followmsi]

The lastest update seems to have am issue playing 60fps content. Basically the same issues listed in your crdroid forum. When interacting with the tablet via volume controls or something in the app playing content, the fps is normal. Otherwise it stutters

Did this problem start with September build ?
Both August builds did not have this "60fps" problem ?

 

[followmsi]

lineage-19.1 - October 2022

There is still some strange "60fps" stuttering .. The last device and kernel changes were made in August .. to test the changes from michie.
Maybe some lineage patches are related .. need to check and find the root cause.

lineage-19.1-20221010-UNOFFICIAL-dragon.zip

Changes:
- Google security updates -> October 2022
- Patched system/netd to bring back Network traffic monitoring on older kernels.
- Patched frameworks/base & Permissions to support microG
- Latest LineageOS changes

As SDK level increased to version 32 we have to use new gapps for Android 12L.
Pls check latest gapps builds here ..
https://drive.google.com/drive/folders/1O-I01LDvno57ztnxIW_bSnVWEk8-6Ics
Thanks to @ipdev for the opengapps packages !

Tested with Magisk 25.2 !

Enjoy Android 12L

 

[followmsi]

lineage-19.1 - October 2022 - Part 2

This build should fix the "60fps" issue ..

lineage-19.1-20221019-UNOFFICIAL-dragon.zip

Tested with Magisk 25.2 !

Enjoy Android 12L

 

[Papaw01]

lineage-19.1 - October 2022 - Part 2

This build should fix the "60fps" issue ..

lineage-19.1-20221019-UNOFFICIAL-dragon.zip

Tested with Magisk 25.2 !

Enjoy Android 12L

Since the recent builds need a new gapps, can we still dirty flash?
thanks for you hard work!

 

[_benedict_]

For those of you who made the jump to Android 12/12L, how good is it? Have some spare time in the weekend and planning to upgrade

 

[followmsi]

Since the recent builds need a new gapps, can we still dirty flash?
thanks for you hard work!

All 12L builds will need 12L gapps !

Otherwise go for it .. dirty upgrade from previous build should work without problems .. I did the same.

 

[EnginEAR]

For those of you who made the jump to Android 12/12L, how good is it? Have some spare time in the weekend and planning to upgrade

I've been on the latest build since it was out.
Smooth and no complaints.

 

[_benedict_]

I updated and am now enjoying a very smooth experience with Android 12. Thank you @followmsi !

 

[_benji]

Hello fellow Pixel C fans,

I've installed the Rom on my trusty Pixel C and noticed the physical keyboard is not mapped correctly. I had the same probem running PixelExperience btw. I'm using the german keyboard layout and ö, ä and ü files are not mapped right. ü = ´, shift + ü = ` and alt gr + ü does nothing but should be +. Ö and Ä do work but their alt gr functions are missing (should be ' for ö and # for ä). Any chance this can be fixed somehow?

Thanks for keeping the Pixel C alive!

Regards

Andy

Hi,
I also see the same issue on my Pixel C with the german Pixel C Keyboard. Looks like its missing the correct keyboard layout. https://github.com/followmsi/android_device_google_dragon already contains an App called DragonKeyboard, and this does contain the correct .kcm keyboard layout file for the Pixel C Keyboard (res/raw/keyboard_layout_german.kcm) but this seems to get overriden by the version provided by InputDevices.apk, which contains a different mapping not suitable for the PixelC keyboard.

As a workaround I used https://exkeymo.herokuapp.com/ to provide an additional layout containing the correct mapping (copied from here: https://github.com/followmsi/androi...ard/res/raw/keyboard_layout_dragon_german.kcm), but of course it would be nice to have this active by default.

 

[_benedict_]

Hi,

LineageOS 19 has also installed Lineage Recovery, while I am pretty sure I did not approve to.
Did I miss something in the installation process?

 

[ndrs81]

Hi,
I also see the same issue on my Pixel C with the german Pixel C Keyboard. Looks like its missing the correct keyboard layout. https://github.com/followmsi/android_device_google_dragon already contains an App called DragonKeyboard, and this does contain the correct .kcm keyboard layout file for the Pixel C Keyboard (res/raw/keyboard_layout_german.kcm) but this seems to get overriden by the version provided by InputDevices.apk, which contains a different mapping not suitable for the PixelC keyboard.

As a workaround I used https://exkeymo.herokuapp.com/ to provide an additional layout containing the correct mapping (copied from here: https://github.com/followmsi/androi...ard/res/raw/keyboard_layout_dragon_german.kcm), but of course it would be nice to have this active by default.

Thanks, that looks promising!

I'll give that a try when I get home.

 

[jwhan]

Hi, I want to ask a dumb question. Please forgive my ignorance. How to change the command kernel command line parameter. BTW I am work on lineage-17.1 branch of your kernel repo.
I want to add the console=tty0 to kernel command line parameter. Till now, I've tried three way but none of them worked.

1. Modify the device/google/dragon/BoardConfig.mk.
BOARD_KERNEL_CMDLINE += console=tty0

2. Insert these line to kernel/google/tegra/arch/arm64/configs/lineageos_dragon_defconfig
CONFIG_CMDLINE="console=tty0"
CONFIG_CMDLINE_EXTEND=y

3. Modify the kernel/google/tegra/arch/arm64/boot/dts/tegra/tegra210-smaug.dtsi

chosen {
#ifdef CONFIG_KASAN
            bootargs = "cros_legacy console=ttyS0,115200n8 init=/init rw kgdboc=ttyS0 earlycon=uart8250,mmio32,0x70006000 ignore_loglevel=1 drm.atomic=1 firmware_class.path=/vendor/firmware kern_guid=%U no_console_suspend";
#else
            bootargs = "cros_legacy console= init=/init rw ignore_loglevel=1 drm.atomic=1 firmware_class.path=/vendor/firmware kern_guid=%U no_console_suspend androidboot.selinux=permissive androidboot.hardware=dragon";
#endif
};

to

        chosen {
#ifdef CONFIG_KASAN
        bootargs = "cros_legacy console=ttyS0,115200n8 init=/init rw kgdboc=ttyS0 earlycon=uart8250,mmio32,0x70006000 ignore_loglevel=1 drm.atomic=1 firmware_class.path=/vendor/firmware kern_guid=%U no_console_suspend";
#else
        bootargs = "cros_legacy console=tty0 init=/init rw ignore_loglevel=1 drm.atomic=1 firmware_class.path=/vendor/firmware kern_guid=%U no_console_suspend androidboot.selinux=permissive androidboot.hardware=dragon";
#endif
    };

But all I get is just this
[ 0.000000] Kernel command line: cros_secure [email protected] cros_legacy console= init=/init rw ignore_loglevel=1 drm.atomic=1 firmware_class.path=/vendor/firmware kern_guid=bc81152b-b527-4ab1-9cf1-c39104dffc12 no_console_suspend androidboot.selinux=permissive

As we can see, there is no value on console key. Am I do something wrong?

 

[_benedict_]

Hi!
USB file transfer doesn't seem to work for me. Tried different ports or different cables. Has anyone tested it?

 

[heyChristo]

Hi!
USB file transfer doesn't seem to work for me. Tried different ports or different cables. Has anyone tested it?

Mine hasn't worked for years now. I gave up and have to download everything to the tablet.