yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] followmsi:
Tested the build as well .. no problems.

Never have to reinstall gapps .. the ROM installer do backup and restore without issues.

Same like for Magisk as well .. will be reinstalled via ROM installer too.

Just don't play on system .. you have plenty of space on pixel c ;)

Cheers
[Pixel C Android Development] bigtreiber:
No, DRMInfo still shows only L1, not L3 (also L3 directory exits in /data/mediadrm/IDM1013) :(
[Pixel C Android Development] wizzardsk:
You think I should not integrate app to system? I always do that and never had a problem.
[Pixel C Android Development] followmsi:
Yes .. drminfo app should always show L1 only !

Once deleted the complete IDM1013 folder and rebooted - in L3 subfolder should be just one file.

But in L1 subfolder should be the cert.bin and some more files .. also .lic files, just one at the start.

Over the time the L1 folder will get more and more licenses files.

For me HD content and L1 widevine works fine on Lineage-15.1 for Pixel C ..
[Pixel C Android Development] followmsi:
No ;)

To verify :

Pls format system and install last week ROM, gapps and Magisk .. wipe cache/dalvik and reboot.

Of course - Keep data !

Don't play anything ...and install new ROM from today - just the ROM only.

Watch the addon installer of Magisk...etc.

Wipe cache/dalvik and reboot into system.

Gapps working .. Magisk is working .. pls confirm !

It's nice that you like to play on system ..but I will not be able to help. :)

Cheers
[Pixel C Android Development] wizzardsk:
I already made a factory reset and it seems to work now, just installing all the apps :)
[Pixel C Android Development] followmsi:
Factory reset does not clean system partition .. just as a reminder.

If system is screwed up you just reproduce the root cause with each factory reset.

Cheers
[Pixel C Android Development] wizzardsk:
Ok, i see that freezing and unfreezing apps in link2sd causes problems. Maybe integrating apps to system is not a common thing, but i think that it should not break the system. Perhaps it is just some minor bug that can be solved.
[Pixel C Android Development] followmsi:
May 2018 ..

The May 2018 changes for official Lineage-15.1 have been pushed today .. for dragon device too.

The next official build on Monday will require May vendor.img !

If you like to play with unofficial version ..

lineage-15.1-20180510-UNOFFICIAL-dragon.zip

Changes:

- Google May 2018 security updates

- Latest Lineage changes

- Pls use May 2018 vendor.img !

Just as a reminder ..

May 2018 factory image does include new bootloader: bootloader-dragon-google_smaug.7900.121.0.img

Enjoy :p
[Pixel C Android Development] mightywhites29111971:
I am trying to install the latest official update (May) and am having problems. I tried flashing it in TWRP and then flashing the vendor img but I kept getting into a bootloop into TWRP after the Lineage boot-up screen. I have tried this the other way round with the same result. This was doing a dirty install. Does this update require a clean one? Not sure what the problem is.
[Pixel C Android Development] followmsi:
Today I did install it as well - 20180514 ..no problems.

Started with fresh bootloader first .. installed dirty too.

Magisk 16.4 got automatically reinstalled.

Wiped cache/dalvik and did reboot into system ..

No issues !
[Pixel C Android Development] wizzardsk:
I had to reinstall gapps, but after it works fine.
[Pixel C Android Development] JelleZon:
My device often does not react when pressing the power button to wake it from sleep or power it on.

Can't boot into recovery either.

The device responses, because the LED on the back works but the display does not turn on. After 10-15 minutes it works again.

So ennoying!

Any help?
[Pixel C Android Development] followmsi:
Never had this kind of problems .. can't remember any similar reports either.

If you switch back to stock ROM ?

Same problems ?
[Pixel C Android Development] Verdera11:
I have the same issues, and I'm currently in stock [emoji55]

This happens since 7.0 update I think (in my case)

Enviado desde mi Pixel C mediante Tapatalk
[Pixel C Android Development] wizzardsk:
The latest update was already almost without problem, it seems like that Gapps was still installed, but the play store was just loading and loading. So I flashed Gapps again and the problem was over :)
[Pixel C Android Development] JLowe:
Does anybody if there's a working double tap to wakeup available for the Pixel C, maybe Oreo? I am still on N.
[Pixel C Android Development] wizzardsk:
This is not supported on Pixel C.
[Pixel C Android Development] JLowe:
also wakeup with volume buttons never worked for me in N.

is there any alternative wake-up available which is working maybe in O?
[Pixel C Android Development] followmsi:
Checked wakeup via power button.

Indeed its not working correctly in Oreo.

