yashsingh1/xdaforums huggingface dataset:
[Pixel C Android Development] brackenhill_mob:
Weird screen "blackout" problem started

Since installing the July snapshot I've been suffering from the screen shutting off when the battery drops to around 25%. The tablet is still working but I cannot see anything on the screen. The Google fora are full of complaints about this both for our C and other Pixel devices. The common thread for the C appears to be that it started with the July snapshot.

Does anyone ( [MENTION=5480152]followmsi[/MENTION]?) have a copy of the June snapshot and vendor.img file saved somewhere so that I can test this? I cleared out my old ROMs directory before I went on holiday as everything seemed to be working fine - the issue kicked off on 2nd day I was away!! I normally put my tablet on charge around 30% which is why I hadn't seen it before.

On a side note, a) does anyone know if this issue affects the Lineage ROM and/or b) would the [MENTION=5480152]followmsi[/MENTION] kernel be likely to fix this?

Thanks
[Pixel C Android Development] followmsi:
Did you test and run AOSP version or official monthly stock google ROM ?

Did you test June stock ROM already?

https://dl.google.com/dl/android/aosp/ryu-opm4.171019.021.d1-factory-d198e485.zip

Now you want to test June AOSP version ?

Pls test August version first.

Currently running lineage-15.1 and do not have any screen issues at 25% and below.

Cheers
[Pixel C Android Development] brackenhill_mob:
Would you believe it - as I saw your message the screen has gone dark again. Using your August AOSP rom which I installed after writing my earlier message. Battery this time was 35%.

I haven't used stock for over 9 months - always your AOSP version :)

As far as I can tell the issue started with the July update. Others in the Google fora are saying the same thing and screaming at Google to get a fix out so I'm confident that the July update is the starting point for the issue hence my request for your June AOSP image to test to see if I'm correct. This issue doesn't seem to affect every C which is frustrating.

I'll try now with your kernel with the August update to see if that makes any difference.

[MENTION=5480152]followmsi[/MENTION] If you still have your June AOSP and vendor image to hand, I'd be grateful for a link so I can see if that fixes it. If not, and assuming your kernel doesn't fix it, I'll have to try Lineage

Thanks
[Pixel C Android Development] followmsi:
Ok .. thanks for better explanation !

I have re-uploaded the June AOSP ROM and vendor.img again. (r31)

Not sure if the "unified" kernel does fix it .. needs to be tested.

As mentioned before, I don't have this problem at all.

Pls test AOSP kernel first and test with "unified" kernel afterwards.

Pls test Lineage-15.1 and/or RR too.

Pls let me know your testing results ..

Good luck !
[Pixel C Android Development] brackenhill_mob:
Thanks for the June images - I've grabbed them.

August AOSP update with AOSP kernel is borked.

Now testing with the unified kernel. If this borks, I'll try the June update to confirm or disprove my theory. If that fails, I'll try Lineage or RR.

I'm now away for a week so I might not be able to report back for a few days.
[Pixel C Android Development] brackenhill_mob:
Ok I've finished my testing.

June image - works

July image - borked

August image - semi-borked

Why semi-borked? Because when August was installed after July, the Pixel went comatose at 40% which was worse than July. But when installed after June it worked fine - go figure!

Anyway I've now switched to Lineage which is butter smooth and has no battery issues. I should have done this ages ago :)
[Pixel C Android Development] followmsi:
Ok .. thanks for testing and your results.

Still no idea what's wrong in July build.

Are more user affected by this problem ?
[Pixel C Android Development] followmsi:
Android Pie (BETA) ..

AOSP_9.0.0_r1_PPR1.180610.009_dragon-ota-eng.followmsi_V3.zip

Known issues:

- Camera

- MTP

- DRM -> L3 (SD) works fine - L1 (HD) still needs testing

Installation:

1. Boot into TWRP (3.2.3)

2. Wipe system only !

3. Install AOSP_9.0.0_r1_PPR1.180610.009_dragon-ota-eng.followmsi_V3.zip

4. Install Opengapps

