yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] followmsi:
Systems sounds are not working ..but spotify and movies via kodi and vlc are working .. Or YouTube in browser.

The same sounds work via Bluetooth too.

Will check logs for graphics stuff next time .. I want to have root .. To be able check logs online .. etc. :)

Removed fstab from kernel again ...

https://github.com/followmsi/androi...mmit/0cf468ec94f20dad1dc6135ecaf9e8ec4c3c7e98

This way it should work for other "legacy" devices too !

Magisk is working on a-only android 10 way to root ... 2SI ..

https://mobile.twitter.com/topjohnwu/status/1174392832007667712

Cheers
[Pixel C Android Development] 12paq:
For testing Beta 2, what Gapps and TWRP versions are required now? TWRP 3.3.1-1 and Vartom's Gapps?

Thanks
[Pixel C Android Development] followmsi:
Both TWRP versions are ok .. there are no other gapps - at least I did not search nor build.
[Pixel C Android Development] followmsi:
This is a lineage thread .. for this reason - let's start the lineage testing :p

Same as for AOSP .. the first build - we have to see whats broken - and how to fix.

Just realized that device rotation (sensors) seems to work in lineage .. and we have switched to permissive selinux.

Happy testing !

lineage-17.0-20190920-UNOFFICIAL-dragon.zip

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:
Lineage 17 is booted with OpenGApps Nano.

open_gapps-arm64-10.0-nano-20190920-UNOFFICIAL

twrp-3.3.1-1-dragon

For some reason, I had to flash the boot.img after the system/vendor install to get it to boot. (I just flashed boot.img using fastboot.)

OpenGApps has 10.0-nano test builds for arm and arm64.

OpenGApps SourceForge - Link

Note:

TWRP-SAR didn't work for me. Seemed to be mount issues with system_root and system.

TWRP-> Mount showed system_root instead of system.

After installing los17 and rebooting to recovery(SAR) TWRP-> Mount showed system.

Regardless, system(or system_root) was empty or could not be mounted.

Will have time tomorrow to do some more testing.

Have some recovery logs but, I'm not sure if the problem is TWRP, install or GApps.

Note 2:

I have now come to despise this error. It seems to be following me.

(fajita, mata, bonito and now (ryu)dragon. There are some workarounds.)

linker: Warning: couldn't read "/system/etc/ld.config.txt" for "/sbin/busybox" (using default configuration instead): error reading file "/system/etc/ld.config.txt": Too many symbolic links encountered

Cheers. :cowboy:

Quick-Edit.

After installing and booting LOS17, the TWRP-SAR gave me less errors.

ADB push locked up with regular and SAR TWRP. Rebooting into system and pushing files to /data/local/tmp. Then back in TWRP (regular) linker error, when moving the files from /data/local/tmp to /system/system/priv-app. SAR version I was able to mv files to /system_root/system/priv-app.
[Pixel C Android Development] Vartom:
Found how to fix this constant fall.

You need to change the value from false to true in these variables

https://github.com/followmsi/androi...works/base/core/res/res/values/config.xml#L23

https://github.com/followmsi/androi...works/base/core/res/res/values/config.xml#L26

Perhaps only the first is enough, I have not tested this option.
[Pixel C Android Development] Burakki:
Hi,

thank you for your labor

rom installed after all wipes.

recommended open gapps tests

Fast analysis:

Overall the rom works well.

Only a few lags occasionally detected.

The volume, on the other hand, does not work as if it were preset and cannot be changed
[Pixel C Android Development] followmsi:
Again -- big thanks for your testing and reporting !

And big thanks for the link to gapps .. they work wonderful - no setupwizard crashes .. like in early Oreo/Pie.

Made dirty upgrade from Pie as well .. also ok !

Tested both AOSP and Lineage-17.0 .. I am really happy with this version until opengapps goes official.

Forget about SAR TWRP version :p

I did made all my tests with "normal" versions .. tested both - official (3.3.1-0) and unofficial (3.3.1-1).. no difference for me.

And I can always mount system partition .. no problems here.

When I did play in system and vendor thru adb in recovery I used the "real" file location and not the "symlink".

This is error message about .. maybe busybox needs some changes.

But I did not play in "priv-app" .. :)

Tested clean install a few times .. never had to reflash boot.img to get it booting .. you may did play with magisk 19.3 ?

If you copy Rom and boot.img into your "/sdcard/Download" folder you can always flash boot.img inside TWRP - no need for cable connection and fastboot.

