yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] followmsi:
I do have the same information like you ..

https://source.android.com/security/bulletin/2019-09-01#nvidia-components

"BootROM" sounds like to be fixed thru new bootloader version.

Maybe we get a final stock rom for dragon .. actually I doubt as support time is over now.

But you never know .. :p
[Pixel C Android Development] followmsi:
AOSP_10.0.0_r2_ALPHA2

I was able to trigger a new build .. remotely - and still no time to test myself.

DM-verity seems to be a requirement for "system-as-root" .. dragon does have "special" chrome os dm-verity version.

Tested to add "android dm-verity" into kernel .. but there are problems.

dragon kernel needs more/bigger changes to support both versions at the same time.

For next test build I will "try" to disable chrome os dm-verity completely and use "android" version instead, if required.

Not sure yet if we get it working for dragon device.

In the next time there will be more new "solutions" on how to make android 10 running on "older" devices, hopefully.

Luckily we use 3.18 kernel already .. not sure about the "very old" devices using 3.4 kernel .. etc.

We will see ..

AOSP_10.0.0_r2_ALPHA2_dragon-ota-eng.followmsi.zip

Changes:

- enabled dm-verity for system (chrome os version)

- enabled "system-as-root" config

- new kernel binary to support "skip_initramfs" .. etc.

Sources:

https://github.com/followmsi/android_device_google_dragon/tree/aosp-10

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel-10

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

If you test the ROM, please let me know your results .. problems are to be expected.

As I don't know myself when I will have the time to work on Android 10, pls don't ask for the next update.

Enjoy :p
[Pixel C Android Development] followmsi:
Not aware of any "big" changes for lineage-15.1 .. no device and kernel changes since months.

Does it work on previous ROM version .. from last month ?

When did the game stop to work .. just on latest build ?

Did you try with clean install too ?

Maybe other changes are related to your problems now ?

Pls post logs here before opening ticket at lineage.

Thx.
[Pixel C Android Development] xda_jm:
Made some more tests. Actually, it seems to be battery related.

When the battery is loaded at 100% it works nice. As soon as the battery is down to 55% or so, it starts stuttering and the game becomes unplayable.

Tested with old builds (4 weeks in the past), and same behavior. Just hadn't seen it.

Anything known in Android that does this? Can it be disabled? Strongly reminds me the Apple behavior where the cpu is trhottled with aging battery.
[Pixel C Android Development] Vartom:
I can’t understand why you turn on dm-verity and root=/dev/dm-0? We have already broken data encryption in 9.0
[Pixel C Android Development] followmsi:
Because I want to get it booting .. :)

As mentioned above .. and in link below .. dm-verity seems to be required for system as root.

https://source.android.com/devices/bootloader/system-as-root

Need to find correct "dm=" definition for "chrome os dm-verity" and system-as-root config.

Or switch to "android dm-verity" .. ?

https://github.com/followmsi/androi...ce7#diff-78ec901c9c29ef6a20b79592fd93f941R117

Or find any other solution .. or find switch to use "old" boot.img style ???

As I know, encryption of RW /data partition is different process as to verify hash value (dm-verity) on unencrypted RO /system partition.

Yes, gapps may have an issue.

No idea what happens if Magisk (with system-as-root support) will remove the "verify" flag in fstab.dragon ..

If you have any ideas on how to make it booting/working .. pls let me know.

Still did not test the ROM myself ..

Cheers
[Pixel C Android Development] locuturus:
I'm running LOS 16 and this sounds like the same problem I have. The system throttles the CPU and GPU pretty severely when the battery is below some amount. For me I usually experience problems around 70% battery but this is not consistent. You are not alone. Many of our tablets do this. Presumably a quality battery replacement would solve the issue but I am not aware of any such battery available to buy.
[Pixel C Android Development] ipdev:
I was hoping last month's unexpected update would have included a bootloader update. ;)

Maybe they would follow their own instructions for orange boot. (10 second delay.)

Hopefully they will surprise us again. :fingers-crossed:

