yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] JLowe:
Dear followmsi,

just know that my Xiaomi Mi5 with Los 13.1 can play 24bit audio flac files by stock and my Htc with Android 5 too.

can't remember if i tested this before with Pixel C. Would be really nice to have this for the Pixel C too.
[Pixel C Android Development] followmsi:
Ok .. I am not the audio specialist either.

Just downloaded a flac 96/24 audio sample ..

10-27 13:52:21.739 D/VLC (9189): [0000007116907688/23fa] flac decoder: channels:2 samplerate:96000 bitspersamples:24

Not sure about 192/24..

How do you determine that it's not working ?
[Pixel C Android Development] JLowe:
VLC has his own Decoder inside.

Test it with stock Music-Player i.e. Eleven.

Maybe there must be just some change in the configuration files for decoding HRA (High Res Audio).

https://www.reddit.com/r/Android/comments/73v3o6/this_is_how_you_change_the_sample_rate_to_441_khz/

The files you have to change:

a2dp_audio_policy_configurations.xml

audio.policy.conf

audio.policy.configuration.xml

r_submix_audio_policy_configurations.xml

usb_audio_policy_configuration.xml

https://developer.android.com/reference/android/media/MediaCodecInfo.CodecCapabilities.html

https://github.com/LineageOS?utf8=%E2%9C%93&q=Audio&type=&language=

Maybe some other devs from Google Pixel smartphone knows how to implement.
[Pixel C Android Development] followmsi:
Just tested the same 24/96 flac file on music app .. was playing fine.

Not sure about actual rates.

For example just changing the sample rate from 48 to 44.1 will not implement proper hi-res audio.

Pls figure out a proper solution for impmentation. ;)

I will need time to sort it out and I don't have the time.

But I am happy to implement the required changes into official Lineage sources for dragon device.

Cheers
[Pixel C Android Development] JLowe:
I am not a developer and I can't figure out a solution for you. If so I would compile my own Roms, lol. I can tell you that 24Bit Audio Playback isn't working. In system/etc there you'll find audio_policy_configuration.xml

So there's only 16Bit and no frequency above 48khz. So this must be configured for 24bit up to 192khz

Speaker
Built-In Mic

Speaker

Maybe you can just compare this configuration file with your other Rom, this takes 1 minute checking system/etc. Maybe you have this time ;)

And another solution would be just asking another LOS Dev for implementing 24Bit Playback maybe they know a solution.

Update: LOS 13.1 works as expected. So something is broken in LOS14.
[Pixel C Android Development] followmsi:
We are talking about Pixel C here only !

I have asked you before .. on which ROM works 24bit on Pixel C ?

The audio_policy_configuration.xml is located in device tree ..

https://github.com/followmsi/androi...blob/aosp-oreo/audio_policy_configuration.xml

One version for each branch .. but this file has not changed.

For this reason this file is identical on official LOS-14.1 and all my other Pixel C ROMs. (nougat and oreo)

You can edit this file .. mount your system partition RW and replace it with your changed version.

Set permissions correctly and reboot.

This way you can test all the various scenarios by changing this file.

Maybe just something like this .. from here .. https://android.googlesource.com/de...roid-8.0.0_r17/audio_policy_configuration.xml

<mixPort name="primary input" role="sink">
<profile name="" format="AUDIO_FORMAT_PCM_8_24_BIT"
samplingRates="8000,11025,12000,16000,22050,24000,32000,44100,48000"
channelMasks="AUDIO_CHANNEL_IN_MONO,AUDIO_CHANNEL_IN_STEREO,AUDIO_CHANNEL_IN_FRONT_BACK,AUDIO_CHANNEL_INDEX_MASK_3"/>
</mixPort>

You need to add higher sampling rates for testing too ..

All needs to be tested and checked for Pixel C .. and this will take time .. a little bit more as 1 minute. :p

And if you find the correct values/config we can implement into sources for all users on all ROMs

Thats the way open source works.

You dont need to be a "developer" .. not for changing this file and not for building ROMs either :)
[Pixel C Android Development] JLowe:
It's working on this Rom here

[ROM] Temasek's Unofficial CM-13.0.1 [06 August 2016]

https://xdaforums.com/pixel-c/development/rom-temasek-s-unofficial-cm-13-0-t3401037
[Pixel C Android Development] followmsi:
Ok .. on Marshmallow it's working.

If you check the device tree for cm-13 there is also no config above 48000 and 16 bit.

For me it looks like the device tree config was not related at this time, it still was working.

But most probably it has to be changed now ..

Again .. how do you determine / test 24 bit output ?

Which app .. or logs are you using to see it's either working or not ?

