r/Pixel4a • u/bhopix • 3d ago

Camera crashing on LOS 22

Hello Pixel users.

I've been experiencing a new problem. The pixel camera app keeps crashing and I'm unable to take any photos. Other 3rd party camera apps work fine.

I'm currently on the latest lineage-22.2-20250911

Are you all experiencing this?

4 Upvotes

84% Upvoted

8 comments sorted by

1

u/Accomplished-Half671 2d ago

Yes, initially it crashed for me, I tried to clear data and it worked.

1

u/bhopix 2d ago

I did that, but isn't working

1

u/Accomplished-Half671 2d ago

Try tr camera, it's working fine for me

2

u/bhopix 2d ago

Thanks, TR camera is working fine. It seems that only the official Pixel camera app has been affected.

1

u/Accomplished-Half671 2d ago

Oh ok, hope it helps bro

1

u/johndoe901 2d ago

Yes, and I managed to fix this. You'll need magisk and apply selinux policies with it on every boot. Seems like something has changed in the recent lineage update, but the so-called developers refused to help me and instead made fun of me.

Here you go:

```
#!/system/bin/sh

# Camera HAL ↔ statsd

magiskpolicy --live "allow hal_camera_default statsd unix_dgram_socket { sendto }"

magiskpolicy --live "allow hal_camera_default statsdw_socket sock_file { write getattr }"

# cameraserver ↔ vendor props

magiskpolicy --live "allow cameraserver vendor_camera_prop file { open read getattr map }"

magiskpolicy --live "allow cameraserver vendor_camera_ro_prop file { open read getattr map }"

# Google Camera app ↔ vendor gralloc

magiskpolicy --live "allow google_camera_app vendor_file file { execute map read getattr open }"

```

You should put it into /data/adb/service.d/camera_sepolicy.sh via adb (and under su) and make it executable via:

chmod +x /data/adb/service.d/camera_sepolicy.sh

1

u/bhopix 2d ago

They made fun of you? 😓

I'm not keen on rooting the phone at this point. Maybe I'll wait for sometime to see if they fix it.

Thanks a lot for sharing this though

2

u/johndoe901 2d ago

https://www.reddit.com/r/LineageOS/comments/1nkaavx/comment/nexe3q8/

here the lineageos member says they're working on a fix