Only if TWRP got lost you will need to get the cable ;)

Cheers
[Pixel C Android Development] followmsi:
Thanks for checking ..

Similar like the Bluetooth problem -> in this case it's again a "general" issue in /frameworks/opt/telephony ..

https://review.lineageos.org/c/LineageOS/android_frameworks_opt_telephony/+/258536

Not merged in to lineage-17.0 yet !

But already included into my lineage-17.0 build .. and it's part of new AOSP BETA3 ;)

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

One more AOSP build ..

AOSP_10.0.0_r2_BETA3_dragon.followmsi.zip

Changes:

- New kernel: some patches from [MENTION=6556709]Vartom[/MENTION] .. latest wireguard version and back to "permissive" selinux.

- Rotation is working again -> selinux issue

- fix for android.phone.com -> as it looks like we left "RescueParty" mode !

( https://review.lineageos.org/c/LineageOS/android_frameworks_opt_telephony/+/258536 )

- fixed fingerprint -> no warning after boot anymore -> required for Magisk SafetyNet as well. (when we get Magisk "2SI" Support for A-only.)

( https://github.com/followmsi/platform_build/commit/95aa63802d14b17f9bc09db43fa6d835fa101caf )

- Removed fstab from kernel binary and switched to "first_stage_mount" ..

( https://github.com/followmsi/androi...mmit/0cf468ec94f20dad1dc6135ecaf9e8ec4c3c7e98 )

Whats works ..

- Audio (partly only)

- Wifi

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

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

- Sensors (rotation is working now - selinux issue) - needs more testing.

What is not working .. )

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

- Audio (you can not change volume) . .etc.

- And maybe more !?!

TWRP & Magisk & Opengapps

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

- "2SI" support is coming soon .. https://twitter.com/topjohnwu/status/1174392832007667712

- Tested the unofficial nano opengapps -> https://sourceforge.net/projects/opengapps/files/arm64/test/

Works good on AOSP and lineage-17.0 too.

For clean install I did skip all steps in setupwizard.

As well I made dirty upgrade from Pie - no crashes so far.

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] ipdev:
Good News. :D

Today's Magisk Canary works with A-Only SAR.

We have root on Lineage17 and AOSP_10. :)

magisk-canary GitHub - Link

The UI is f'd in AOSP_Beta_3 when magisk is installed.

Stabilizes for a little while then becomes glitchy again.

Lineage 17 on the other hand is smooth and so far no ill side-effects yet.

Cheers All. :cowboy:

Edit:

Quick Update.

Magisk canary files have moved.

magisk-canary GitHub - Link
[Pixel C Android Development] followmsi:
Thanks for testing !

Yeah, TWRP version based on Pie seems to have some busybox issues ..

busybox have had compiling problems - "should be fixed" (TWRP sources.)

Official TWRP version is still based on CM-14.1 and Nougat busybox sources.

Not sure if you dump boot partitioin correctly .. if you remove chromes os header in boot.img it will not work/boot.

You can quickly check in editor .. needs to start with .. "CHROMEOS" .. for other devices you will see "ANDROID" ..

Good News !

Will test them soooon ..

Cheers
[Pixel C Android Development] 12paq:
Okay! I've got the latest Los 17 beta flashed rooted and running with nano gaaps for A10.

Magisk 19.5 for root and superuser seems to work fine. The apps Root Explorer, titanium backup, substratum light, and Swift theme installer, all gained root access and run perfectly. Quite the surprise. I thought I would have much more problems with root and root access. However it seems to be running very well.

When flashing LOS 17 and nano gapps for A10, using TWRP 3.3.1-1, LOS installed fine but nano gapps failed with "can't find build.prop" error. However, when I switched to TWRP 3.3.1-1 SAR (flashed to SAR easily from within TWRP), then nano gaaps intalled without an error.

Darn near a daily driver for me. I have not tested Bluetooth. Will do soon. I did notice with gboard voice to text is broken. I'll keep hunting for more bugs and report them if needed.

Thanks for the test builds! This is fun.

Edit: Known issues still broken: youtube videos in app, videos broken in other apps, no audio system wide (so far). Microphone works for Google app search, however not for voice to text on Gboard. So microphone is not broken completely

Edit: Casting audio from Play Music works, however will not play on device (known issue)