As for AOSP_10.0.0_r2_ALPHA2 - I tested it last night.

ROM only = BootLoop. (Google SplashScreen -> Reboot -> SplashScreen -> Reboot ... )

ROM + Magisk = Stuck on Google SplashScreen.

Might not be getting to Boot animation but, at least it's not booting into fastboot. :D

Got a little sidetracked, last night, looking up somethings.

If I'm reading this part (correctly) source.android - boot.img

(and the part right above it) - Ramdisk

Non-A/B devices do not need a boot image ramdisk for 9 but, they do for 10?

When I unpacked ALPHA2 boot.img there was no ramdisk.

What about recovery, TWRP's mount points should be off or not work?

And now that I'm typing this, I just thought about vendor.

Sidenotes:

I have also test the ALPHA boot and vendor image(s) using AOSP's 10 GSI.

developer.android - GSI-10

(Same results by the way.)

Not sure if it will help but, Nexus 6P (angler) is going System as Root.

(Awhile back, most angler custom roms updated to use File Based Encryption.)

PixelExperience is currently SAR, and Statix looks to be soon.

Cheers.
[Pixel C Android Development] tschmid:
https://www.ifixit.com/Answers/View/536928/Where+can+I+find+a+battery+replacement

https://www.google.com/search?q=C15...9i57.1046j0j7&sourceid=chrome-mobile&ie=UTF-8

Hope you find one
[Pixel C Android Development] followmsi:
Thanks for testing - again !

Also here ..

https://source.android.com/devices/bootloader/system-as-root

In Android 10, the root file system is no longer included in ramdisk.img and is instead merged into system.img (that is, system.img is always created as if BOARD_BUILD_SYSTEM_ROOT_IMAGE was set). Devices launching with Android 10:

Use a system-as-root partition layout (automatically enforced by the build with no options to change the behavior).

Must use a ramdisk, which is required for dm-linear.

Must set BOARD_BUILD_SYSTEM_ROOT_IMAGE to false. This setting is used only to differentiate between devices that use a ramdisk and devices that don't use a ramdisk (and instead mount system.img directly).

The meaning of a system-as-root configuration differs between Android 9 and Android 10. In an Android 9 system-as-root configuration, BOARD_BUILD_SYSTEM_ROOT_IMAGE is set to true, which forces the build to merge the root file system into system.img then mount system.img as the root file system (rootfs). This configuration is mandatory for devices launching with Android 9 but is optional for devices upgrading to Android 9 and for devices running lower versions of Android. In an Android 10 system-as-root configuration, the build always merges $TARGET_SYSTEM_OUT and $TARGET_ROOT_OUT into system.img; this config is the default behavior for all devices running Android 10.

"BOARD_BUILD_SYSTEM_ROOT_IMAGE =: false" will trigger creation of "mini" ramdisk in boot.img .. new in Android 10. (ALPHA1)

"BOARD_BUILD_SYSTEM_ROOT_IMAGE =: true" will not trigger creation of ramdisk in boot.img - just kernel binary .. same like in Android 9 already. (ALPHA2)

For testing you should be able to switch/change boot.img from ALPHA1 with ALPHA2 and vice versa.

GSI normally requires "treble-ized" vendor and kernel .. etc. .. we do not setup (full) treble for Pixel C - it's non treble device.

TWRP

Made a new "SAR - system-on-root" version for dragon device - needs testing too.

twrp-3.3.1-0-dragon-SAR.img

Based on omnirom 9.0 sources and latest TWRP sources .. added SAR config too.

https://github.com/followmsi/androi...mmit/6c550fcf3ffa85a0a1d1d23e91ffd3e9438b785d

PE angler is using the "standard" system-as-root setup ..

https://github.com/PixelExperience-...mmit/b34ca625f05d991fe8fdc868ad17e1620874a9c4

But they use also "standard" android dm-verity version ..

https://github.com/PixelExperience-Devices/device_huawei_angler/blob/pie/BoardConfig.mk#L51

We may need to test "android dm-verity" in dragon kernel .. if possible.

