yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] assdredxexfg:
hi,

I installed lineage-18.0-20201121 coming from lineage-17...

I did Wipe System Data, like described in the OT.

- Now on lineage 18, the performance is very very bad.

- App updates in the play store do not update.

- wifi not working most of time (connected but no download)

- Home button (navigation) not working

- Settings button (pull down from top) not working

...

any idea? Do I need a factory reset coming from 17?

thx
[Pixel C Android Development] keviiinn:
In several threads it says to remove or rename "/vendor/lib/liboemcrypto.so", but I don't have this file, nor do I even have lib. I only have lib64. Either way, I don't have that file. So all my video streaming has crapped out. What am I missing here?
[Pixel C Android Development] Alxoom33:
Look again. There is a root/Vendor/lib folder along with Lib64. Open it and rename the file.
[Pixel C Android Development] followmsi:
As L1 Widevine has been revoked we will switch to L3 in

next

builds. (17.1 and 18.0)

For this reason I have patched Nvidia "libnvomx.so" to make the HW codecs work on L3 too.

dragon: Switch to L3 widevine · followmsi/android_vendor@b210932

As it looks like Pixel C device (6377) has been revoked. https://t.me/s/wvcrl/896 We keep liboemcrypto.so as liboemcrypto.so.bak Patched libnvomx.so to removed dependcy on liboemcrypto.so patchel...

github.com

Before this change we were "forced" to keep liboemcrypto.so to make Nvidia HW codecs working.

In current ROM, if liboemcrypto.so is missing, you will disable HW codecs automatically and you will use Google software codecs only.

This change will help to logon to Netflix without "playing around" with "liboemcrypto.so"

You will not get back HD video quality (L1) anyway .. due to revocation by Google.

But this change will not help with videos not playing in Chrome browser .. this is an other HW codecs issue.

Not sure if this can be fixed ever ... due to closed sources and "old" prebuilt libs.

Cheers
[Pixel C Android Development] assdredxexfg:
any idea? - thx
[Pixel C Android Development] Alxoom33:
I dirty flashed coming from 17.1 and worked. Remember, 18.0 is new and @follwmsi is still working out some bugs, along with LOS.
[Pixel C Android Development] followmsi:
My "dirty" upgrade from 17.1 did not work at all .. booting forever. (n)

Checked logs and tons of permissions and upgrade paths were missing.

Some part has to be done by Lineage and most of the stuff has to be done by Gapps.

For this reason I strongly recommend to go for clean install at this point of time !

Do factory-reset in TWRP to keep your internal storage.

Cheers
[Pixel C Android Development] Alxoom33:
Actually, my dirty flash to 18.0 came immediatly from an internal memory format and clean set-up of 17. Remember I was having issues previously. However, I again did a clean flash to 18 and restored my data (does that make it a dirty). But I have 18.0 working fine. So confusing!
[Pixel C Android Development] heyChristo:
Good afternoon, I am posting here since this seems to be the most active forum for this device. I am having horrible wifi issues with my pixel C. I can't even stream 1080i video from my plex server in the other room. I can stream just fine to my htc 10 but to my pixel c I have to reduce video to 4mb/second 720i video. I have been searching to see if there is anything to do as in a fix. WIth my phone next to my tablet and both on the same wifi, the pixel c is geting less then half of the speed that my phone is getting. I can watch my wifi download speed in my status bar and when my video stops its because it stops downloading all together. I know this isn't the place to post this, but I'm having issue searching the forums with the new format. Any advice?
[Pixel C Android Development] Alxoom33:
What rom, os are you running on your Pixell C?
[Pixel C Android Development] heyChristo:
Right now, dirty unicorns but was thinking of flashing this one. Are the WiFi issues rom specific?
[Pixel C Android Development] Alxoom33:
I am not sure. But I think they are. There is a big difference between the 2 Roms. DU is based on earlier android versions. The last version I tried is based on Android 10. LOS 18.0 is Android 11. I woulld ask the developer, @NYCHitman1 about your issues. Although my understanding is he is no longer supporting the Pixel C.
[Pixel C Android Development] Alxoom33:
In order to try and attempt to solve my Issue with not having Fasboot not working or seeing the Tablet, I tried flashing a Magisk Module labled: ADB & Fastboot for Android NDK. It states Static ARM adb and fastboot binaries for Android build with the NDK.