Edit: In news apps, video plays for ads with no audio. Non ad videos do not stream. Tested several apps that play video.

Edit: Magisk module "Busybox for Android SDK" installed successfully. (Needed to run certain modules etc.)
[Pixel C Android Development] EnginEAR:
Thanks!!!

Flashed LineageOS 17 together with the unofficial nano GApps followed by the custom followmsi kernel and Magisk 19.5.

TWRP is 3.3.1-0.

Seems okay.

Didn't encounter any issues not already mentioned.

Thanks for all your work [MENTION=5480152]followmsi[/MENTION]!!!
[Pixel C Android Development] Alxoom33:
Lineage OS 17 working great with Nano gapps, TWRP and Magisk 19.5. Could not dirty flash. Didn't boot. A factory wipe fixed thinks! Flashed the new Android 10 kernel, working. BT working great with my keyboard, connected my BT earbuds (Bose), as well!

Animations and scrolling are very smooth and fast. Using Nova Launcher Beta Prime.

Got gesture navigation working using Nova linked as the secondary Launcher and the native LOS launcher as primary. Don't know how to get the swipe left Google feed page working, like in the Pixel Launcher. Is it an option?

I can't seem to get sound on Google Music or I-Heart Radio or YouTube. Although, this morning I was on Firefox and I got sound in 1 ear of my BT earbuds of an interview on YouTube, low volume, however. Same with the native LOS browser. Faster and smoother than others.

Firefox, FF beta, Chrome and Chr beta work, although freeze and/or crash intermittently.

Chrome Canary crashes immediately. NVM, Chrome Canary just updated...works now.

Banking app works w/2 step Verification.

I'm trying LOS 17 out as a dd, although clearly we are somewhere in the Alpha-Beta stage. Great work! Thank you.

View attachment 4827905
[Pixel C Android Development] followmsi:
Made a new build for testing ..

DRM seems to be fixed.

L1 in DRM-Info app.

This time I made dirty upgrade from last lineage-16.0 backup .. had to clean contacts storage app - otherwise it's running ok.

Sound and HW graphics is still a mess .. maybe more.

lineage-17.0-20190927-UNOFFICIAL-dragon.zip

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:
Testing latest Lineage 9-27.

I dirty flashed over the previous beta with your A10 kernel installed.

Odd activity on TWRP SAR, on first boot to TWRP it asked for a password. However, I have never set a password and my device is not encrypted. A quick reboot of custom recovery and TWRP is back to normal not asking for a password. Somehow it glitched on boot and missed the encryption flag or decryption flag. No worries a quick reboot of recovery fixed it.

I first tried to flash the beta, Gaaps and you're A10 kernel all at once. However the kernel failed to flash and errored out in TWRP. Flashing the beta and Gapps alone worked fine. I went back into recovery and flashed A10 kernel which flashed successfully this time. However on boot up the device booted and started but then crashed. This repeated itself three times before booted stable and ran. Apologies I am not near my PC and could not pull a kernel log.

Everything else seems to be running just fine except for the known bugs with video and audio. I'll keep testing this weekend.

Thanks!

Edit: I set the tablet down for over 7 hours today and only lost 2% battery. So deep sleep works well! Zzzz...
[Pixel C Android Development] Vartom:
Problems with sound are connected with incorrect operation or config(audio_policy_configuration.xml) of AudioPolicsManager. The extended log clearly shows this. No solution has been found yet.

Problems with the video are related to the non-working new codecs media.c2. No solution has been found yet.

There is also a problem with access of some services to Ashmem. But this is probably not a big problem.
[Pixel C Android Development] tschmid:
Maybee this:

https://github.com/StatiXOS/android...mmit/c010bb7121e600296716da91283e28e0468cc169

Or this:

https://github.com/StatiXOS/android...mmit/3081624937dfd7a2eebedf6ac84606791b1c03b5

Gesendet von meinem Pixel 2 XL mit Tapatalk
[Pixel C Android Development] followmsi:
setprop debug.stagefright.ccodec 0

Fixes audio. ;)

Still working on video ..

Not sure if access to ashmem client lib is required.

Cheers
[Pixel C Android Development] Vartom:
I added all this, it did not help. And this is for other purposes.
[Pixel C Android Development] Vartom:
After adding this video in YouTube it worked !!!

:good:
[Pixel C Android Development] followmsi:
killall mediaserver

Afterwards all audio works .. volume change .. system sounds .. etc.

