yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] followmsi:
Made a fresh build today ... lineage-15.1-20180418-UNOFFICIAL-dragon.zip

No problems at all !

Installed the ROM

Magisk 16.3 got installed automatically after ROM installation - thru addon script.

Installed the latest "unified" kernel as last step and did wipe cache/dalvik.

Reboot ... done .. no issues at all !

Magisk works ... all is working fine !

Hmmmmmm ... as next step I will need to install the official version.

Had a chat with razorloves (maintainer for nexus 5 and 6p) .. no probblems reported on other devices.

Cheers
[Pixel C Android Development] frauhottelmann:
My Nexus 5X didn't have any problems. ?
[Pixel C Android Development] alphamode:
Clean install of the newest build and I'm stuck at the Google screen

Edit: even the previous one is getting stuck at Google logo so I'm thinking it's my fault. I did it in this order, wiped data, flashed newest update + opengapps + magisk 16 and cleared cache/davik. Am I missing something?
[Pixel C Android Development] followmsi:
Yes, pls use version from last week .. and magisk 16.3 has been tested.

Not sure about 16.0 .. and earlier versions.

Depending on your previous ROM wipe system before ROM installation.

Good luck !
[Pixel C Android Development] Lostprophet85:
Hi,

did you flash the vendor image? Seems to me you missed that. Just an idea.

Best of luck!
[Pixel C Android Development] frauhottelmann:
No, latest build doesn't work...
[Pixel C Android Development] Lostprophet85:
I know, but I assumed he flashed the inofficial new build from followmsi based on the quote in his post.
[Pixel C Android Development] followmsi:
Thanks .. did you test the unofficial build from April 18 in the gdrive folder ?

Any problems ?

Somebody else who did install this build ?
[Pixel C Android Development] alphamode:
I was glashing magisk 16 and it was causing the issue. I flashed the current unofficial build with magisk 16.3 and it's running well
[Pixel C Android Development] followmsi:
Current unofficial .. 20180418 .. April , 18 ?

Just to confirm ...

Thanks
[Pixel C Android Development] alphamode:
Yes the April 18th one is running smooth, thanks for the great work ?
[Pixel C Android Development] blue_algae:
If LiveDisplay is set to 'Night' or 'Automatic' (and it is night time), YouTube TV would just be black though audio is still playing. I'm on 2018-04-09 build.
[Pixel C Android Development] followmsi:
Some devices and apps have problems with LiveDisplay.

Just switched on LiveDisplay and set to night mode manually and tested YouTube .. still plays fine for me.
[Pixel C Android Development] blue_algae:
Yup, no problems with YouTube. It is YouTube tv that it has a problem with which is a different app from Google. Maybe we could have that added in the problems section?

Another issue I found is that Play Books' night mode doesn't work either regardless if LiveDisplay is on or off. It just doesn't work. But it is not bad considering we have LiveDisplay for night mode. Again, nothing major but I think should be added in the problems section.
[Pixel C Android Development] followmsi:
Thanks for the update.

Did you test on stock image too ?

YouTube TV works with night mode on ?

Same with PlayBooks .. works fine on stock image ?

Lineage just made some changes for LiveDisplay .. will need to test them in next release.

I will not be able to test YouTubeTV ..
[Pixel C Android Development] parakleet:
Everything installs fine for me accept Magisk.

I cant get 16 or 16.3 to boot.
[Pixel C Android Development] followmsi:
Did you flash onto fresh boot.img ?

Just flashed 16.3 a few times yesterday .. no problems.

The problem build from last week has been removed now .. took a while.

Looking forward for the new build today ..
[Pixel C Android Development] followmsi:
Just tested the new official build .. no endless bootanimation for me.

Seems to work fine ..

Pls confirm .. Thanks
[Pixel C Android Development] wizzardsk:
It works, but had to reflash gapps and google play services keeps stopping. Cannot update any app from store.
[Pixel C Android Development] followmsi:
Not for me .. migrated my existing (dirty) data partition to official version (change keys) and installed the official build from April 09.