Description: Marsmellow removed adb from tehe /system/xbin and uses a command wrapper to point adb to the corrrect HOME directory and set TMPDIR for compatibility...

After instullation, ADB still worked, but Fastboot was not working. Any thoughts?
[Pixel C Android Development] followmsi:
LineageOS 18.0 - December 2020

lineage-18.0-20201209-UNOFFICIAL-dragon.zip

Changes:

- Google Security updates -> December 2020

- Switched to L3 Widevine

- Improvements for DRM service

- Fixed aptX codecs for Bluetooth.

- Fix for Camera

- Moved/Changed overlays for Android 11

- Patched framework/base to support microG

- Latest LineageOS changes

Magisk 21.1 sems to require manual reinstall after ROM update .. while opengapps test package got automatically reinstalled.

Enjoy :p
[Pixel C Android Development] followmsi:
LineageOS 17.1 - End of LIfe !

Just to let you know .. I will continue on 18.0 only.

The upcoming December build will be my "final" Lineage-17.1 ROM.

Thx for understanding !

Cheers
[Pixel C Android Development] mdonders:
Hi, had the same issue that Windows 10 didn't recognize our pixel c in fastboot mode. Tried many different drivers, but none worked.

Then found:

https://xdaforums.com/t/yet-another-universal-adb-driver-package-and-adbupdater-for-windows.3595277/

And after installing this, the pixel c was recognized again.

Grtz Mark
[Pixel C Android Development] muerte33:
Since you are going all in on 18.x, where is the best place to download opengapps Pico Arm64 version off sourceforge?

Thanks!
[Pixel C Android Development] ipdev:
You might be interested in the root of that module.

Fastboot for ARM/ARM64 xda thread - Link

In the pictures, you can see he is using a Nexus 6P to flash a Pixel 2XL.

Also, there was some recent discussion about it over in Odds and Ends starting on page 143 (Post 2842). Read though the end of the thread (you can skip posts not related).

[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms] xda thread - Link

Cheers. 🤠
[Pixel C Android Development] Alxoom33:
Thank you @followmsi. The new ROM flashed without problem and retained the test gapps. Are there new Android 11 gapps available? I haven't checked yet. :)

However, I had no problem reflashing latest Magisk Canary zip 21101 version. Thank you![/QUOTE]
[Pixel C Android Development] Markeee:
Can someone please post a link to the 18.0 Gapps i need to install this update
[Pixel C Android Development] Alxoom33:
Yes. Look for test.
[Pixel C Android Development] Alxoom33:
Just Google open gapps 11 test. Or look for the Nik 11 gapps.😄
[Pixel C Android Development] Markeee:
Is there a specific Gapps that's tested and working ?

Google search brings up many wouldn't want to pick the wrong one

Nik 11 gapps forum people seems to be having alot of issues
[Pixel C Android Development] EnginEAR:
I've been using these for a while (including the flashing of the latest build):

https://sourceforge.net/projects/opengapps/files/arm64/test/20201116/open_gapps-arm64-11.0-pico-20201116-TEST.zip/download
[Pixel C Android Development] muerte33:
OK, all was going well on the Lineage 18.x install, then I got to this question after reboot:

Update Lineage Recovery alongside the OS

It is pre-ticked, should I proceed or untick?

Update:

I went ahead and took the default (ticked).

This was a mistake because TWRP is so much better than the LineageOS recovery.