But then YouTube video plays sound only .. :(
[Pixel C Android Development] followmsi:
One more build ..

Improving Audio .. volume control and systems sounds are back.

But HW video decoding seems to be broken .. needs more testing.

lineage-17.0-20190929-UNOFFICIAL-dragon.zip

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] EnginEAR:
Thanks!!!

Dirty flashed lineage-17.0-20190929-UNOFFICIAL-dragon.zip, the new beta version of OpenGApps (10.0, "stock") from September 28th, tegra-3.18_kernel_10_dragon_v190921_unicorn-xceed-followmsi.zip, and finally the latest Magisk canary.

No new issues.

I can report that neither 3.3.1-1 nor 3.3.1-1 SAR work for me and that I can only get things to install using the 3.3.1-0 version of TWRP.
[Pixel C Android Development] Vartom:
Drm L1.
[Pixel C Android Development] zmw:
okay folks I am full on stumped. I can not get ANY combination of TWRP and Lineage to work any longer on my pixel C - I have tried everything from TWRP 3.2.1 to the latest 3.3.1 and lineage 16 and 17 builds, I either get in a complete boot loop, or it just keeps rebooting into recovery. Here is my process, what am I doing wrong. Already unlocked and bootloader unlocked obvious.

1. Boot into fastboot

2. fastboot flash recovery twrp

3. reboot into recovery via key controls

4. flash lineage 16 or 17

5. flash open gapps (either for 9 or 10)

6. flash magisk 19.3

7 reboot

8 reboot again

nothing....

at one point I was able to get it into a boot loop where at least lineage was getting to the splash screen but it would either hang there (left it for more than an hour) or another time, it would just reboot and keep looping - each reboot seemed to take somewhere between 8 and 10 minutes.

At this point I'm about to just give up, I've flashed the stock image to the latest june of 2019 image but honestly that makes this thing about worthless to me.

It's a shame this is so dang painful, the pixel C was the last good android tablet in my opinion.

If anyone can help, I'd greatly appreciate it!

---------- Post added at 04:00 AM ---------- Previous post was at 03:44 AM ----------

and FWIW the factory image does load perfectly fine, so I'm confident it's not a hardware or tablet issue. I'll likely load it up with software tonight just to make sure though.
[Pixel C Android Development] ipdev:
I'm not sure what is wrong with mine. I am chalking it up to a device gremlin.

I call mine Gizmo now. ;)

Something goes wrong with the boot image for me.

I'd have to look back but, I mentioned it a little while back.

The simplest way that works for me, flash the boot image using fastboot and then just fastboot continue, or reboot into TWRP and install Magisk.

I haven't had time to look to close into it but, these are the steps I use.

Starting from a clean formate and wipe.

Install ROM

Install GApps

Reboot to bootloader and fastboot erase boot and then flash boot boot.img (from the ROM.zip)

a. Fastboot continue

b. Reboot into TWRP

- b1. Install Magisk

- b2. Reboot system

Cheers. :cowboy:
[Pixel C Android Development] jorgen2009:
For both of you, you should reduce your variables here and see where it goes wrong. Here are some steps I would do to start diagnosing this:

First start from the latest Google image, that is your base. If everything runs fine you probably don't have a hardware failure. This is always the first step in diagnosing

Redownload official TWRP and Lineage, and verify the checksums, they are there for a reason!

Install TWRP, reboot to recovery and then install Lineage, ONLY Lineage!

Reboot, see if it works properly then and only then install the latest official OpenGapps

Reboot, see if it works and then install Magisk. If things are not working for you at this point, you either have faulty downloads or

After this is confirmed to work you can start doing the same with the latest experimental TWRP/Lineage/OpenGapps and Magisk. But make sure you install them separately, not in one go

Only if you used these steps a developer is might be able to help you, they don't have influence on hardware or any software they didn't write. Also logfiles will be very handy.

Good luck with your Pixel, it truly is the last great tablet :)
[Pixel C Android Development] Vartom:
I am 90% sure that his problem is that he did not remove the encryption from the date section. Since he did not mention that he did formatting the Date section. Lineage 16 and 17 do not support encryption.
[Pixel C Android Development] m+a+r+k:
My guess is that you didn't format the data partition to remove encryption?
[Pixel C Android Development] zmw:
sorry to be clear - I was on a good build of 16, it was just out dated, so I was updating and it went poorly. Because I only use the tablet for gaming or non work stuff I just figured I'd wipe and start over - I have had lineage on this thing for close to 2 years and up until now it was relatively painless.