Made a change for the release from today .. no changes for Nougat anymore - just Oreo.

https://github.com/LineageOS/androi...mmit/56f5d12dbd9020358699f7129f6975765bf0e41e

Tested the change and wakeup is working fine now ..

Thanks for feedback.
[Pixel C Android Development] wizzardsk:
This is the first update I had not have to reflash gapps, just to install google :)
[Pixel C Android Development] JLowe:
that's nice to integrate the button fix for wakeup from volume buttons! hope that ext4 partitions are supported with Oreo. Will upgrade soon then to Oreo.
[Pixel C Android Development] followmsi:
For Oreo I did test NTFS and Ext4 on USB OTG .. both works fine.

RW access for NTFS works too.

ExFat is not supported.

Asked you 2 times to install test kernel on Nougat .. did you finally test ?

Normally it should work on Nougat too.
[Pixel C Android Development] JLowe:
No, didn't test it. I had some hardware issues and tablet is away for repair. when it's back I'll take a go with Oreo.
[Pixel C Android Development] tebra:
Hi [MENTION=5480152]followmsi[/MENTION]

I have a small bug since last 20180528 update: alarm clock didn't make any sound. The system show me that I miss it but it does not ring.

Did you also have this bug on your dragon?
[Pixel C Android Development] followmsi:
Go to sounds and check the current alarm sound .. and choose a new sound and test volume.

Test alarm afterwards.

It seems alarm sounds have changed.

The alarm sound I had configured before is not selectable anymore.

I am not aware of this kind of changes .. general lineage stuff for all devices.
[Pixel C Android Development] ToldYouSo:
After using 15.1 for some time now I am still unable to create folders on my home screen/launcher. It show the ring that it wants to create a folder when I hover the app-icon over another app-icon, but in the end just refuses to create a folder and just puts the icons next to each other... I must have tried a 100 times by now. I still have not figured out why or what is causing this. I have not been able to create any folders since being on 15.1... Is someone else having the same issue and maybe knows how to fix it? Would be very much appreciated!
[Pixel C Android Development] followmsi:
Are you talking about lineage trebuchet launcher or google pixel launcher ?

If you install google launcher via gapps you normally remove trebuchet from system completely.

Yes, Google pixel launcher 8 has issues with folders .. on several devices.

Independent of Lineage or AOSP ROM.

Old pixel launcher version 7, runs on Oreo too, here you can create folders without problems.

I did not made any more investigations ..
[Pixel C Android Development] followmsi:
June 2018 ..

The June 2018 changes for dragon device have been pushed to Lineage github today.

The next official build will require June vendor.img !

Google updated the Bluetooth driver this month.

Yesterday the Lineage signing server had some problems .. it's still building cm-14.1 ROMs.

The 15.1 ROMs should come soon as well.

https://jenkins.lineageos.org/job/android/

Unofficial Lineage version for dragon will come in the next days too ..

Just as a reminder ..

June 2018 factory image does include another new bootloader: bootloader-dragon-google_smaug.7900.126.0.img

Enjoy :p
[Pixel C Android Development] wizzardsk:
So Google is stil supporting this tablet? I heard somewhere that the support was finished some time ago.
[Pixel C Android Development] followmsi:
It stops with the last release of Android 8.1.

Most probably in August or September the new Android P will be released.

Once P is released there will be no Google Pixel C ROMs anymore.

And .. we will have to use the last Oreo vendor.img for unofficial Android P ROMs ;)

Cheers
[Pixel C Android Development] Dressiel:
Ha, I like ;)
[Pixel C Android Development] JLowe:
will get my Tablet back tomorrow and will flash Oreo and give some feedback. Is it recommended to flash always actual bootloader as well as vendor?
[Pixel C Android Development] followmsi:
Yes !
[Pixel C Android Development] tebra:
Hi [MENTION=5480152]followmsi[/MENTION]

Will it be possible to:

Lower the lowest sceen brightness (still to bright in the dark)

Lower the lowest sound volume (still high at lowest volume)

Thanks for your support for the pixel c
[Pixel C Android Development] followmsi:
We need to find solution for all users.

For screen brightness I will have a look ..

For testing I need to switch back to unofficial version.

This will take time .. if you have unofficial ROM running you can test as well, pls let me know.

Sound is quite low already ..at least for me.

For now have a try to edit build.prop ..

ro.config.media_vol_steps=30

Reboot and test media volume .. does it help ?

EDIT:

Pls edit .. in /system/etc/mixer_paths_0.xml

https://github.com/followmsi/android_device_google_dragon/blob/aosp-oreo/mixer_paths_0.xml#L8