Superb job on the ROM FollowMSI !
[Pixel C Android Development] Fredplex:
18.x working splendidly. Thx!

I do have an issue with chrome, it does not recognize that I am already logged in with my google ID and asks to login when I try to turn on sync. But what I try to login I get an error "user already exists on device"

Any workaround for this?
[Pixel C Android Development] followmsi:
LineageOS 18.1

Lineage Team called the change "18.1 for Xmas" ..

lineage-18.1-20201211-UNOFFICIAL-dragon.zip

Changes:

- Dropped PinnerService -> improves memory usage

- Latest LineageOS changes

Magisk 21.1 seems to require manual reinstall after ROM update ..

For 18.1 you have to reinstall gapps too.

Enjoy :p
[Pixel C Android Development] muerte33:
Is there any way to get back to the Old recovery (TWRP) instead of the LineageOS recovery?

When I use the Lineageos recovery it loads the 18.1 rom, but fails on the Gapps load

I am using the Pico (which is the smallest on sourceforge).

Even on a sideload I get:

Insufficient storage space available in system partition.

You may want to use a smaller Open Gapps Package or consider removing some apps using gapps-config.

see: '/sdcard/open_gapps_log.txt' for complete details and information

Copying log to /sdcard

no changes were made to your device

installer will now exit

error code: 70

-unmounting partitions

e: error in /sideload/package.zip (status 70).

UPDATE:

YES, that was FUN!

I did a factory reset from the Lineageos recovery (formatted DATA, CACHE, and SYSTEM)

I then sideloaded the new 18.1 ROM using the Lineageos recovery (still would not let me install GAPPS).

Rebooted and did a minimal setup in Android 11

Rebooted to Lineageos recovery and sideloaded TWRP.

Rebooted to recovery and it was now TWRP (Hooray)!

I then had to use TWRP to load the OpenGapps Pico ARM64 version

Rebooted and finished Android 11 setup.

Wow, all is well now, and thanks to FollowMSI for such a great ROM!
[Pixel C Android Development] Alxoom33:
I had the same issue. I take it your fastboot dosn't work?

@followmsi provided a twrp.3.4.0.zip file. You can sideload and flash it and it will enabble TWRP Recovery.

I I ssuggest searching this thread. Or look in @followmsi's llink to the Google drive. I think the file is stored therre.
[Pixel C Android Development] followmsi:
Lineage did change the prop for 18.x .. I have changed it for next build.

dragon: Update UPDATE_RECOVERY_PROPERTY for 18.1 · followmsi/android_device_google_dragon@1f6c500

Contribute to followmsi/android_device_google_dragon development by creating an account on GitHub.

github.com

Of course, Magisk installation will prevent the stock recovery replacement too !

Yes .. "Update.ZIP_TWRP_dragon_3.4.0-0.zip" is still on gdrive.

Cheers
[Pixel C Android Development] followmsi:
LineageOS 17.1 - December 2020 - FINAL BUILD !

This is my last lineage-17.1 ROM for dragon ..

lineage-17.1-20201211-UNOFFICIAL-dragon.zip

Changes:

- Google security updates -> December 2020

- Switched to L3 Widevine

- Fixed aptX codecs for Bluetooth

- Switched to media_profiles_V1_0.xml

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

- Patched frameworks/base to support microG

- Latest LineageOS changes for Android 10

Pls check first page for installation instruction and known issues !

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

Enjoy :p
[Pixel C Android Development] muerte33:
I could not load anything with fastboot, it would start, then it kept getting an invalid IMG, but I cannot remember the exact messages.

The other problem I had was on the Google Drive download page for FollowMSI, it would not let me download individual files using Firefox or Edge Chromium. I ended up having to click download ALL, where it zips all the files into one big one and sends it down (which was fine). I was just glad to get TWRP back, it seems to have so much more power than the LineageOS recovery. This 18.1 ROM seems to be really fast for me, I don't know about everyone else. This tablet should have at least another year of longevity.
[Pixel C Android Development] Talonette:
Thank you very much followmsi for the last build of Lineage 18.1
[Pixel C Android Development] octopus90:
Does anyone else have problems with WIFI - the device mac address is 00:90:4c:11:22:33 and I can't connect to my wireless network.