I did do a clean start and ONLY try lineage and the boot just simply didn't work. I reinstalled the official google image and it worked fine so I know there is no hardware issue I even put some games on it to test out the graphics and make sure I wasn't having some weird only under load hardware failure.

I'll mess with it again tonight, but this is the first time I've been stumped through countless lineage devices.

-Z
[Pixel C Android Development] Markeee:
I'm running the latest Lineage-16.0 and absolutely no issues until today need to use the Pixel's camera and it just keeps freezing up?

I'm running Opened Camera and stock and both seem to just keep freezing having to reboot to unfreeze.

Wondering if anyone knows a work around for it ?
[Pixel C Android Development] ipdev:
Like I said.

I haven't had time to check my gremlins on Pixel C.

If you want to look, I just tried again and updated/added to the files I uploaded awhile back.

xdaPost 1254 - Link

GoogleDrive dragon - Link

Another user had a similar problem, so I mentioned the workaround that worked for me.

Sidenote:

I wasn't that concerned since, I seemed to be the only user to have an issue.

I found a work around by manually flashing the boot.img from the rom file.

I am using the official TWRP from twrp.me.

I only modified default.prop to grab a logcat. Normally I leave everything as is.

Cheers. :cowboy:
[Pixel C Android Development] muerte33:
I want to thank everyone involved in getting this ROM to the Pixel C Tablet!

One question....

Do I need to install that tegra-3.18_kernel_10_dragon_v190921_unicorn-xceed-followmsi.zip kernel, or is that just for speed?

It seems to work great with the twrp-3.3.1-1-dragon.img, open_gapps-arm64-10.0-nano-20190928-BETA.zip , lineage-17.0-20190929-UNOFFICIAL-dragon.zip ROM, and Magisk canary 19.5 for me.

Thanks again!
[Pixel C Android Development] Alxoom33:
Working great with either the stock or upgraded kernel. I am keeping the stock kernel for now until LOS 17 is stable.

Or, when we get the next [MENTION=5480152]followmsi[/MENTION].dragon kernel update. [emoji1]
[Pixel C Android Development] Alxoom33:
Anyone know of a camera that works with LOS 17 beta?
[Pixel C Android Development] 12paq:
I've tried quite a few, even some Gcam mods and modules. Not much works. I think it might be due to system changes that have yet to be implemented in 17.

I have had some luck with Open Camera. However, it is buggy and crashes often. I will keep testing and let you know if I find any positive results.
[Pixel C Android Development] Istvan_86:
ROM installed and working flawlessly, really thanks for all the work!!!!
[Pixel C Android Development] Iggy82:
Nice! Dirty flashed (Wipe dalvik cache, wipe cache, install) over previous build (20190806) and all is well.

Couldn't help notice Lineage v17 (Q??!) in the Google drive directory - What is it!?

Thanks for all your hard work
[Pixel C Android Development] Alxoom33:
It's an Android 10 based LOS ROM. Beta version.
[Pixel C Android Development] ratorresf:
Using Lineage 17 20190929 + kernel Tegra 3.18_10_Dragon_v190921. So far so good!

Thanks for the great work, you are extending the life of the tablet.
[Pixel C Android Development] followmsi:
Android 10 - October 2019

HW decoding seems to be fine !

Tested Youtube App (1080p60fps) and Netflix (HD) - all ok.

Camera is still not working correctly.

lineage-17.0-20191010-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> October 2019 (10.0.0_r4)

- Latest LineageOS changes for Android 10 -> still a lot of lineage stuff is missing.

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

New Lineage-16.0 build will come later this month.

Enjoy :p
[Pixel C Android Development] EnginEAR:
Thanks!

Installed and seems nice and smooth.

Also seems to be missing the settings app.
[Pixel C Android Development] Alxoom33:
Installed, works nicely. One issue is that I can't get into Settings. Only exception is USB debugging, when tethered, I can access Developer options, but that's it.
[Pixel C Android Development] Talonette:
As always, great work ! Thank you so much.
[Pixel C Android Development] Alxoom33:
Also, blue tooth doesn't seem to be working.
[Pixel C Android Development] followmsi:
BT works fine for me .. also settings menu.

Did you made clean install ?

Made dirty update from last build.

Did you forget gapps ?

No idea what's wrong, need more info.