Pls with the value .. change to 80 as first test.
[Pixel C Android Development] wizzardsk:
I know my experience is not relevant, because I integrate updated system apps to system and forgot to flash vendor prior update, so I had to clean install the ROM and Gapps again after update, cause Play Services keeped stopping.

Cannot wait for ending the official support from Google, hope there will be less problems with vendor and updates :)
[Pixel C Android Development] ToldYouSo:
Sorry, the Pixel Launcher yes! GAPPS install is set up to remove Trebuchet. Thanks for the info! Gonna try version 7!
[Pixel C Android Development] tebra:
I edit build.prop and it works. The minimum sound level is now much lower. Thanks

What's the advantage of the other solution you add later ?

I don't have a experimental build of lineageos on my dragon to test brightness. If needed I can backup my current installation and flash a fresh experimental to try.

Envoyé de mon Pixel C en utilisant Tapatalk
[Pixel C Android Development] followmsi:
I do prefer the vol_steps solution for sound volume -> better granularity

Will add this into next release .. but 25 steps only.

https://github.com/followmsi/androi...mmit/20e932901a1fdf0e1241c0899623944b5dd1ee08

For the minimum brightness I made another change .. framework-res overlay.

Before we had default minimum value of 10 now we have 2 only. (max. 255)

https://github.com/followmsi/androi...mmit/c8d951bbc53a766954fe910008a7c81b32b093cc

I will make unofficial version first .. if all is fine I will merge into official version !

Once the June sources are ready for Lineage I will make a new unofficial version.

Will come back to you for testing .. :)
[Pixel C Android Development] Agent.Orange:
[MENTION=5480152]followmsi[/MENTION]

Just two questions:

1.) If I pick a wallpaper in one of the Google Pixel Launchers (com.google.android.apps.nexuslauncher or com.google.android.apps.pixelclauncher), the wallpapers are always misaligned and some sort of "zoomed in" and blurry. With the official unrooted 8.1 image from Google and the same Google Pixel Launcher there were no such problems.

2.) If I flash the newest update via TWRP, I always have to install the Pixel Launcher (com.google.android.apps.pixelclauncher) again as a system app in order to use the Google feed on the left. I am not sure how it was on my rooted LG G3 with CM but I think the settings were remembered?

Do you know this kind of problems and maybe how to fix them? Thank you!
[Pixel C Android Development] followmsi:
1) Remember an issue with zoomed wallpapers in trebuchet launcher.

Here it depends on the rotation (horizontal vs. vertical) when you setup the wallpaper.

Just have a try with different rotation on setup.

2)

How do you install your gapps initially ?

Normally the addon installer recognize your old gapps setup and do re-apply after ROM upgrade.

Just wipe system partition only.

Install ROM again and then install the gapps you want .. maybe use config file for fine tuning.

They all will be installed as system apps .. and there should be no need to re-install them manually.

Even you wipe cache/dalvik the settings should be kept.

As last step you have to test with factory reset .. to exclude issues on your current data partition.

Cheers
[Pixel C Android Development] Agent.Orange:
1) Unfortunately that didn't work either. Tried it in horizontal and vertical but wallpapers are always aligned to the far right and are zoomed in. Trebuchet isn't installed because gapps installed com.google.android.apps.nexuslauncher instead. So there must be some issues with the wallpaper picker, because sometimes I cant even move them right.

2) I think the problem is, that gapps package includes the com.google.android.apps.nexuslauncher which is used for pixel phones but not the pixel C, so I installed the com.google.android.apps.pixelclauncher from apk mirror which was on my unrooted Pixel C before. A solution would be to change the installed package to the last one.
[Pixel C Android Development] Rox598:
For what it's worth this issue with the wallpapers happens on stock with a lot of launchers (including the stock "Pixel" launcher) And it's absolutely infuriating
[Pixel C Android Development] followmsi:
I use Nexus launcher.. from normal gapps package and have no problems to swipe left to the google feed.

You may extract latest stock ROM and pull Pixel C launcher for testing .. to see if it works better for your purpose.
[Pixel C Android Development] followmsi:
June 2018 .. unofficial version

lineage-15.1-20180611-UNOFFICIAL-dragon.zip

Changes:

- Google June 2018 security updates

- Latest Lineage changes

- added dragon-keypad.kl

- overlay: screenBrightnessSettingMinimum

- set ro.config.media_vol_steps=25

[MENTION=3288205]tebra[/MENTION] - Pls test screenBrightnessSettingMinimum - thx