EDIT:

Tested on AOSP Oreo ..

24bit flac with max 96000 are playing fine via speakers.

Above is not supported ..

10-28 23:47:28.471 E/FLACExtractor(241): unsupported sample rate 192000

Not sure if the device tree needs to be changed at all.

EDIT2:

https://github.com/LineageOS/androi...0/media/libstagefright/FLACExtractor.cpp#L536

https://github.com/LineageOS/android_frameworks_av/commit/b2c7134f634b8798b22b5ebe03b0b258b1d7196d

https://github.com/LineageOS/androi...a7e8ae0#diff-7f458eb8cf8545b3b0e2cc6ee37418cf

https://github.com/LineageOS/androi...d/media/libstagefright/FLACExtractor.cpp#L527

On LineagOS 14.1 it should work too.. same changes like in Android M.

The chnages are not part of Oreo yet .. here it's blocking at 96000.

Pls send logcat of LOS Nougat ..

Pls test 24/96000 and 24/192000.
[Pixel C Android Development] JLowe:
Dear followmsi,

it seems not (only) a matter of these configuration files in sysstem/etc, there must be some libraries missing. What I wrote is only a matter of native support for playback Hi-Res Files which works in mentioned unofficial LOS 13.1 (i.e. 24bit Flac). As I wrote above you just need to use the standard system music app which use the system decoders (so here: Eleven). VLC are using his own app decoders. The playback in LOS 14.1 with Eleven doesn't bring any output of 24Bit Flac-Files for me. This isn't a matter of Android native transcoding 24bit to 16Bit 44.1Khz. It's a matter of just playing back Hi-Res Files which should natively working also in LOS 14.1.

I am checking a logcat if I am flashing again LOS 14.1, atm I stay with 13.1.

Thank you for your efforts!
[Pixel C Android Development] followmsi:
The tests above were made on Oreo AOSP music.apk .. no VLC anymore.

I am on Oreo and will not go back to Nougat anymore.

The related code is similar on Oreo too .. blocking flac at 96000 - per default.

Which is working fine on Oreo AOSP music.apk, at least it opens and plays the 24/96000 flac file.

Did you test LOS 15 too ?

Did you test AOSP (Nougat/Oreo) e.g. music.apk at all ?

What about stock Nougat/Oreo images .. using another "native" player ?

Except for device tree and blobs all cm-14.1 ROMs for all devices are using the same sources, depending on the hardware.

The blobs are opening/playing fine on Oreo (AOSP).

And yes .. transcoding is another issue.

If you have some logs .. pls let me know.

I would love to have it running properly on all Android versions for dragon device, but as said before I will not drive this "project".

Cheers
[Pixel C Android Development] followmsi:
Another snapshot of the ongoing lineage-15.0 development ..

lineage-15.0-20171103-UNOFFICIAL-dragon-followmsi.zip

Meanwhile Opengapps for Oreo has become official too.

No webview updates are done for this release .. pls install Chrome/Webview via opengapps.

Used latest lineage-15.0 kernel sources.

Pls use October 2017 vendor.img for this build.

And still using "my" installer ..

Enjoy :p
[Pixel C Android Development] followmsi:
If you want to play with microg ..

https://lineage.microg.org

https://download.lineage.microg.org/dragon/

Cheers
[Pixel C Android Development] Mother_Teresa:
Which file is it, I only see the earlier version?
[Pixel C Android Development] followmsi:
It's there ;)

Moved previous version into "OLD" subfolder.

Just try via browser .. etc.

Cheers
[Pixel C Android Development] Mother_Teresa:
Somehow it didn't show in my main Google account.

I dirty flashed it and wiped cache and flashed the October vendor image.

After boot 8t showed a 'finishing android update' message which ended in a soft reboot (5s to reload}.

This repeats itself and as I didn't want to factory reset I went back to the previous version.
[Pixel C Android Development] followmsi:
You are coming from previous LOS version ?

Or another ROM in between ?

Pls try to generate logs next time ..
[Pixel C Android Development] Mother_Teresa:
What is the quick and easy way to provide logs when I flash the new build?

Key here is that I did not do a factory reset as it takes time and effort to reinstall the apps.

It seemed that the mentioned 'android update' process, after first boot, looped.
[Pixel C Android Development] tux95:
I had the same problem too... Went back to the older build.
[Pixel C Android Development] followmsi:
Start logcat while your are booting the system .. ( adb logcat )
[Pixel C Android Development] followmsi:
Same question here ..

You are coming directly from previous LOS 15 version ?

Or another ROM in between ?

Which vendor.img has been used ? October ?