Cheers
[Pixel C Android Development] Vartom:
I see one mistake. You register the command line parameters and use the prebuild kernel with the command line already generated during assembly. Accordingly, your addition may not work.

Ps. It seems to me that you need to first implement support for the system as root in 9.0, and only then go to 10. This will allow sharing the task of launching a new version of android.
[Pixel C Android Development] followmsi:
Where do you define cmdline paramter for kernel binary while compiling ?

I do not have cmdline parameter in kernel config. (CONFIG_CMDLINE)

Do you ?

The required creation of image.fit is special for dragon device .. used for chrome os signing .. on top of any other stuff.

Normally no cmdline config/parameter either.

As well .. you can extract boot.img and you will see the "correct" cmdline .. the new stuff is included.

For example Nexus 10 kernel does have problems to use cmdline parameter from android (BOARD_KERNEL_CMDLINE)

This kernel requires cmdline parameter inside kernel config. (CONFIG_CMDLINE)

Until now we never had to add any kind of cmdline config for dragon kernel .. we will see how it goes.

Have a try to make it working on Android 9.0 .. I will test on 10 :p

I have made new prebuilt kernel and switched to android dm-verity now ..

Adjusted device tree too ..

https://github.com/followmsi/android_device_google_dragon/commits/aosp-10

Hopefully I can schedule a new test build for tomorrow.

Cheers
[Pixel C Android Development] Vartom:
https://github.com/followmsi/androi.../arm64/boot/dts/tegra/tegra210-smaug.dtsi#L22

---------- Post added at 02:23 AM ---------- Previous post was at 02:10 AM ----------

With this approach, you will poke into the blind for a very long time until you get tired or a miracle happens (launch). You don’t even look at the logs ...
[Pixel C Android Development] followmsi:
Yes .. I missed the .dts file .. Thanks.

Pls don't mell me about approach .. start to build android 9.0 and let me know your results.
[Pixel C Android Development] xda_jm:
Won't work over here in Europe...

Thing is - If I can't get this fixed, I'll change Tablet. But there is barely another recent Tablet running LOS...
[Pixel C Android Development] tschmid:
Sad im also from Europe, switzerland exactly

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] followmsi:
AOSP_10.0.0_r2_ALPHA3

The last build for the next time .. will it boot or not boot ? :D

Hope to find a time slot on the weekend .. to finally test myself.

AOSP_10.0.0_r2_ALPHA3_dragon-ota-eng.followmsi.zip

Changes:

- switched to android dm-verity - in device and kernel sources.

- switched to permissive selinux for testing

- new kernel binary for android dm-verity .. etc.

Sources:

https://github.com/followmsi/android_device_google_dragon/tree/aosp-10

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel-10

TWRP

Made a new "SAR - system-on-root" version for dragon device - needs testing too.

twrp-3.3.1-0-dragon-SAR.img

Based on omnirom 9.0 sources and latest TWRP sources .. SAR config ..

https://github.com/followmsi/androi...mmit/6c550fcf3ffa85a0a1d1d23e91ffd3e9438b785d

Since android 9.0 we need to build and include vendor.img into ROM installer .. same for Android 10 now.

If you test the ROM, please let me know your results .. problems are to be expected.

As I don't know myself when I will have the time to work on Android 10, pls don't ask for the next update.

Enjoy :p
[Pixel C Android Development] ipdev:
Whoops. :o

Apparently I never check for treble on this device.

SAR TWRP is adb secure.

- adb sideload option works.

- Magisk failed to mount system.

Magisk mounting error is odd.

ALPHA3 (Both Standard and SAR TWRP)

Google SplashScreen -> Recovery.

Actually expected this.

Sidenote:

(Late night testing.)

Tonight was ALPHA3 and a repacked TWRP-SAR

ro.secure=0, ro.adb.secure=0, ro.debuggable=1

I tried to get passed the Magisk error by

bind mount system_root/system to system/

It breaks adb sideload. If I push Magisk to internal and then bind mount system, Magisk still fails to install.