Enjoy :p
[Pixel C Android Development] tebra:
I will test this unofficial version but do I have to backup any thing from my official lineage15.1 before switching to the unofficial one?

I want to switch back later to the official one and keep all my data and config.
[Pixel C Android Development] followmsi:
Backup data partition only.

Restore after testing ..

Or .. You can switch between official/unofficial using scripts for key signing.

https://wiki.lineageos.org/signing_builds.html

Thanks
[Pixel C Android Development] tebra:
I am now on last unofficial. So far so good.

I will report any bug about minimum brightness

Envoyé de mon Pixel C en utilisant Tapatalk
[Pixel C Android Development] followmsi:
Are you able to reduce brightness more as before ?

Is it dark enough ?

Thanks for your help !
[Pixel C Android Development] tebra:
Have to wait the night to be sure but it don't look more dark than before

Is it any command to check the real value?

Envoyé de mon Pixel C en utilisant Tapatalk
[Pixel C Android Development] followmsi:
Run as root in terminal app ..

cat /sys/class/backlight/lpm102a188a-backlight/brightness

Thx
[Pixel C Android Development] tebra:
Value is 8 at minimum brightness
[Pixel C Android Development] wizzardsk:
The last update encrypted data again even though I had the latest Magisk installed.
[Pixel C Android Development] followmsi:
Same value on my older build .. the overlay seems not to work.

Will have a look in the next time .. will come back to you once I have more information.

Thanks for your help !
[Pixel C Android Development] followmsi:
A bit late this month .. I just installed new bootloader only .. via fastboot.

Did reboot into recovery and installed official 20180611 release and June vendor.img.

Magisk 16.4 got automatically reinstalled..

Wiped chache and did reboot into system ..

Still not encrypted .. all fine.

Cheers
[Pixel C Android Development] wizzardsk:
The last update went without problems :)
[Pixel C Android Development] LONGXF:
Is there any possibility about Pixel C's Android P？
[Pixel C Android Development] followmsi:
Yes, there is a possibility for P .. First we need to be patient and wait for the AOSP sources. ;)

Once Android P will be published in AOSP we can start building and see what's breaking for Pixel C.

At the same time Lineage and all other teams start to apply all their customization on top on AOSP.

Same procedure as for Oreo before ..

Pixel C is not a "treble" device .. we will see the impact later on.
[Pixel C Android Development] LONGXF:
Google said Pixel C Won't have an official Android9.0 ，Is it very hard to make an unofficial 9.0？Because I see that Nexus's Developers seem much more than Pixel C's。
[Pixel C Android Development] followmsi:
Like you said - no official Android P releases for Pixel C !

Today I can't tell you if it's hard to build.

Normally the fully working sources are published at go-live date and not before.

Made a quick search .. DP3 is not too hard to build ..

https://groups.google.com/forum/#!topic/android-building/JfgzeR_S9N4

Actually I did start a DP3 test build last night .. It's building .. but not sure if and how it's running.

Needs to be tested ..

AOSP_Android-P-DP3_dragon-ota-eng.followmsi.zip
[Pixel C Android Development] followmsi:
I did not forget you .. but I dont find a solution right now.

Dont want to make the brightness darker for all of us - just the possibility to reduce even more.

Not sure if and by when I will find the appropriate solution for this issue.

Did you play with the values ?

echo "2" > /sys/class/backlight/lpm102a188a-backlight/brightness

Did you try 3rd party tools/apps as well ?

Cheers
[Pixel C Android Development] tebra:
yes it works very well with echo "2" > /sys/class/backlight/lpm102a188a-backlight/brightness command.

The screen don't turn off and the brithness goes to the minimal value
[Pixel C Android Development] followmsi:
Do you still run unofficial build ?

If yes, pls replace /system/framework/framework-res.apk from download folder and reboot directly afterwards.

Or replace via recovery .. etc.

If you replace on Official build system will not boot due signing.

Does it help ?

Cheers
[Pixel C Android Development] tebra:
Sorry I'm back to official build because I had some random reboot with unofficial
[Pixel C Android Development] wizzardsk:
The last update cause the encryption again, had to format data and reinstall Magisk.
[Pixel C Android Development] LONGXF:
Thanks for your patient answer.Hope you can make it.You are quite nice guys.:svetius:
[Pixel C Android Development] followmsi:
The overlay itself is working fine .. but it does not help in our case.

You can check the current Android display settings brightness values via command line too ..

To get the current value .. (0-255) .. converted in UI display settings to 0-100.

settings get system screen_brightness

The same via adb ..

adb shell settings get system screen_brightness