Pls provide some logs ..
[Pixel C Android Development] tux95:
Yes directly from pevious Los. And flashed new vendor image before updating. Will provide logs later.
[Pixel C Android Development] followmsi:
Did you clear cache and dalvik cache too .

Yes, pls provide logs ..

Thanks
[Pixel C Android Development] followmsi:
Finally .. the LineageOS team has updated the sources including November 2017 security fixes.

They were still running on August security level till last week ..

lineage-15.0-20171110-UNOFFICIAL-dragon-followmsi.zip

Changes:

- google security fixes for Nov 2017 -> android-8.0.0_r30

- new Kernel -> google security fixes for Nov 2017

- added stable WebView 62.0.3202.xx for better Oreo support.

- Still using "my" installer .. E3004 error on regular Lineage installer

Pls use November 2017 vendor.img for this build.

Sources:

https://github.com/followmsi/manifests/tree/dragon-lineage-15.0

https://github.com/followmsi/android_kernel_tegra/tree/lineage-15.0

Enjoy :p
[Pixel C Android Development] Mother_Teresa:
Not to sound rude but have you learned/reproduced why me and tux95 got the same -bootlooping- message after flashing over the earlier 15 beta?

We both flashed the vendor image with oktober in the name. Do know you also have another vendor image file that could be an october version also.

I am using the L09 phone btw, it could be the cause.

The feedback is provided because I appreciate the effort, I just don't have the experience and time to process and share logs as I need to rollback immediately when it even fails to load/work :)

offtopic: I lack knowledge to answer this other thread/support request (stuck at logo, can not shutdown) ->

https://xdaforums.com/mate-7/help/mate-7-l-09-bricked-dead-t3701774
[Pixel C Android Development] followmsi:
No .. I did not replicate your issue.

I have asked for logs and my time is limited.

There is just ONE vendor.img existing .. which is coming from monthly Google factory images.

Every month I pull the vendor.img and upload the same file to gdrive folder.

The device tree will be changed to let lineage know which vendor.img to use. (fingerprint)

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

If you not install the correct vendor.img you get a notification message after booting into system.

Pls install latest version and keep you October vendor.img .. once you see the message you can reboot into TWRP and just install the new vendor.img for November.

Do you still have problems on latest version ?

Sorry, no ideas for your phone problem ..

Enjoy your weekend ..
[Pixel C Android Development] followmsi:
Quick hotfix release !

Sorry, but the ROM from yesterday did not boot at all.

I was playing with vendor files for the new TWRP version based on Oreo sources :)

lineage-15.0-20171111-UNOFFICIAL-dragon-followmsi.zip

Changes:

- google security fixes for Nov 2017 -> android-8.0.0_r30

- new Kernel -> google security fixes for Nov 2017

- added stable WebView 62.0.3202.xx for better Oreo support.

- Still using "my" installer .. E3004 error on regular Lineage installer

Pls use November 2017 vendor.img for this build.

Sources:

https://github.com/followmsi/manifests/tree/dragon-lineage-15.0

https://github.com/followmsi/android_kernel_tegra/tree/lineage-15.0

Switched from November AOSP Oreo ROM to this lineage-15.0 ROM without any problems.

I wiped system, cache and dalvik but kept my /data partition.

Installed the ROM, Gapps (stock version with config file) and Magisk 14.0.

All gapps are working fine .. Magisk seems to work fine .. no problems at all.

Enjoy :p

EDIT:

It seems Lineage-15.0 has some issues with Magisk 14.0 on dragon.

Fist boot was fine .. no issues. Did reboot again and the boot time was very long.

Did reboot another time and it was booting even longer - strange !

Quick logcat check .. MediaService had problems .. Youtube not working .. Chrome did not work too .. etc.

Booted into TWRP and re-flashed the boot.img only - but installed SuperSU 2.82SR5 !

And voila .. boot time 3 seconds and all is working again.

I remember the issue from Nexus 10 Oreo builds.

Still strange .. AOSP Oreo ROM for dragon does not have this problems with Magisk.

Maybe it's related to version 14.0 .. I did not test any newer BETA versions.

EDIT2:

Reflashed boot.img and tested Magisk 14.3 BETA .. seems to solve the issue on lineage-15.0

Did 3 test reboots .. all fine .. 3 seconds only.

Changelog of Magisk ..

v14.3 (1437)

- [MagiskBoot] Fix Pixel C installtion

Enjoy your weekend :)
[Pixel C Android Development] tux95:
Still the same problem... I tried to capture some logs, but there are so much. My shell-windows loses most of them...
[Pixel C Android Development] followmsi:
Save logs into file .. adb logcat > file.txt