Today I just did upgrade .. all normal .. existing gapps and magisk 16.3.

You did test unofficial version .. isn't it?

Did you migrate your data before installation of official build from today ?

It sounds not like .. as the problems you describe are related to different keys.

You may try to change keys after restore from data partition and before ROM installation ..

More Infos here ..

https://wiki.lineageos.org/signing_builds.html
[Pixel C Android Development] wizzardsk:
I did not try the test version. Had official april 9 version and just did upgade in updater. After update the google play services did not work.

I am just used to integrate updated system apps to system, it is a habit since my first device with low internal storage :)
[Pixel C Android Development] followmsi:
Ok. Thanks.. interesting.

Will keep the official version for now .. and test next week release again.
[Pixel C Android Development] wizzardsk:
I flashed back april 9 version and play services works fine....
[Pixel C Android Development] parakleet:
I am working now without issue.

SO a few things.

I formatted and wiped it was fresh evverytime.

Only the Apr 9 release worked for me.

Installing Magisk always led to issues.

Until (DING DONG) i used the boot.img from the Lineage install.

i had been using Factory image.

Please go easy on me.

After using the Lineage img all was well.

I forgot how much of a mess TWRP had become.

I should have stuck to ADB/FASTBOOT commands.

it would hae saveda bunch of time.

Very happy now
[Pixel C Android Development] frauhottelmann:
New update works for me...
[Pixel C Android Development] followmsi:
TWRP works fine .. but its damn slow due to drm graphics issue .. discussed 100 times in TWRP thread.
[Pixel C Android Development] bigtreiber:
Problem with prime Video App

Hi,

I'm running LOS 15.1 (20180423) on my, Pixel C and am trying get Amazon Prime video working. When starting the app I get an error message:

Detected problems with app native libraries (please consult log for detail): libAIVPlayReadyLicensing.so: W+E load Segment

Video seems to work, but why the error message?

I can't find any solution on the net. Any suggestions?

bigtreiber
[Pixel C Android Development] followmsi:
Seems to be App related ..

https://stackoverflow.com/questions...ot-allowed-in-android-o-8-0?noredirect=1&lq=1

Like above described .. there are also the .. "text relocations" warnings .. like in Kodi app too.

In my understanding this kind of issues needs to be fixed inside the APPs .. and not inside the ROM.

You may can manipulate the ROM (platform_bionic) to prevent warning messages .. but thats not the goal.

Sorry .. can't help you better here ..

EDIT:

(please consult log for detail) .. Maybe the logs include more detailed infos.
[Pixel C Android Development] Dressiel:
Hi [MENTION=5480152]followmsi[/MENTION]

Im back with another Question. Currently Im using the official LinageOS 14.1 Build and i just wondering if i can update to official LinageOS 15.1 Build with ease. I havent touched TWRP for while , so the first would be to update TWRP via .img file in TWRP