6. install Magisk.zip (tested with 17.1)

7. Wipe cache and dalvik

8. Reboot into system ..

- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)

Opengapps:

Pls use opengapps from here .. https://xdaforums.com/android/development/gapps-unofficial-opengapps-builds-t3828141

Or any other package for Android 9.0 (ARM64).

And big thanks to [MENTION=2489052]NYCHitman1[/MENTION] (Dirty Unicorn) !

Without his work the Android Pie project would not have been possible !

Enjoy ..:p
[Pixel C Android Development] Vartom:
Can I put over the official firmware?

ps I have disabled encryption.

What other bugs are there?
[Pixel C Android Development] wizzardsk:
I wanted to sell the Pixel, but it seems I will let it for some time yet :)
[Pixel C Android Development] NYCHitman1:
You no longer use the stock vendor.img. A new one is flashed with each build.

As for bugs.. many remain to be seen -- I'm still sifting through things.
[Pixel C Android Development] wizzardsk:
It seems that apk installer tool keeps crashing, I cannot install magisk manager.

It is not there after flashing magisk zip.

Edit: after clean flash of aosp 8 with magisk it works.

Edit2: now i dont have recent apps button :)
[Pixel C Android Development] Monazite:
AOSP 9 have too many UI bugs... disappeared recents button is one of them...hope 9.1 can fix them
[Pixel C Android Development] NYCHitman1:
That's not a bug. Recents is controlled by the center navigation gestures now.
[Pixel C Android Development] Monazite:
P's gesture on a large screen device is terrible...?
[Pixel C Android Development] NYCHitman1:
I don't disagree, but it is what it is.
[Pixel C Android Development] Vartom:
in P. Another bug. No connection to the PC for data transfer. The PC does not see the disk.

HW decoder now works for me. after some recent patches [MENTION=5480152]followmsi[/MENTION].

---------- Post added at 08:06 PM ---------- Previous post was at 08:06 PM ----------

in P. Another bug. No connection to the PC for data transfer. The PC does not see the disk.

HW decoder now works for me. after some recent patches [MENTION=5480152]followmsi[/MENTION].
[Pixel C Android Development] NYCHitman1:
You could've just cherry-picked the commits I added for mediacodec and mediaextractor lol. Kinda silly to kang it.
[Pixel C Android Development] followmsi:
Mtp has changed in pie .. needs to be checked.

Hw decoding ? .. is working.

YouTube even 1440p ;)

You mean drm L1 ?

The changes on your GitHub ?
[Pixel C Android Development] Vartom:
I checked the availability of the HW + mode in the MX player, it did not work, playback was in the SW mode.

I do not deny the possibility that something was broken in my previous build. For which I used

https://github.com/followmsi/androi...mits/7c41f8cbc422cda0d4bfafbc5470b0b87104e1b9

and

https://github.com/nychitman1/android_vendor_nvidia .

DRM L1 was determined by the DRM info program. I did not check the reliability of his work.
[Pixel C Android Development] Burakki:
Hi,

thank you so much for your effort and work, I appreciate it very much.

I have a problem. I come from aosp of google, android 8.1 stock.

Following the instructions, at startup, the pixel c remains on the blue wave screen but the configuration does not start...

Any idea?
[Pixel C Android Development] followmsi:
Pls do factory reset first .. will update the OP soon.
[Pixel C Android Development] Vartom:
Graphical tests and benchmarks crash with errors. It looks like a problem with Vulcan.
[Pixel C Android Development] followmsi:
September 2018

No need for Oreo anymore :)

Camera works now .. except for MTP it runs very well.

There are still some minor issues which will be fixed in the next time.

AOSP_9.0.0_r8_PPR2.180905.006.A1_dragon-ota-eng.followmsi.zip

Changes

- Camera works for AOSP now !

- Google September 2018 security updates

- New kernel including the latest Google patches

- The ROM does contain it's own vendor.img ! (If you go back to Oreo, pls reinstall stock vendor.img)

Opengapps:

Pls use opengapps from here .. https://xdaforums.com/android/development/gapps-unofficial-opengapps-builds-t3828141