Did you try with fresh restore of latest data backup ?

If you move to latest AOSP build .. for testing .. same problems ?

Wipe system, cache, and dalvik .. install ROM, gapps and magisk.

Did you install opengapps again ?

Pls use stock package and include chrome.

Reboot and start grabbing logs into text file ..

Sorry .. can't help you better.
[Pixel C Android Development] sxg75:
Great work - was coming from 20170704-LOS14.1. Flashed BL, Vendor, Wiped everything (except internal sd), flashed ROM, OpenGapps (Stock), Magisk.

Still testing.

Titanium 8.1 (latest oreo version) was not able to restore Android-ID (may be Titanium problem).

Where Is original LOS15 trebuchet launcher? Is it removed because "stock opengapps" were flashed? Would "full" opengapps also work, trying to "keep" LOS standard apps?
[Pixel C Android Development] 12paq:
So funny! I just spent awhile today trying to figure out Magisk root on a very early build of LOS 15 for my new Essential Phone. I finally did but, I should have just checked back here at my reliable and well maintained, largely by you, Pixel C forums. Lol

Note to self: when all is new check betas!

Thanks for being on it dev. :)
[Pixel C Android Development] followmsi:
Just checked trebuchet .. it's part of the ROM (system/priv-app) .. my gapps installation did remove it as well.

Use config file to keep it..

https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options

Prevent automatic Stock removals

When installing a Google app that can replace a stock app, the stock app is automatically removed. For example, if you are installing Android Messages, then the Stock SMS app will automatically be removed.

To prevent the automatic removal of the stock apps when using the Open GApps Super/Stock package, type the keyword option preceded by a '+' as shown below:

Cheers
[Pixel C Android Development] carbon dioxide:
Dear followmsi,

Thanks for your good work! The rom runs very smoothly! Btw Is it possible to add an option to hide the navigation bar? Cause it'll be even better if I can fully utilize the whole screen.
[Pixel C Android Development] frauhottelmann:
Settings -> Display -> Extended Desktop
[Pixel C Android Development] followmsi:
Is expanded desktop feature working in Lineage for Nougat (cm-14.1) on Pixel C ?

Can't remember ;)

It's missing .. not sure if it's still under development or never been part of dragon ROM.

Maybe it needs to be activated via device overlay .. etc. ?

Needs to be checked ..
[Pixel C Android Development] frauhottelmann:
Oh, I just assumed it works on all lineage devices ?
[Pixel C Android Development] followmsi:
Actually me too.

If not activated for all devices via common sources/configs it needs to be activated per device.

I guess like doze and some other features it has to be activated via framework overlay in device tree.

Yes.. needs to be checked.

Do you know how to activate via device tree change .. if at all ?
[Pixel C Android Development] followmsi:
Quick info for official cm-14.1 weeklies ..

https://github.com/LineageOS/hudson/commit/d43cb96ea8fd3dbcc4ff72256dd2153630ab4afe

The dragon build will be made on Tuesday now and not on Monday anymore.

The first build every Tuesday ;)

Cheers
[Pixel C Android Development] kurze12:
Is there an appointment for an official LineageOS 15?

I am very satisfied with LineageOS14.1. I have a small problem. The screen does not wake up with the volume tase, even though it is set. It only works shortly after turning off the screen.
[Pixel C Android Development] followmsi:
No .. don't know any dates for official Oreo .. some rumors about beginning of next year.

"Short period" .. when does it not work anymore ?

After entering sleep mode ?

Did you test different 14.1 builds .. all the same issue ?

You are using the included linage kernel ?

Actually I'm have switched to Oreo and exactly this feature has to be taken out as it's not ready for Oreo.

https://github.com/LineageOS/androi...mmit/e479bec2775f5c70458e96de65daa90e03f69bba

Sorry, but not sure if this issue will be fixed for Nougat anymore ..

If it's a general problem it will be fixed in one of the next weeklies.

But I will not have the time to go back to Nougat anymore and start searching for this issue.

Hope you understand ..

Cheers
[Pixel C Android Development] followmsi:
Just uploading the fist Lineage 15.1 "sneak preview" ..
[Pixel C Android Development] followmsi:
And here we go .. it's a first version .. very early developing.

I have used the "staging/lineage-15.1" branch for building.

Just running this version .. seems to be ok.

Maybe some dirty installation issues are left :)

Used latest Magisk 14.5 BETA .. also fine.

lineage-15.1-20171209-UNOFFICIAL-dragon-followmsi.zip

Changes:

- Android 8.1 -> android-8.1.0_r1

- new Kernel -> google security fixes for Dec 2017