I tried the the new build lineage-18.1-20201211-UNOFFICIAL-dragon.zip (fresh installation).

Then I wanted to switch back to 17.1 but the same problem occurs with December build lineage-17.1-20201211-UNOFFICIAL-dragon.zip.

I already sent a logcat to @followmsi.
[Pixel C Android Development] followmsi:
No need for logcat .. it's a known issue !

Just updated first page as well.

- MAC address is fixed and device specific MAC will be ignored.

This has been discussed in spring this year ..

Here are some more infos ..

https://github.com/followmsi/android_kernel_tegra/commit/59f8c10b61fe286315d7a631903fed542e1270d5

Pls use this kernel ... tegra-3.18_unified_dragon_kernel_10_v200305.zip (inside KERNEL/OLD folder)

https://xdaforums.com/showpost.php?p=81938531&postcount=842

As the patch makes boot problems it has been taken out again .. same like in latest kernel/rom versions too.

https://xdaforums.com/showpost.php?p=82065729&postcount=852

Same for "standard" kernel in ROM .. the patch has been taken out again.

Even you use "special" kernel and have sometimes boot problems or you keep the fixed MAC for the moment.

I know, in case you have 2 or more Pixel C devices this is a pain !

Sorry .. not able to just "fix" this problem myself.

Cheers
[Pixel C Android Development] octopus90:
Thank you very much for your fast reply @followmsi

I thought that the WiFi connection problem with version 18.1 was due to the MAC address.

I never noticed that this was also the case with version 17.1. ;)

With version 17.1 everything is ok - WiFi connection is possible. (y)

But with version 18.1 my problem with WiFi connection still exists.

When I try to connect I get the error "Failed to connect to network".

I found a error in the Pixel C log:

Does anyone else have problems connecting WiFi with 18.1?
[Pixel C Android Development] Fredplex:
@followmsi does the latest version of 18.x take up a lot more space? I am not not able to install gapps nano (not enough space) - this same gapps work ok with your previous 18.x thx!

update: pico can't install either

update: ....arg - I've been away from pixel-c roms for too long - I think this is a SAR issue - going to re-read everything and see if I can fix myself up - I'm using Lineage recovery - I would have thought it had all the SAR stuff in it ...
[Pixel C Android Development] Alxoom33:
New Lineage 18.1 works great! Much smoother than 17.1 or 18.0. Used OpenGAPPS 11 Micro test gapps. Magisk Canary 21101.zip worked great. No manual reinstall, i.e. patching, needed. After update, just boot back into TWRP and flashh the Magisk 21101.zip! Thanks @followmsi. Can't believe I have the December seurity patch on my Pixel C and my Taimen with the December update only has the October security patch installed! I think I need to swich to Lineage 18.1 for Taimen soon!
[Pixel C Android Development] muerte33:
I had that same problem. I ended up having to sideload TWRP back to replace the LineageOS recovery.

I then used TWRP to load the PICO version of the Sourceforge Android 11 Gapps. Good Luck.
[Pixel C Android Development] Grigori88:
I still don't know how to install TWRP.

I have LineageOS recovery.

I can't install Gapps and Magisk.
[Pixel C Android Development] followmsi:
This is another problem .. not related to MAC address at all.

Did you switch Wifi Router .. or router configuration ?

Looks like WPA3 stuff .. had similar problem on another device as well.

For next build we will disable PMF .. should help in this case.

dragon: disable wlan PMF · followmsi/android_device_google_dragon@cd952ac