Last night's testing was with the newer kernel and ALPHA1/ALPHA2.

Used AnyKernel3 to flash Image.fit

Cheers. :cowboy:

PS.

It's late again for me, I'm tired so I hope this post isn't confusing. :)
[Pixel C Android Development] Vartom:
[/COLOR [MENTION=5480152]followmsi[/MENTION] On AOSP 9, the system as root configuration failed to be verified. I downloaded the source 10 I will try immediately on it.

ps AOSP 10. BOARD_BUILD_SYSTEM_ROOT_IMAGE := false set this flag and the system gives launch logs. But there are problems with the graphics drivers.
[Pixel C Android Development] Vartom:
AOSP 10 is starting up. We need gapps.
[Pixel C Android Development] followmsi:
Big thanks for all your testing !!!

For the TWRP build I have used wrong script .. and made "userdebug" instead of "eng" build.

Made new SAR version .. and one "normal" version too .. both as "eng" build now ..

twrp-3.3.1-1-dragon-SAR.img

twrp-3.3.1-1-dragon.img

Cheers
[Pixel C Android Development] followmsi:
Big thanks for testing on android 9 .. I see below -- you managed to boot up - COOL !

What did you do now ?

Kept all the dm-verity stuff and mount points .. but just set "BOARD_BUILD_SYSTEM_ROOT_IMAGE := false" only ?

Or did you remove all the system-as-root config too ?

What did you do for the grahics driver issue in logs ?

Thanks !
[Pixel C Android Development] Vartom:
just set "BOARD_BUILD_SYSTEM_ROOT_IMAGE := false".

In the kernel, I did not add anything for dm and systems as root.

To solve problems with graphics, added nvidia nouveau firmware to the kernel. For assembly I had to replace the source with hwcomposer, libdrm.

Is there where to download gapps for 10?
[Pixel C Android Development] followmsi:
Ok .. just to "false" - even better !

How did you include nvidia drivers into kernel ? .. You mean into boot.img ?

We did this all the time for dragon .. thru PRODUCT_COPY_FILES into rootfs .. How did you do it for 10 now ?

Pls push device tree to your Github.

Thanks a lot !
[Pixel C Android Development] Vartom:
How did you include nvidia drivers into kernel ?

CONFIG_EXTRA_FIRMWARE="nvidia/tegra210/xusb.bin nvidia/tegra210/bpmp.bin nouveau/acr_ucode.bin nouveau/fecs.bin nouveau/fecs_sig.bin nouveau/gpmu_ucode_desc.bin nouveau/gpmu_ucode_image.bin nouveau/nv12b_bundle nouveau/nv12b_fuc41ac nouveau/nv12b_fuc41ad nouveau/nv12b_fuc409c nouveau/nv12b_fuc409d nouveau/nv12b_method nouveau/nv12b_sw_ctx nouveau/nv12b_sw_nonctx nouveau/pmu_bl.bin nouveau/pmu_sig.bin"

---------- Post added at 07:12 PM ---------- Previous post was at 07:06 PM ----------

In AOSP 10 No sound. The video does not play. It is necessary to search and edit the config.
[Pixel C Android Development] followmsi:
Nice way to include the "problem" driver into kernel. Cool !

Did you change fstab.dragon in device tree at all .. mount point is still pointing to /system ?

Did you made selinux permissive or enforcing ?

Will trigger a new build later on .. when the kids are sleeping :)

Cheers
[Pixel C Android Development] Vartom:
This was faster than looking for options on how to add this to ramdisk.

Did you change fstab.dragon in device tree at all .. mount point is still pointing to /system ?

I have been mounting for a long time in DT. https://github.com/vartom/android_k.../arm64/boot/dts/tegra/tegra210-smaug.dtsi#L18

Did you made selinux permissive or enforcing ?

set to androidboot.selinux=permissive just in case.
[Pixel C Android Development] followmsi:
Thanks for the infos .. made a new build now.

Did not used "early boot" in dts file .. yet.