(https://xdaforums.com/pixel-c/development/twrp-3-0-2-0v16-t3400503).

After that do i really need to go for a full wipe (clean install)? That would mean ....Quote from your first Post

1. Boot into TWRP

2. Wipe system, cache, dalvik and data. (Not required if you upgrade from previous build)

Do you mean upgrading from 14.1 to 15.1 ?

3. Install lineage-14.1-2018xxxx-dragon.zip

you mean this --> https://download.lineageos.org/dragon ?

4. Install current stock vendor.img (flash via TWRP)

from your Download Folder: vendor_OPM1.171019.022.A1_Mar-2018.img or vendor_ryu-opm1.171019.026_Apr-2018.img ?

6. install SuperSU.zip

7. Reboot into system ..

Sometimes i wonder what the difference between "dragon" and "ryu" is.....i guess its the same.

Thx in advance

Have a nice Day
[Pixel C Android Development] followmsi:
https://xdaforums.com/showthread.php?p=76100466
[Pixel C Android Development] Dressiel:
[MENTION=5480152]followmsi[/MENTION]

Thx alot, lesson learnt ....i had read that post for quite a while....but i forgot. Sry

For the vendor image im going for the march build or April ? (Maybe a silly question )
[Pixel C Android Development] tebra:
[MENTION=5480152]followmsi[/MENTION]

Hi, did you know anything about the small bug with the option to show arrow buttons when typing? They display together like this <> on the left part of other soft buttons.

I don't have this bug with official 15.1 on my Nexus 5x
[Pixel C Android Development] followmsi:
With each monthly stock update I do update the fingerprint to current month.

The release on Monday will still have April.

This week the May patches (most probably on Wednesday) will come..

The lineage release one week later should have May fingerprint e.g. vendor.img.

In case you forget latest vendor.img you get warning message in system.

Just reboot into TWRP and install the correct one.
[Pixel C Android Development] followmsi:
The bug is the "normal" dragon navbar layout itself. ;)

If you switch to "compact" navbar .. also the "<" working fine.

Did you made clean install ?

Plenty of dragon navbar overlays have been removed in the last time.

The dragon default position for "back" button is very left .. same position like "<".

There are no plans to change the default "normal" layout of dragon navbar ..
[Pixel C Android Development] tebra:
I was not clear. The bug is not about the back button but additional buttons to move cursor when you type something. See on this screenshot. Normally < will be on the left and > on the right but they are together on the right of other buttons.View attachment 4489376

Envoyé de mon Pixel C en utilisant Tapatalk
[Pixel C Android Development] followmsi:
Did you read my text above ?

It's working if you use compact layout for navbar.

Just tested it again ..
[Pixel C Android Development] followmsi:
Just tested latest official build from today .. lineage-15.1-20180430-nightly-dragon-signed.zip

No issues at all .. works fine.

It seems the failings build 2 weeks ago was a strange incident .. not able to reproduce.

Tested with latest Magisk 16.4 .. works fine too.

Cheers
[Pixel C Android Development] wizzardsk:
Just updated, after boot it encrypted data and google services not working again. Twrp was unable to decrypt data so I have no way to install gapps without formatting again.
[Pixel C Android Development] followmsi:
Official lineage builds do force encrypt ..like google stock ROM too.

You may install magisk or no-encrypt packages after each ROM upgrade.

Magisk will be triggered automatically via add-on script.

In TWRP thread there are some users with similar problems ..and how they solved it.

As well you can use USB stick to install gapps or do adb push to /tmp folder ..etc.

Will still monitor the next official builds more closely ..

Cheers
[Pixel C Android Development] wizzardsk:
I had installed magisk :)
[Pixel C Android Development] followmsi:
It seems something went wrong for you ..

As I wanted to test magisk 16.4 today and the automatic addon installer of 16.3 did his work.

To start clean I flashed boot.img from today's ROM only.

Installed 16.4 and wiped cache/dalvik.

Rebooted into system ... All fine and not encrypted ;)

Cheers

EDIT:

If you want to reset all magisk settings you install the magisk uninstaller via twrp as very first step.

Even magisk uninstaller will restore stock boot.img you should anyway overwrite with fresh boot.img taken from current ROM.
[Pixel C Android Development] wizzardsk:
Ok, I reinstalled it again and it works for now :) btw, that Orion Nebula on the wallpaper is great.
[Pixel C Android Development] ToldYouSo:
I know for the Official LineageOS on 6P u are sometimes required to flash the latest vendor.img from the Google factory builds.
[Pixel C Android Development] followmsi:
Yes, you always need to flash current vendor.img.

But in this releases here the required vendor.img is already included into the ROM installer.

You need to install SuperSu as last step .. but no vendor.img.

Maybe we will change this later on ... to become more "official" :)