* After I4c120e1f094a7b039837779f58d15cfc7f68d697 merged in android-10.0.0_r31, the device fails to connect to PMF enabled (not necessarily enforced) wifi access points. * Stop advertising ...

github.com

Pls try yourself and adjust "/vendor/etc/wifi/wpa_supplicant_overlay.conf" with root explorer .. Add "pmf=0" and reboot device .. test connection again.

Cheers
[Pixel C Android Development] followmsi:
No .. 18.1 does not use more space .. we have still plenty of "free" space on system ..

Even stock package should work.

But there might be strange issues due to gapps starting problems on Android 11.

For the moment do always wipe system .. do not rely on backup scripts.

They used to work in 17.1 .. but not yet in 18.x.

Always install ROM, Gapps and Magisk in one go .. do never reboot in between !

Good luck !
[Pixel C Android Development] brackenhill_mob:
That's not my experience with 18.1 which bootlooped when I did this. But installing ROM, reboot, install Magisk, reboot, then GApps reboot worked perfectly.

Weird ;)
[Pixel C Android Development] muerte33:
In Android 11 they removed the Screen Capture button from the power menu.

I know you can do Power button + Volume Down, or go to the "recents" screen and click the "Screenshot" button at the bottom, but is there a way to add this button back to the power menu?

Thanks!
[Pixel C Android Development] jercar:
Can anyone let me know if the camera and video work well on 18.1. The camera and video always crashed on 17.1 which was a issue for me. Thanks.
[Pixel C Android Development] Alxoom33:
Not sure why you needed Pico. I used micro, just because it was the largest Open Gapps test 11 version available. Used Full with LOS 17.1. Plenty of room in the System partition.
[Pixel C Android Development] Alxoom33:
I addressed that issue and it was discussed only a few days ago. read the last few days and you will learn how.
[Pixel C Android Development] Alxoom33:
I had the same experience as you. Bootlooped when Los 18.1 and gapps flashed together, and then Magisk. But when flashed seperately worked without a hitch!
[Pixel C Android Development] Markeee:
Can you post a link to where your getting the latest Micro Open Gapps test 11 versions at please ?
[Pixel C Android Development] ahalol:
Can you check the MD5? the file in the Gdrive has different MD5 with the md5 file. this is causing me in bootloops
[Pixel C Android Development] Eurgain:
My access point (EnGenius EWS357AP ) was set up for WPA3/WPA2 and the Nexus C would not connect, even with the changes above. I changed the access point to WPA2 only, and the Nexus then connected.
[Pixel C Android Development] octopus90:
The same for me:

Disabling PMF didn't solved the problem

Changed SSID (on my router) to WPA2 only => connection is possible (also with enabled PMF)
[Pixel C Android Development] Alxoom33:
I usually search on Google chrome for Android 11 Gapps download. I may add test. Usually I use Open Gapps Arm 64 test. But Nik Gapps are also ok.
[Pixel C Android Development] Alxoom33:
You will never learn until you find your own stuff and determine what works and does not work on your own!
[Pixel C Android Development] followmsi:
I have been testing Opengapps only .. I do not have problems with "all 3 in one go" installaton.

Did the same ARM64 installation on another device running 18.x builds.

No bootloop issues too.

No installation problems at all .. just other gapps problems :)

In the past you get strange issues if lineage installer running before opengapps installer .. like home button not working correct ..etc.

But as it looks like it works different .. at least for you and others too.

Thanks for the update .. and your solution to this problem.

Cheers
[Pixel C Android Development] followmsi:
Thanks for testing and feedback .. I still do have WPA2 router and no such problems.

I have reverted this change on Github now.

Don't want to disable function if they are not related to the problem.

On another device the same "trick" did help to solve connection problems to WPA2/3 routers.

It may works different on another router/configuration .. anyway.

I am not able to replicate .. most likely our wifi driver in kernel is responsible.

Maybe there are some android flags to force WPA2 on older devices like Pixel C.