Or any other package for Android 9.0 (ARM64).

Enjoy ..:p
[Pixel C Android Development] Vartom:
Graphical information (AIDA64) and benchmarks (3Dmark) crash with errors. It looks like a problem with Vulcan.

Camera :good:
[Pixel C Android Development] NYCHitman1:
Where are the logs?
[Pixel C Android Development] Vartom:
https://drive.google.com/file/d/1UnNRRh97mzRD3tDCfOo-OmdnhjmOhcPD/view?usp=sharing
[Pixel C Android Development] Burakki:
my pixel doesn't boot. I follow the guide in the op... what is your method to start with the android 9 rom?
[Pixel C Android Development] NYCHitman1:
If it doesn't boot -- you're doing something wrong on your end. The only thing you need to do is clean flash.
[Pixel C Android Development] Vartom:
Will Full Treble support be implemented?
[Pixel C Android Development] NYCHitman1:
I have no plans of doing so. Can't get vndk 28 compliant because there's no P blobs, so the odds are this is as good as it's going to get.
[Pixel C Android Development] iestyn99:
Clean install 9.0. Gets stuck in the opening wizard on "checking for updates", total freeze, can't skip that thing. Tried different 9.0 gapps, tried wiping everything and factory reset in twrp (3.2.3). Any ideas?

Edit: solved it for now by first installing ROM, then let it boot without gapps, then installing gapps.
[Pixel C Android Development] NYCHitman1:
Use these: https://www.androidfilehost.com/?fid=1322778262903998678
[Pixel C Android Development] Vartom:
Can try these recommendations, maybe they will help. Or it does not make sense?

https://source.android.com/devices/architecture/vndk/#vndk-versioning
[Pixel C Android Development] NYCHitman1:
I think you misunderstand. In order to be vndk compliant with the current level -- your proprietary blobs have to match the API level. Sure, we could do vndk 27, but that's useless to us.
[Pixel C Android Development] Burakki:
even without gapps the system remains blocked. I'm not the problem.

I tried everything, all the wipe, several times. Always the same, with lineageos 16 or aosp, it remains blocked
[Pixel C Android Development] zetsumeikuro:
Thanks for keeping our Pixel C's alive and updated!
[Pixel C Android Development] Vartom:
Maybe it's easier to do this on the Qualcomm, but I know that they do not officially support Treble on devices that have officially only Android 8.0. For example Oneplus 3. https://github.com/OP3Treble/android_device_oneplus_oneplus3

Can you make libhealthd.dragon and power.dragon in the binderized version HAL?
[Pixel C Android Development] iestyn99:
Same problem with these gapps.
[Pixel C Android Development] followmsi:
Blocked ?

Are you encrypted ?

Pls format /data inside TWRP and start again.
[Pixel C Android Development] Burakki:
is normal that, reboot into recovery, the twrp ask me to insert the default_password of recovery?

(twrp 3.2.3-0)
[Pixel C Android Development] NYCHitman1:
There's no value in going full treble. The work doesn't justify the amount of time needed to accomplish the task.
[Pixel C Android Development] followmsi:
Yes, If encryption is not working correctly .. as mentioned above "format" data in TWRP and start from scratch.
[Pixel C Android Development] NYCHitman1:
I built them and used them without issue.
[Pixel C Android Development] Vartom:
Can not be assembled with a working camera. Shim does not work. How did you get the camera to work ?

ps I got an MTP connection. But I still have not figured out for what change this happened.

pps I think I found a solution. This is it?

https://github.com/Pie-onyx/bionic/commit/d324a447a3381649480102edf363ba94b4447433
[Pixel C Android Development] followmsi:
Yes .. you need to change bionic .. to get shim libs working.

https://github.com/followmsi/manifests/tree/dragon-aosp-pie
[Pixel C Android Development] iestyn99:
Yeah, it's not the Gapps, they are probably fine. This very thing happens with any Gapps and I have tried three different ones. Must be something in the ROM?
[Pixel C Android Development] Vartom:
[MENTION=2489052]NYCHitman1[/MENTION] [MENTION=5480152]followmsi[/MENTION]