Hope this helps ..
[Pixel C Android Development] Reuben_skelz92:
This is running great so far. I like the live display to turn up the coolness slightly:)
[Pixel C Android Development] followmsi:
Good news :)

The previous builds were still using "external/tinyalsa" and "external/tinycompress" from AOSP sources - due to build errors.

Was a little bit confused by this problem :confused:

But now I have found the issue - it's actually kernel related.

Angler and other official LOS devices are using the same "patch" ...

https://github.com/followmsi/android_kernel_tegra/commit/0403e655edfdbe7186c00ab5d4276c09ba4b2181

Now we can build LineageOS and it's family (OMS and RR) without using any other sources !

We are fully compliant now !

This version below is compiled on 100% LineageOS sources .. and the latest followmsi-kernel changes !

lineage-14.1-20170505-UNOFFICIAL-dragon-followmsi.zip

This is a big step into the right direction to be an "official" LineageOS device .. maybe soon :)
[Pixel C Android Development] xda_jm:
Very nice. Thx for your work on that :)

One little quuestion though.

I'm using LIneage OS on other devices too, and noticed that depending on the verison of TWRP and SuperSU one can have strange results.

Any chance you folks could post the current versions of these tools to use (for the Pixel C), and eventual links to these too?

Also - as I tend to not use any cloud services (using my own cloud at home with. nextcloud) - what's the best way to backup the apps + configs?

So far - I never did it, as contats/calendar/files etc. was always synced to my cloud (owncloud at first, nextcloud now) - but my "yougens" here want to keep their Game-stats :eek: - and that, I can't store in my cloud as only the Google cloud is supported by the games, or local machine.

Thx for any feedback on all that :)

Cheers
[Pixel C Android Development] followmsi:
Since 2.72+ supersu is supporting the pixel c (chromeos support)

No issues if you follow the installation instructions correctly.

I have moved to Magisk (v12) now .. works fine with Pixel C too.

For TWRP you should use the official version .. live since April 1st !

https://twrp.me/devices/googlepixelc.html

Which is still the best way to backup data partition .. offline.

For the owncloud stuff you have to search yourself ..

I use "Cirrus" for my little owncloud syncing on Android.

Hope this helps ..
[Pixel C Android Development] followmsi:
Made a new OMS version today ..

lineageOMS-14.1-20170508-UNOFFICIAL-dragon-followmsi.zip

Changes:

- Latest LOS and OMS changes

Enjoy :)
[Pixel C Android Development] xda_jm:
Which image/zip file do I have to install?

I just installed your latest lineageOMS-14.1-20170508-UNOFFICIAL-dragon-followmsi.zip - and followed the steps:

From TWRP, I installed the files in the following order:

1. lineageOMS-14.1-20170508-UNOFFICIAL-dragon-followmsi.zip

2. open_gapps-arm64-7.1-nano-20170507.zip

3. SuperSU-v2.79.zip

The system did reboot one time, and then again, and then presented me with the Lineage-OS first time wizard.

Only - I am unable to get past that wizard.

- if I select: "setup as new" I get a: "Setup wizart has stopped" Open again.

- if I select: "Copy your data", I get a: You don't have a network connection. This could be a temporary problem. Try again or connect to anotehr Wi-Fi network.

Only it never asked me to connect to another WiFi.

Do I have to instal the non OMS first?

UPDATE: To answer to my own question.

When using the OMS zip, I was unable to configure the network (Swipe from top down to open preference pane did not work.

When using the lineage-14.1-20170505-UNOFFICIAL-dragon-followmsi.zip, I could open the preference pane and configure the network upfront, before the google-apps made the lineage OS wizard crash.

I was able to actually get through it now. Will check how it works from here.

Cheers :)
[Pixel C Android Development] followmsi:
Pls install BeansGapps .. setupwizard of opengapps has problems.

Or you boot into system once, without opengapps.