You can set the "display settings" value like this ..

settings put system screen_brightness 2

Even to 0 if you want - no change.

The actual brightness value does not match .. it never goes below "8".

cat /sys/class/backlight/lpm102a188a-backlight/brightness

If you change the "display setting" values (0-10) the actual brightness value stays on "8".

The actual brightness value starts to increase somewhere above 10 ..

For this reason it does not help to allow reducing the minimum setting from 10 (default) to 2 or even 0.

The actual brightness does not change accordingly.

We need to match minimal display settings with minimal actual brightness.

Maybe I will find a way to match them better .. right now I have no time for further "brightness" investigations.
[Pixel C Android Development] followmsi:
The official version have had an "one-time" build issue 2 months ago.

There was one broken build in April.

For this reason I did switch to official version and tested a lot of the official Monday builds.

I have had no issues aferwards.

Today I have made a new unofficial version and did switch back .. lineage-15.1-20180627-UNOFFICIAL-dragon.zip

For me it's more easy and more flexible to change Android versions on unofficial data partition.

Of course, you can migrate data all the time .. but for the next time I will stay on unofficial builds.

Maybe switching to RR as well .. etc.

Thanks for all your testing and reports ..

Cheers
[Pixel C Android Development] LONGXF:
I have a question,developer.

Is Pixel C supporting Project tremble?
[Pixel C Android Development] followmsi:
No .. pixel c is not a project treble device.
[Pixel C Android Development] xda_jm:
Hi folks,

running latest official build updated through OTA, July 2 2018, latest Vendor Image, followmsi's kernel tegra-3.18_kernel_dragon_v180605_unicorn-xceed-followmsi.

On every tablet start I get the an error message that the application oClock has stopped working/crashed.

Then - trying to upgrade all apps, the clock app fails with the following Error message.

Can't install app

"Clock" can't be installed. Try again, and if the problem continues, get helpo troubelshooting. (Error code: -505)

Any clue what may be wrong? or what I could do?
[Pixel C Android Development] followmsi:
Which clock app ?

How do you upgrade system apps .. e.g. clock ?

Do you use gapps ?

Which version ? .. e.g. using Google clock app ?

Try cleaning cache/data of the affected clock apps.

You may format system only and install ROM and gapps from scratch.

Sorry, otherwise you will have to do factory reset.

Good luck !
[Pixel C Android Development] LONGXF:
So Android P is impossible for pixel C？
[Pixel C Android Development] Monazite:
Possible, but need work. Android P never optimized for tablets, the whole system UI is in a mess right now.☹️
[Pixel C Android Development] followmsi:
July 2018 ..

The July 2018 changes for dragon device and kernel have been pushed to Lineage github.

The next official build will require July vendor.img !

Unofficial Lineage version for dragon will come in the next days too ..

Due to holiday season the August changes and releases will be delayed !

Enjoy :p
[Pixel C Android Development] followmsi:
July 2018 .. unofficial version

lineage-15.1-20180707-UNOFFICIAL-dragon.zip

Changes:

- Google July 2018 security updates

- disable bionic warnings

- Latest LineageOS changes

Enjoy :p
[Pixel C Android Development] frauhottelmann:
Bionic warnings?
[Pixel C Android Development] followmsi:
disables bionic linker warnings ..

https://github.com/followmsi/androi...mmit/7f20f2d833c9498a83c216f0f9b69b73a54d6dad
[Pixel C Android Development] wizzardsk:
The last update caused encryption again despite of using Magisk. Time to move on to AOSP :)
[Pixel C Android Development] Agent.Orange:
Is on last update from 2018-07-09 the encryption enabled as well after flashing supersu?
[Pixel C Android Development] wizzardsk:
Dont know. I switched to unofficial LOS 15.1 and will install the updates manually and Magisk after each update.
[Pixel C Android Development] tebra:
For informations, it is possible to use DisplayLink adapter to display your pixel C to external display. It works very vell with LOS 15.1
[Pixel C Android Development] Dressiel:
Hiho [MENTION=5480152]followmsi[/MENTION]

Is it possible to upload the August-VendorImage to your GoogleDrive ?

Edit:

Have Fun :p

Thank you in advance
[Pixel C Android Development] NYCHitman1:
https://cdn.dirtyunicorns.com/api/download/dragon/vendor_images/dragon_opm4-171019-021y1.img
[Pixel C Android Development] Dressiel:
Thank you
[Pixel C Android Development] followmsi:
Back from holidays ..

Have uploaded the August vendor.img now - will make the related device and kernel changes for lineage-15.1 soon.

Cheers