Any idea why Vulcan causes a fall in applications?
[Pixel C Android Development] NYCHitman1:
We may be using outdated permissions for vulkan (maybe?)
[Pixel C Android Development] Vartom:
Perhaps this is a problem with accessing devices from a certain type of application.

[ 108.359194] type=1400 audit(1536193113.321:12): avc: denied { read } for pid=3636 comm="inalwire.aida64" name="devices" dev="sysfs" ino=8314 scontext=u:r:untrusted_app:s0:c135,c256,c512,c768 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=0
[Pixel C Android Development] followmsi:
Once booted and you change "setenforce 0" .. does it work now ?
[Pixel C Android Development] NYCHitman1:
09-10 21:59:07.111 I/inalwire.aida64(10308): type=1400 audit(0.0:566): avc: denied { read } for name="temp" dev="sysfs" ino=9235 scontext=u:r:untrusted_app:s0:c135,c256,c512,c768 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
09-10 21:59:07.111 I/inalwire.aida64(10308): type=1400 audit(0.0:567): avc: denied { open } for path="/sys/devices/virtual/thermal/thermal_zone0/temp" dev="sysfs" ino=9235 scontext=u:r:untrusted_app:s0:c135,c256,c512,c768 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
09-10 21:59:07.111 I/inalwire.aida64(10308): type=1400 audit(0.0:568): avc: denied { getattr } for path="/sys/devices/virtual/thermal/thermal_zone0/temp" dev="sysfs" ino=9235 scontext=u:r:untrusted_app:s0:c135,c256,c512,c768 tcontext=u:object_r:sysfs:s0 tclass=file permissive=1
09-10 21:59:07.138 I/inalwire.aida64(10308): type=1400 audit(0.0:569): avc: denied { read } for name="devices" dev="sysfs" ino=8314 scontext=u:r:untrusted_app:s0:c135,c256,c512,c768 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=1
09-10 21:59:07.138 I/inalwire.aida64(10308): type=1400 audit(0.0:570): avc: denied { open } for path="/sys/bus/usb/devices" dev="sysfs" ino=8314 scontext=u:r:untrusted_app:s0:c135,c256,c512,c768 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=1

All of these policies violate Google's neverallow rules in sepolicy. They cannot be patched.
[Pixel C Android Development] Vartom:
But earlier applications received information about available devices (hardware) and information from sensors. Why did 9 become so demanding?

And if you take as an example temperature data, then another application can get this data.
[Pixel C Android Development] NYCHitman1:
You'll have to ask Google that. A workaround would be to remove the never allow from system/sepolicy then add the policy to the device tree to permit the event access to whatever path it needs. However, I'm assuming Google did this for security purposes.
[Pixel C Android Development] Vartom:
So you want to say now that on all devices with Pie you can not get information about the availability of Vulcan technology and an elementary list of devices? I do not believe in this.

Ps I would rather believe that the driver of the vulcan of the old version causes a crash in the new android. But it does not fit with the fact that the main video driver works fine.
[Pixel C Android Development] NYCHitman1:
I never said that. The issue you're describing doesn't really even relate to Vulkan in the way that you are thinking. I readjusted the Vulkan permissions to the new schema Google is using. Perhaps you should look at that: https://github.com/DirtyUnicorns/an...mmit/68155d3940c445a9c6a9fe9fea106828c281cb52
[Pixel C Android Development] Vartom:
Did you check this works, does the 3dmark start?
[Pixel C Android Development] NYCHitman1:
No, I don't care for benchmarks. Simply suggested it to you because you seem to.
[Pixel C Android Development] Vartom:
Very bad. A benchmark is just an opportunity to check that everything works as it should be. And not just numbers.
[Pixel C Android Development] NYCHitman1:
Nothing personal, but you are more than capable of digging into this supposed Vulkan issue. I've seen your work on Flounder. You've done some very interesting stuff. What I've suggested to you is a starting point.