Cheers
[Pixel C Android Development] ahalol:
Sorry, i was referring to the actual firmware in @followmsi 's folder. The md5 mismatches. I kept on getting bootloops from a clean install so i was wondering if the pack was faulty
[Pixel C Android Development] followmsi:
Quickly tested MD5 .. all OK .. can't replicate your mismatch.

Cheers
[Pixel C Android Development] Eurgain:
I would be happy to try to help debug this, but I am not sure how to start. I have lots of Linux experience (since 1999 Kernel 2.0.36) and I would normally start investigating with journalctl -f or tail -f /var/log/messages, but neither of these work on Android :-( Any tips?

Apart from that tiny problem, this is a superb ROM. Thanks indeed for all of the work, followmsi!
[Pixel C Android Development] Alxoom33:
It worked fine when I tried. Perhaps you just got a bad dl. Try again.
[Pixel C Android Development] ahalol:
what is the correct md5? from you

Thank you and @followmsi , it was indeed a corrupted download. I got it to work now.
[Pixel C Android Development] jercar:
@followmsi just wondering how the camera and video are working out on lineage 18.1?
[Pixel C Android Development] followmsi:
Lineage "stock" camera starts and works .. you can take pictures and record video .. I did not made more tests yet.

Just install 18.1 and test yourself. :)

Cheers
[Pixel C Android Development] followmsi:
"logcat" is /var/log/messages in android .. like in linux "dmesg" shows kernel log.

But you may need to adjust debug / log level in kernel / android to get the information you need. Perhaps the default log level is too low and you do not see the problems related to failing WPA2/3 router connection.

Pls don't ask me where to change log / debug level .. have to search myself.

If you are able to refresh wifi kernel sources and fix problems .. pls go ahead !

I have seen another android flag which may helps too ..

Disable WPA2 -> WPA3 upgrade.

dragon: wifi: Disable WPA2 -> WPA3 upgrade. · followmsi/android_device_google_dragon@374aa5f

Our device doesn't simply support sae. Change-Id: Ibf8b9e363b4677cf2ab9590cc2ea1ba2341e29ca

github.com

Part of next build.

Cheers
[Pixel C Android Development] followmsi:
I have made a TEST build including GAPPS from Pixel Experience .. let's share it.

Files · eleven · PixelExperience / vendor_gapps · GitLab

GitLab.com

gitlab.com

If you have used other gapps package before you may get problems .. clean install is recommended.

Made the same build for another ARM64 device too .. Pixel launcher and all the stuff seems to work fine. I did not test on dragon yet.

The stock Lineage apps have not been removed .. apps like contacts, calculator, browser still exists.

Again .. This is a special gapps build and just for testing.

lineage-18.1-20201214-UNOFFICIAL-dragon.zip (gapps-included subfolder)

Changes:

- Added GAPPS

- Re-added PinnerService

- Set flag for UI optimizations

Enjoy :p
[Pixel C Android Development] wardy277:
Was planning on wiping my 17.1 and installing 18.1 and saw the version with gaps included. Gave it a go and seem to be working well
[Pixel C Android Development] philetus:
I tried out Lineage 18 on my Yoga Tab 3 Plus yesterday. It's pretty nice, but I had a few problems with one of my apps.

I decided to revert to the Lineage 16 backup and found out my twrp had been replaced. I believe it was because I rebooted the Lineage 18 install?

I found out trying to boot into bootloader that when the boot screen comes up, it's in bootloader. I didn't realize that at first and was able to install twrp by

by enabling adb in the Lineage recovery. Installed twrp in fastboot and found my backup from yesterday and I'm good to go.
[Pixel C Android Development] octopus90:
I've been using version 18.1 for a few days now - runs really well.

I have noticed the following small things:

after starting the "Play Store" the logo is displayed, but then it takes about 20 seconds until it goes ahead

the app "Google Maps" starts, but after a few seconds it closes automatically

Is it the same for you?