id love to see /e/ for the google pixel 4a
Until one day there is an official /e/ OS ROM, @harvey186’s ROM can already use eOS-Q-GSI (arm64 a/b) with pixel 4a.
Wait you are saying this ROM is compatible with the 4a?
Hi, Out of curiosity I want to know that Pixel 4a is old release. And I know that Google supports for generally 3 years. Once new model is launched they give up support of old one.
So even if /e/ takes Pixel 4a, how long /e/ will support it without base support of Google??
Thanks
The hardware is perfect for a compact phone.
How come no other current Pixel phone, like 3a or 4, is supported by /e/?
Is there a problem with the bootloader?
Regain your privacy! Adopt /e/ the unGoogled mobile OS and online services
Hi,
I want to know that Pixel 4a is old release. And I know that Google supports for generally 3 years. Once new model is launched they give up support of old one.
So even if /e/ takes Pixel 4a, how long /e/ will support it without base support of Google??
Thanks
Hello !
Is there someone have a bug on their photo’s application since e/os installed?
In my case, when i opened the photo, its take 5-10 sec before open and often there is a crash message which appears
Have’nt experienced a camera bug as described on 2.7-u-20250109460549-community-sunfish
…
edit: see my post below…
You may check out the 4a-specific feedback for the eOS-version you’re on in the eOS-version specific section of the forum because others may have dealt with this issue (?)
Have you tried deleting the cache and/or data of the camera-app already?
I deleted the cache and the data, it looks like its worked !
Thanks ! I keep the link to 4a-specific feedback in case of a new bug
I had the same problem with 2.7 U.
Also after updating to 2.8-u.
Now I cleared cache and data as it worked for you. But on my phone the problem remains.
After doublechecking I must admit the bug is present on my phone as well…
(phone is on 2.8-u now)
Sorry for being misleading initially… I just realized that I am mostly using app.grapheneos.camera.play
per default instead of onboard camera…
(I’ll edit my post above)
Anyway good that clearing data+cache helped at least one person
edit because see post below…
Hmmm i was wrong… I clearad cache and data but the bug remains even