At this juncture, my Dragon does everything I need it to do with very minimal issues (which I've been fixing as they come up) -- so pardon me if I am not interested in spending the little free time I have on something that truthfully isn't important to me.
[Pixel C Android Development] Vartom:
[MENTION=2489052]NYCHitman1[/MENTION] Okay, no problem. I just thought you were interested in the full operation of the device without any errors.

I was able to run the android.hardware.graphics.composer in hwbinder mode.

The main reason again was still in the selinux.
[Pixel C Android Development] mediawiz:
I had some noteworthy issues with the AOSP 9.0 build. These included:

- After installing this ROM, I could no longer install an Android 8.x ROM (my Pixel C would no longer boot any ROMs that I tried).

- This ROM doesn't seem to support any routers that don't broadcast SSID.

- After install, the ROM never seems to totally complete Android setup. It keeps displaying a notification.
[Pixel C Android Development] NYCHitman1:
You need to reflash the last Oreo vendor.img if you're going back to an Oreo ROM.
[Pixel C Android Development] mediawiz:
How does one do that?
[Pixel C Android Development] NYCHitman1:
Get a copy of the August/September image and flash it in recovery.
[Pixel C Android Development] followmsi:
https://xdaforums.com/showpost.php?p=77598530&postcount=715
[Pixel C Android Development] 12paq:
Loving some Pie on my Pixel C!

Good enough for a dd for me.

Thanks guys!
[Pixel C Android Development] Vartom:
The vulkan API does not work in 9(Pie). After removing the permissions files and the vulkan.tegra.so file, all applications(3Dmark, GFXBench, AIDA64(tabs Android, Devices, Temperature) started.

With the games using Vulkan API I think it will be the same.

Based on this, I draw a conclusion Vulkan API will not work without patches. Perhaps some intervention in the source code of the android will help to launch it.

We are incredibly lucky! Vulkan libraries from Shield-TV allow to launch the Vulkan API.
[Pixel C Android Development] followmsi:
Tested 3Dmark now .. did not start at all.

I kept all the permissions and vulkan.tegra.so .. but did change libvulkan.so in system.

Took libvulkan.so from latest google stock ROM and replaced them in lib and lib64 - now 3dmarks works !

I guess, we do not need the shield libs ..

Will add them to GitHub soon form the next build.

Tested on lineage.. should be the same on AOSP.
[Pixel C Android Development] Vartom:
You went the other way, having lowered the version of the API in the system to 1.0.x by replacing the library libvulkan.so.

I took compatible with the new api libs from Shield. https://gitlab.incom.co/CM-Shield/p...ineage-15.1/shield/hal/lib/hw/vulkan.tegra.so

and i use frameworks/native/data/etc/android.hardware.vulkan.version-1_0_3.xml
[Pixel C Android Development] followmsi:
Maybe switching back to 1.0.3 .. not sure if the version matters.

Most important is to use prebuilt libvulkan.so in system !

Just finished 3dmark sling shot unlimited with 3620 points. (5595 graphics and 1619 for physical)

Normal values ?
[Pixel C Android Development] Vartom:
Tested 3dmark sling shot unlimited with 3872 points. (5032 graphics and 2143 for physical). This test does not use the Vulkan.

For the Vulkan there is another test of the API Overhead. 15976(ES3.0)/38250(Vulkan)

Both methods are good, the main result.
[Pixel C Android Development] followmsi:
It seems not .. for me the API overhead test did crash first time .. second time only low values. (Vulkan 18789/ 9532 ES 3.0).

Will change back to 1.0.3 native.. and test again.

Maybe using shield vendor libs is the way to go.

Cheers

EDIT:

Tested with 1.0.3 .. first test did work directly and got 36778 ES 3.0 and 19297 Vulkan.

Will keep it this way .. only prebuilt dragon libs.

Maybe later on we can switch to other tetra.vulkan.so vendor libs.

Thanks

https://github.com/followmsi/androi...mmit/89d1f5db900f381a3bd87430714537ca7c808e57

https://github.com/followmsi/android_vendor/commit/493c8a7e4af58692e2d36429dfe7d4b331e72f98

One last edit ..

Tested on fresh lineage build again .. got 4456 with sling shot .. much more as before.

But much less with api overhead test .. especially ES 3.0 values - the vulkan values were quite stable.

Made a few more repeating overhead tests .. always quite different ES 3.0 values while getting stable vulkan values.
[Pixel C Android Development] Vartom:
I get different results every time in the overhead test. The picture is jerking. In the error logs.

syslog

09-16 22:46:41.078 242 320 W hwc-drm-display-compositor: Acquire fence 97 wait 1 failed (-1). Total time 300

09-16 22:46:41.458 242 320 W hwc-drm-display-compositor: Acquire fence 51 wait 0 failed (-1). Total time 100

09-16 22:46:41.658 242 320 W hwc-drm-display-compositor: Acquire fence 51 wait 1 failed (-1). Total time 300

dmesg

[ 250.850233] nouveau E[ PGRAPH][57000000.gpu] DATA_ERROR [INVALID_VALUE] ch 19 [0x04016a2000 cation:workload[3445]] subc 0 class 0xb197 mthd 0x07c4 data 0x000002d0

[ 250.850282] nouveau E[cation:workload[3445]] error notifier set to 13 for ch 19

[ 250.850601] nouveau E[ PGRAPH][57000000.gpu] DATA_ERROR [INVALID_VALUE] ch 19 [0x04016a2000 cation:workload[3445]] subc 0 class 0xb197 mthd 0x07c4 data 0x000002d0

[ 250.850648] nouveau E[cation:workload[3445]] error notifier set to 13 for ch 19

While it is not clear from what it is.
[Pixel C Android Development] Bloch_hd2:
hi

Thanks for the great work, i love that the pixel c still get some love !

I followed the instructions on installing pie, and get stuck on the setup wizard:

I connected to wifi > devices hangs on checking for updates > system ui eventually crashes > "Couldn't sign in. You dont have a network connection" even tho i connected to my home wifi, that works fine.

I followed the install steps. tho the open gapps are official now. i got the stock arm64 package. also i installed super su instead of magisk, but i dont think that would make a difference :)

so what do i do from here? is this a gapps issue?

---------- Post added at 08:08 PM ---------- Previous post was at 07:31 PM ----------

After lots of trying different stuff i bypassed the setup wizard by doing a factory reset and skipping the wifi connect page.

now i just got a "preparing for setup..." notification that never seems to go away, even after a reboot.
[Pixel C Android Development] followmsi:
Mount /system in twrp (read/write) and remove /system/app/setupwizard folder completely.

Sorry .. no idea about fully working stable opengapps (setupwizard) for pie.
[Pixel C Android Development] Vartom:
There are problems from the side of drm_hwcomposer. for verification, I replaced it with the old version of 8.1. As a result, the tests in 3Dmark pass through the results much higher and the image went smoothly without jerks, but there are problems with the startup since the old version is poorly compatible with libsurfaceflinger in the system. I think that the problems are due to the addition of HWC2 API.

In Antutu i got 219914, gpu 129314 8.1 drm_hwcomposer/(~104000 w 9.0 drm_hwcomposer).
[Pixel C Android Development] followmsi:
System is not booting with replaced drm_hwcomposer ?

HWC2 has been activated in Oreo too.
[Pixel C Android Development] NYCHitman1:
I'll look into this. No ETA though.
[Pixel C Android Development] Vartom:
The difference is that they are in this patch, which is not used for 9.0.

https://android.googlesource.com/pl...er/+/9cc83934f92aab292f16213c1b716e8ecfcb5875

Ps. In general, I canceled it in the source and rebuilt the firmware. Now everything works. Tests go smoothly. There are no errors in the HWC.

I will look at other tests as it works.
[Pixel C Android Development] followmsi:
Are you able to use the patch in 9.0 sources and build new drm_hwcomposer ?

Does it fix the problem ?
[Pixel C Android Development] Vartom:
It seems yes, I'm testing.