Now it's time to stop Android and have a sleep ..
[Pixel C Android Development] followmsi:
AOSP_10.0.0_r2_ALPHA4

Thanks to [MENTION=6556709]Vartom[/MENTION] for testing, building and help !

[MENTION=7280276]ipdev[/MENTION] .. if you go for no. 4 .. pls let me know your results !

AOSP_10.0.0_r2_ALPHA4_dragon-ota-eng.followmsi.zip

Changes:

- removed dm-verity stuff again

- still permissive selinux for testing

- new kernel binary to include required tegra drivers (previously in ramdisk part of boot.img)

Sources:

https://github.com/followmsi/android_device_google_dragon/tree/aosp-10

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel-10

Since android 9.0 we need to build and include vendor.img into ROM installer .. same for Android 10 now.

If you test the ROM, please let me know your results .. problems are to be expected.

As I don't know myself when I will have the time to work on Android 10, pls don't ask for the next update.

Enjoy :p
[Pixel C Android Development] Grigori88:
How to install AOSP_10.0.0_r2_ALPHA4_dragon?

I have a problem with this.
[Pixel C Android Development] Vartom:
Describe the problems.
[Pixel C Android Development] followmsi:
Sorry .. not your fault.

It does not boot. .. will remove it from gdrive later on.

Kernel requires fstab in dts file .. and some more changes for graphics stuff.

Finally did test myself :)
[Pixel C Android Development] 12paq:
[MENTION=5480152]followmsi[/MENTION] I have a 2nd Pixel C here that I could devote to testing your A10 builds. I also can pull logs etc. I would be happy to help.
[Pixel C Android Development] followmsi:
AOSP_10.0.0_r2_BETA1

Let's call it BETA1 .. :p

It finally boots .. but there are still a lot of issues.

AOSP_10.0.0_r2_BETA1_dragon.followmsi.zip

Changes:

- it finally boots .. bloody "libvulkan" was the reason for all the problems.

- back to enforcing selinux mode - due to "stange" wifi issue .. same on pie.

- new kernel binary to remove selinux stuff from dts file in kernel.

Whats works .. (quick testing)

- Audio

- Wifi

- Play Video thru builtin webviewer .. not at real browser .. but youtube.com works.

What is not working (also quick testing.. )

- Bluetooth is crashing like hell .. as it looks like it pulls down standard "android.phone" process too - > we are in "RescueParty" mode !

- HW video decoding seems to have issues .. vulkan stuff needs testing too.

- Sensors .. (roatation does not work . .etc.)

. etc .. and maybe more ..

TWRP & Magisk & Opengapps

- Newer TWRP 3.3.1-1 (gdrive folder) seems to detect "system-as-root" partitions in Android 10 differently as "older" official TWRP version. (3.3.1.-0)

- The TWRP "SAR" version seems not to required .. either gapps and twrp are adjusting sources to make it working the "old" way.

- For now I have used the gapps version from [MENTION=6556709]Vartom[/MENTION] -> https://xdaforums.com/showpost.php?p=80240483&postcount=28

- If you want to install the gapps package from vartom .. pls use "official" TWRP version and mount system in TWRP before installation.

- Magisk 19.3 does install properly on newer TWRP version but is still bootlooping !!

- Maybe newer Magisk canary build is reqiured .. or maybe some "flags" for Magisk to make it working for dragon device - pls test and report !

- We need proper Opengapps version .. and no time build myself this time !

- Nezorflame is doing good job at opengapps ... in his private repo the "ten" sources are ready to test ...

-> https://github.com/nezorflame/opengapps/tree/ten -- pls feel free to build "unoffical" gapps .. you need some diskspace and time.

Workarounds !!!

- After ROM installation .. mount system partition in TWRP ..

- Remove "/system/system/app/Bluetooth/Bluetooth.apk" - to prevent warnings all the time in GUI.

- This can be done at any time - depends on your personal stress level.

- Magisk is preventing the "standard" AOSP way of replacing recovery image .. TWRP is gone after you install this ROM.

- For this reason we remove .. "/system/system/recovery-from-boot.p" via TWRP too.