Reboot into TWRP and install gapps in the second round - to bypass buggy setupwizard.

Known topic .. opengapps is aware of the problem.

Cheers

Or like this now ...

BeansGapps_SetupWizard_7.1.2_Dragon.zip

Installation:

1. As we want to see the SetupWizard we do a clean install .. wipe system, cache, dalvik, data .. everything except internal storage.

2. install the 7.1.2 ROM of your choice.

3. Install official opengapps package you like ..

4. install BeansGapps_SetupWizard_7.1.2_Manta.zip

5. Install Magisk and/or SuperSu.

6. Reboot into system and wait for the SetupWizard.
[Pixel C Android Development] xda_jm:
Thanks. Will check it out.

Just restoring the previous (stock 7.1.2 apps + configs) to see how that works.

Anyone knows how to disable this "unlocked bootloader 30 second wait on the bootup" crap?

FYI - I had bought the Pixel C in the beginning, thinking that I'll get more freedom on my device than my girls (4) with their iPad's...

Thing is - google has locked down so many thing, and prevent you from doing simple things like disable this absolute Voice/Talk now crap that I can't stand it anymore.

With Lineage OS (as I use on my phones), I realized that I have way more control on my data and how my devices work, reason I wanted it on my Pixel C.

And now this 30secs wait crap? pfff ... Google - please shoot yourself into your foot ;) Kneecaps by preference, it hurts more ;) ;) ;)
[Pixel C Android Development] cam30era:
Sorry to tell you that you can not disable it. You will always get that splash screen during boot unless your bootloader is locked.
[Pixel C Android Development] NYCHitman1:
You don't disable it. It's because it's not an Android bootloader, but a ChromeOS bootloader instead. It also isn't that big of a deal. Relax.
[Pixel C Android Development] frauhottelmann:
Thank you for your effort!

I just got my pixel c and installed Lineage right away :D

You might want to add to the first post that you have to use arm64 versions of gapps and su add-on...
[Pixel C Android Development] followmsi:
You are welcome ...

Yes, will add (arm64) to the first page.
[Pixel C Android Development] creeperlwd:
This is great news for Pixel C owners! Is AICP able to be built without any additions?
[Pixel C Android Development] followmsi:
Don't know .. never tried to build it.

You may have a try yourself :)
[Pixel C Android Development] followmsi:
And fresh LOS versions as well ...

lineage-14.1-20170512-UNOFFICIAL-dragon-followmsi.zip

lineageOMS-14.1-20170512-UNOFFICIAL-dragon-followmsi.zip

Changes:

- Latest LOS and LOS OMS changes

- Latest kernel changes

- Fix for "Wifi direct"

- Enabled Doze (Ambient light)

Enjoy :)
[Pixel C Android Development] xda_jm:
Nice ;) Cool.

So - how do we get these on our Tablets?

Manual Download and install through TWRP? Or would the OMS do?

Sorry - I'm quite new to rooting and doing this manually (so far it has worked, and the losses in terms of data were limited ;) ) ...
[Pixel C Android Development] followmsi:
Yes, manually via TWRP.

Like described on first page.

OMS is Overlay Management Service .. for substratum .. etc.

You may have another lession of flashing and rooting on this ROM ..;)

Cheers
[Pixel C Android Development] Dressiel:
[MENTION=5480152]followmsi[/MENTION]

As always, thx again. I flashed with vendor_ryu-opm1.171019.026_Apr-2018.img and its running fine. First stumbled into a bootloop. The Culprit was Magisk 16.0....with 16.3 all is working as intended.

Strange issue im facing recently: the battery will charge very very slow with the original charger, sometimes nothing happens. Sometimes i get it charged with a OnePlusOne Charger (switching the Cable, USB to USB C from the Nintendo Switch)
[Pixel C Android Development] followmsi:
Yes, Magisk 16.4 works too ..