- Pls use December 2017 (Oreo 8.1) vendor.img for this build.

- The update-binary has been changed too .. Oreo 8.1 is using system.new.dat.br

- The ".br" (brotli compression) does more compression as before .. the otapackage.zip is about 30MB smaller now.

Opengapps packages for Oreo 8.1 ..

open_gapps-arm64-8.1-pico-20171207-UNOFFICIAL.zip

open_gapps-arm64-8.1-stock-20171207-UNOFFICIAL.zip

Sources:

https://github.com/followmsi/manifests/tree/dragon-lineage-15.1

https://github.com/followmsi/android_kernel_tegra/tree/lineage-15.1

Enjoy :p
[Pixel C Android Development] Mother_Teresa:
I appreciate the effort and that is why I went installing it again, after previously having been forced to fallback to a backup when I tried an earlier version over the initial 8 version :)

The short; a dirtfyflash got me in the same pickle.

At first boot, when the gui already loaded, some notification "finishing android update" caused a bootloop.

I did install the december vendor.img and proceeded with a full wipe that got rid of the bootloop.

Now I was unable to create/login with my Google account as the playstore services crashes. Deleting cache did not help nor (re)installing the provided 8.1 gapps.

Flashing the official OTA was denied due to the package being not new enough.

I even ended up flashing the kernel.

Finally I restored the initial 8.0 version, went for fac reset there in the settings.

From there I flashed the recent 8.1 and vendor and no more errors. No idea why which caused what etc.
[Pixel C Android Development] followmsi:
Had the "finishing android update" bootloop too .. after testing aosp rom the update was done and los did work too.

All with the same dirty data partition.

Sorry, still very early developing.

In general if you switch from official to unofficial you will have problems with dirty install.

You need the script to change keys.

Fresh install and crashing services is related to missing chrome e.g. webview installation. (Via gapps)

Once installed the play services are working too.

The next 15.1 release will be hopefully more stable.

But I still run this build today .. no more problems.

Cheers
[Pixel C Android Development] sabrdawg:
15.1 is running flawlessly! The 8.1 Open gapps package I had worked without a hitch :) I'm rooted and backing up all my apps via TB. Thanks for all your hard work!
[Pixel C Android Development] Mother_Teresa:
I cannot get Netflix to work. Could you share a working version? Also, sometimes Nova launcher closes.

Thanks ?
[Pixel C Android Development] julz24:
Fully backed up and wiped the device. The ROM & Gapps installed fine. Setup of my account went flawlessly, except a FC "music has stopped" during the process but app works fine and no FC error message.

Always very happy to see support from the community for this device!!

Can something be done about the very small Navbar?

I know its a work in progress but i always enjoy the new bleu Ui and the Navbar animations and all other modifications we can do with custom ROMs. Will those features be available when the official ROM is completed? Not asking for ETA, just asking!!

Great work as usual!!
[Pixel C Android Development] tebra:
Hello,

I'm interested in LineageOS for Pixel C but can you tel me if the screen brightness can be lower than on the official google ROM?

And is it possible to enable "night mode" with LineageOS ROM? Official 8.0 google ROM don't have that option...

Thanks
[Pixel C Android Development] followmsi:
Yes, will have a look into the small navbar icons ..

All the other lineage "features" should come later .. when lineage-15.1 development is finished.

I maintain the device only .. not much influence what will be part of "lineage" in next relases.

And still no info when 15.1 goes live .. ;)
[Pixel C Android Development] followmsi:
Sorry, no idea about brightness level .. but in unofficial 15.0/15.1 there is night mode available.

Official 14.1 still does not have it .. but soon.

AOSP ROM does have night mode too.

Inside the gdrive folder is an overlay apk which enables night mode on stock ROM too.

Cheers
[Pixel C Android Development] tebra:
Is root needed to use overlay app on your gdrive?
[Pixel C Android Development] followmsi:
This no app .. it's an overlay packaged as apk.

Root is required .. to be able to mount system partition RW and create overlay folder, if missing.

https://github.com/pratik98/Runtime...tep-to-install-and-uninstall-overlay-packages
[Pixel C Android Development] tebra:
Hi [MENTION=5480152]followmsi[/MENTION] any news about lineageos 15.1 "auto build" on lineageos website ?

Thank you for your build for dragon

Envoyé de mon Pixel C en utilisant Tapatalk
[Pixel C Android Development] gajoldeluxe:
is it possible to have more users than five?
[Pixel C Android Development] followmsi:
Sorry .. no idea about go live date.

Will make another test build, based on January security fixes in the next days.

Otherwise we have to wait ..

Cheers