- I have restored old AOSP backup from Pie and it worked very well .. needs more testing but all the apps are running.

Sources:

https://github.com/followmsi/android_device_google_dragon/tree/aosp-10

https://github.com/followmsi/android_kernel_tegra/tree/followmsi-kernel-10

Since android 9.0 we need to build and include vendor.img into ROM installer .. same for Android 10 now.

If you test the ROM, please let me know your results .. problems are to be expected.

As I don't know myself when I will have the time to work on Android 10, pls don't ask for the next update.

Enjoy .. :p
[Pixel C Android Development] 12paq:
[MENTION=5480152]followmsi[/MENTION] thanks for all your efforts and time.

Yeah, Magisk Canary is needed for Android 10.

On Pixel phones, it also helps to have Canary Debug Magisk Manager with the latest Magisk Canary (19.4, 19309) installed on Pie prior to going to A10.

I will test beta 1 with Magisk tonight on my spare Pixel C.

Edit: the latest Magisk 19.4 is out of canary and said to work for A10. I have not tested it. But the commits on his git look the same.
[Pixel C Android Development] Vartom:
I proposed an alternative solution to the problem with blobs for the vulkan "libvulkan" when I switched from 8.x to android 9, but you chose your solution. https://github.com/vartom/proprietary_vendor_nvidia/commit/ce57c814fc16299b9d4a7e047d37b0e82ca11146

The problem in our case with "system-as-root" will most likely always be, since at the current moment we have android 10 without using "system-as-root". This means that all gapps/Magisk officially released for android 10 will search to use "system-as-root" and not find our partition with the system.
[Pixel C Android Development] followmsi:
Yep .. SAR for 10 will be implemented by gapps, twrp .. and Magisk as well.

Made a quick test for Magisk 19.4 today .. it's booting now .. it's removing recovery override .. etc.. -> but no ROOT access.

Have a look here ..

https://github.com/topjohnwu/Magisk/issues/1838#issuecomment-530967281

Maybe fstab in dts is blocking proper rooting .. no idea.

Cheers
[Pixel C Android Development] followmsi:
AOSP_10.0.0_r2_BETA2

A quick BETA2 to fix Bluetooth !

Actually bluetooth was no dragon device problem at all .. general problem in /system/bt sources.

Fixed in lineage-17.0 sources.

Added frameworks/av patches too .. graphics and especially camera are still not working.

DRM / Graphics is still a mess.

Tracked /bionic .. to support shim libs.

Made manifest for current status .. now you can build yourself :)

https://github.com/followmsi/manifests/tree/dragon-aosp-10

BETA2 will be the last build for the next time .. maybe an early lineage-17.0 :p

AOSP_10.0.0_r2_BETA2_dragon.followmsi.zip

Whats works .. (quick testing)

- Audio

- Wifi

- Play Video thru builtin webviewer .. not at real browser .. but youtube.com works.

- Bluetooth is working now .. tested to pair and listen music.

What is not working (also quick testing.. )

- DRM/HW video decoding seems to have issues .. vulkan stuff needs testing too.

- Sensors .. (roatation does not work . .etc.)

. etc .. and maybe more ..

TWRP & Magisk & Opengapps

- Tested Magisk 19.4 BETA .. it removes stock recovery restore and it does boot finally - but no root access.

- Unofficial Opengapps builds are welcome :)

Sources:

https://github.com/followmsi/manifests/tree/dragon-aosp-10

Since android 9.0 we need to build and include vendor.img into ROM installer .. same for Android 10 now.

If you test the ROM, please let me know your results .. problems are to be expected.

As I don't know myself when I will have the time to work on Android 10, pls don't ask for the next update.

Enjoy .. :p
[Pixel C Android Development] Vartom:
How did you check the sound? put your beta2 and no sound.

I also don’t like this kind of error plan

09-20 00:22:28.626 230 230 E /vendor/bin/hw/android.hardware.graphics.allocator@2.0-service: Failed to get IAshmemDeviceService.