Never had any issues with USB charger nor USB cable for connecting to PC.

I do have the original charger and ordered the original USB cable from google store.

Never used any other chargers .. No problems so far.
[Pixel C Android Development] bigtreiber:
Any other ideas? HD Video doesn't work, only SD :(
[Pixel C Android Development] followmsi:
https://www.amazon.com/gp/help/customer/display.html?nodeId=201460880

Android Devices

Android Phones & Tablets

We recommend using the Prime Video app for Android phones and tablets. You can download the Prime Video app from*Google Play*or the Galaxy Apps store by searching for Amazon Prime Video, opening the app detail page, and then tapping*Install.

For Android phones, you can also use the Amazon App/Amazon Underground app to access selected video features—including Your Video Library, Watchlist, and purchasing options. For more information, go to*https://www.amazon.com/GetAndroidVideo.

Streaming Video Quality: UHD/HDR/HD on Sony Xperia XZ Premium mobile devices; HDR /HD on Samsung Galaxy Note 7, Galaxy 8, 8+, Galaxy Tab S3, Sony Xperia XZ1 ; SD on all other Android devices

Download Videos: Yes

Purchase Videos: Yes

Parental Controls: Yes

Subtitles*: Yes

Audio Descriptions: Yes

Watchlist: Yes

Auto Play: Yes (Next Up and Recommended titles)

5.1 Audio: No

Live Streaming Special Events (e.g. Sporting Events): Yes (on app version 3.0.212, and up)

Live Streaming (Prime Video Channels): Yes (on app version 3.0.212, and up)

Note:*On compatible devices, the latest version of the Prime Video app supports HDR and HD video playback. We recommend a connection speed of at least 3 Mbps for smooth playback.

Streaming Video Quality: UHD/HDR/HD on Sony Xperia XZ Premium mobile devices; HDR /HD on Samsung Galaxy Note 7, Galaxy 8, 8+, Galaxy Tab S3, Sony Xperia XZ1 ; SD on all other Android devices

No idea if there are any "hacks" existing ...
[Pixel C Android Development] iestyn99:
Strange thing yesterday and again today: couldn't get the tablet started at all, like it was dead. Connected to the charger it did start. OK, I thought, for some reason the battery was drained. But no, when it was started it turned out to be 80% charged. This exact thing happened today again. Only starting if the charger is connected. Running 15.1-20180430, no root or magisk or anything exotic. Does this sound familiar to anyone?
[Pixel C Android Development] bigtreiber:
HD Video used to work with original Google Android, not LOS ... that's why I'm asking about the error message ...
[Pixel C Android Development] Vartom:
I have the same situation on the stock firmware. For my reasons, the firmware is not to blame. Since the device starts the bootloader from the completely off state.
[Pixel C Android Development] followmsi:
Prime HD works on stock .. interesting.

As we have Netflix since a few weeks I made some quick tests too ..

Netflix seems to have similar problems on Lineage-15.1 .. 960x540 only.

Pixel C is listed as supported device for Netflix HD.

DRMinfo app detects L1 but as it looks like the system is requesting L3.

I assume the problem is same like you have with prime hd.

What about HD on Oreo AOSP version and on "old" Nougat custom ROMs ?

The dragon blobs do not change a lot.

Will need to get some more infos .. may test on stock Rom too.

EDIT:

Made a quick check using an older Netflix client (4.8.5) .. 1080p .. no problems.

The client is requesting : default drm .. and not L3.

New L1 lics will be generated inside /data/mediadrm/IDM1013/L1

The new Netflix client is creating L3 lic files.

Did you try to use older version of prime app ?

Edit2:

Now I am running latest Netflix from playstore and still 1080p.

Pls delete /data/mediadrm/IDM1013 folder and reboot.

Does it help for prime hd as well ?
[Pixel C Android Development] wizzardsk:
Installed latest ota update and had to reflash gapps again. After that play services keeps stopping.