Develop Bugs

Your feedback about Oreo ROM

Hello ,
Actually my Mi5S is working great on MIUI 9.5 global stable ROM. Nevertheless, I don't really like MIUI design and I'd like to change to a Oreo (Stock) ROM like Lineage OS 15.1 or AOSP extended but I need some feedback about them (like Battery, bugs, Performance, Stability etc...) because feedback on topics aren't really complete. You also could share other Oreo ROM which are stable enough. Don't forget to specify which version of the ROM you have.
Thanks a lot and I hope this thread will help others!

Install RessurectionRemix ROM (or PixelExperience - slightly faster IMO) and you don't have to wory about nothing

AEX seems to work best with my phone. Faster than LOS and PixelExp, superior and consistent battery life (6h of SOT with ForceDoze installed) and no noteworthy bugs. Considering stablity and extra functions there are very few bad choices as most ROMs for this device are pretty good. Just be sure to install the right hardware-firmware and follow installation instructions carefully.
If you're moving from MIUI the battery is the thing that will probably will get worse results. Performance and features are better with the custom ROMs. Also installing a modded GCam (ported Pixel image processing for really good quality) is a must.

[sorry X2 post, didn't find how to delete it]

Okey guys thanks for your reply. Are you using a custom kernel ?
 @Djeloan Pixel Experience seems to not be updated anymore... No more support ?
 @8166uy I reckon I will install AEX if it's enough stable for daily use. By the way, you recommend to install a modded Cam. Is it because pre-installed cam on Custom ROM doesn't work as well as stock Cam on MIUI ?

I'm not a big fan of custom kernels as you don't profit THAT much with it, but does give extra problems every few weeks. And yes the modded camera is partly because the stock camera from the ROMs aren't all that good, but also because with it you can make it as good as modern flagships from the big western brands. So expect better sharpness, better dynamic range, better low-light performance and a properly working portrait background blurring effect.
For the best results take the GCam from B-S-G or Arnova for pictures (there are threads plenty about them here) and OpenCamera for videos (can be found here: https://play.google.com/store/apps/details?id=net.sourceforge.opencamera).
Download link for all versions of the modded GCam are btw here if you feel adventurous. Some are more stable than others:
https://www.celsoazevedo.com/files/android/google-camera/
I use this one because of stability and device specific tweaks:
https://www.celsoazevedo.com/files/...018.177470874.41362666__A7.0-8.1_MI5S_v2e.apk

Great ? thanks for sharing that ^^

I've heard that Arnova's GCam works significantly better on Oreo than BSG's.

For me the Arnova ones just keeps crashing with low light no matter which version I pick, so I would just try both and see which one fits best. I personally never had any problems with B-S-G builds on Oreo.

i avoid messing with kernal's unless its a hobby you enjoy. it can get time consuming later on

8166uy said:
For me the Arnova ones just keeps crashing with low light no matter which version I pick, so I would just try both and see which one fits best. I personally never had any problems with B-S-G builds on Oreo.
Click to expand...
Click to collapse
use toylan's

Is OxygenOS camera take better photos than Google Camera ?

As title. I really want to know the differences between 2 camera apps on OnePlus 5T hardware, as I want to try custom ROM but afraid of missing the ability to take portrait mode photos.

I've tried a couple of custom ROM's. But as of now nothing beats OOS Camera features. Interestingly, someone started this thread just today. Thinking of trying out these custom ROM's
https://forum.xda-developers.com/oneplus-5t/help/custom-rom-oos-camera-included-default-t3851694

I totally agree with "poythegraeat" but at the moment I cannot find a good AOSP custom rom with OOS cam included and I'll never use a decripted smartphone or a closed source rom. I'll stay with LOS for microg + gcam under privacyguard and firewall. I also tried the OOS porting for lineage but videos are not working in 1080p, 18:9 cause app crashing.. now it's still really buggy.
Differences gcam vs OOS cam: at the daylight, in optimal condition, they are very similar (You must use "5t library fix" and "Pixel 2 colour" magisk module, and you must use hdr+ too, otherwise you will get glitchy photo). In very low light gcam is totally unusable. In normal low light is barely acceptable (OOS is totally better in low light).. Video stability,portrait mode and slow motion is lost with gcam. If your concern is privacy and you want a custom rom, I think that gcam is a good option. If you only need customization: my advice is strongly to use oxygenos and root it.

@rmroot
What you think OOS is closed source?
https://github.com/OnePlusOSS

OOS has mixed licence (and so closed source too), it's not fully open source. OOS has closed source apks and parts of the sistem that log the user like a malware could do, if you are interested in this particular topic I suggest you to search on the subreddit "privacytoolsIO". You will find a recent post about OxygenOS privacy and some analyzes posted on twitter by a security researcher.

@rmroot I'm a Geek and Professional already on these topics...
I've been doing this a very long time, personally and professionally, sorry if I confused you. I keep making assumptions with comments like that because we are on a Android Developers forum...
Anyhow I should of thought before I posted that...
I meant it's Open in the Context outside of Google and what manufacturers have in the way of their hardware firmware blobs.
So outside of Google and hardware firmware blobs, that's the Open I meant, and why there's a Repo...
Cheers

Camera apk for OnePlus 3T

I am running a custom OS, which varies from Statix, Nitrogen to Holydragon or MSM. At this moment Statix though; simple, fast and stable.
I have read some topics about camera apps for the OnePlus 3T.
Although Google Camera app in modified version is very populair, I have issues running it.
Probably because I am not using any Google related stuff (Google Play Services, Google Photo's etc...), so I keep coming back at Open Camera, or OnePlus Camera app.
At this moment I am using oneplus-camera-2-5-34, but I was wondering if some people have experience with latest Oneplus camera apps (V3.0.xx) on OnePlus 3T, or could advise other options with great results.
2.5.34 is stable and working fine, but ofcourse is missing options of newer (OP5 and OP6) versions.
Home someone is willing to share his experiences and give some advice!

Jan_L said:
I am running a custom OS, which varies from Statix, Nitrogen to Holydragon or MSM. At this moment Statix though; simple, fast and stable.
I have read some topics about camera apps for the OnePlus 3T.
Although Google Camera app in modified version is very populair, I have issues running it.
Probably because I am not using any Google related stuff (Google Play Services, Google Photo's etc...), so I keep coming back at Open Camera, or OnePlus Camera app.
At this moment I am using oneplus-camera-2-5-34, but I was wondering if some people have experience with latest Oneplus camera apps (V3.0.xx) on OnePlus 3T, or could advise other options with great results.
2.5.34 is stable and working fine, but ofcourse is missing options of newer (OP5 and OP6) versions.
Home someone is willing to share his experiences and give some advice!
Click to expand...
Click to collapse
For me 2.8.32 is the latest stable release after trying 3.x versions.

garzacorporations said:
For me 2.8.32 is the latest stable release after trying 3.x versions.
Click to expand...
Click to collapse
2.8.32 running fine indeed, thanks.
Other tips also welcome of course

Why are you running a custom rom?

I wanted to GTFO Google and (ONE) single ROM has been developed for this phone on XDA without Gapps and it's not even maintained any more. I tried out Lineage with Micro G and I was pretty happy. I asked if anyone here would be interested in GrapheneOS and got no reply. I built it for myself and was happier with the spoofing in Lineage so I went back. But that brings me to the OP question...​​I guess I just don't understand why anyone would build a custom ROM that allows Google to spy on you completely unchecked. I thought I must have been insane since literally nobody here seemed to agree. Then I found this write up......I immediately decided to post it. Not because I want to piss people off. Not because I'm unappreciative. But because WTF ARE WE DOING??​​Why are we even running custom ROMS? Xposed came out and Google screwed us with SafetyNet. Then you had Substratum that got checked from Google but it's being "allowed" right now even though they tried to patch it out. Then Magisk comes and Google buys him out. This has always been a "cat vs mouse" game until recently. Now it's just a "cat vs customizable cat" game. Did we lose? Or is it that people would rather trade their privacy for convenience? The direction we are headed as a community is allowing Google to slowly close off and become Apple pt2 and nobody seems to mind much. But this is XDA! How will it exist without people caring about this?​​Here is part of the write up that applies specifically to the OnePlus7T. Hopefully I'm not alone. Hopefully we can get this train back off the tracks where it belongs. Barreling through the unknown in defiance of these huge entities trying to control you. Link is at the bottom of the write up.​​crDroid​LineageOS-based custom ROM designed to increase performance and reliability over stock Android for your device while also attempting to bring many of the best features existing today, according to their intro & how I think its grammar should be.
Personal remarks: A very good heavyweight ROM (and the best Limbo ROM at the moment), burdened with a soydev website (at least there's no BlockAdBlock unlike Arrow) & lack of Vanilla/GApps enforcement in a way similar to Bootleggers - no Vanilla/GApps branding
Advantages:
Per-app data restriction (Pie, A10, A11)
Signature spoofing (A10 & A11: no toggle)
Inbuilt App Lock
Disadvantages:
No signature spoofing (Pie-only; forgiven & redacted starting with A10, 12/4/2020 build)
If you look at the official site, there's a screenshot that shows this feature, on a toggle. Should have been available at Settings > crDroid Settings > Miscellaneous; but it's not there.
Tested the 12/4/2020 build & found out that microG support is enabled without toggle. This anti-feature is redacted.
Poco X3(N) only (confirmed on 23/3/2021 build) - USB debugging enables itself on boot (redacted per 22/4/2021 7.5 build)
28/4/2021 Update : With inbuilt vendor on 22/4/2021 7.5 X3N build, USB debugging no longer self-enables on boot (it's enabled at 1st boot, but can be disabled without enabling itself on subsequent boots). Welp, guess it's like the F1's Pie era all over again, where most builds (especially userdebug ones) enable USB debugging on boot until developers starts to include vendor partition in their builds.
Poco F1 (A11) : No force encryption
No Vanilla/GApps enforcement, in addition to lack of Vanilla/GApps labeling
List of GApps-infested builds :
OnePlus 7T & 7T "Pro"
Not having an active TWRP development for a device does not excuse the maintainers for releasing GApps-only releases, unless they also make a Vanilla variant. And, since there is an active TWRP development, there shouldn't be any more reason to tolerate a lack of Vanilla build (other than the maintainer being too lazy / unwilling to develop a Vanilla build, in which case per should be replaced).
Poco F3 (switched to Vanilla builds as of 9/7/2021 builds, but still listed for reference)
Redmi K20 / Mi 9T (davinci) (Vanilla build available on GDrive, FWIW.)
OnePlus 9 "Pro"
When its non-"Pro" (the vanilla OnePlus 9) variant gets a Vanilla build (despite a lack of functional TWRP for either) there is no excuse to be lazy & provide GApps-only builds
Custom ROM List

Definitely. Yaap microG by John Galt is very good also. Omni microG is also good

I read through your entire post and while most of the things you have said could be attributed to a subjective basis depending on person to person basis but the overall idea has a couple of inconveniences that I would like to add some insight of my own and would like to explain without sounding too brash
This is just my own personal impression that I have witnessed being part of the greater Android ecosystem in general starting from the early days to where we are now
In my opinion, the lack of interest by developers that originally gave their time and effort into working hard and fixing things has generally not kept up with the pace of Google's development efforts to curb these "hacks". The cat and mouse game what the post you quoted said is nearly at an end. I think Google is winning with everything in broader terms and despite the conveniences offered by microG and custom roms using that implementation, it doesn't come close to what Google offers.
The hassle of finding workarounds to make even the basic of functionality to work on Android requires time and effort which as I have already said earlier, it's something no one can commit to these days. The "enthusiast" aspect of custom rom development has really taken a dive over the past few years as manufacturers generally offer good enough functionality (at least for my use case as I am heavily reliant on my phone for work and general personal use) and Android has come a long way since the early days.
All of what I said boils down to the cost of convenience vs concern for issues that are really issues for a specialist segment of users within the entire community. People de-google their phones to focus on privacy and prevent data mining from these data hungry corporations and I for one for wish I could have something that would decrease my overreliance on Google's services but it is just not possible as the majority of people just use their phones and expect things to work just like that. So, the long lived idea of if it ain't broke, don't fix it plays very well into this. The trouble is generally not worth the inconveniences that come with it. Lack of interest of users therefore means lack of options and thus a lack of development.
Here's my 2 cents

I think for devs or hobby-coders who do this for free, time is more valuable than the luxury of "privacy" (which doesn't really exist if you're using any form of social media, like XDA).
Things changed. Android is more polished now than the Nexus days.

General Current state of AOSP - Lineage/Pixel Exp/Etc...

Wanted to write a thread to give feedback on where AOSP devs are currently at with AOSP ROMs for those who are interested. Don't want you to think that there is no development in this area.
While there are GSI out there, I think ROMs built from source are the better option.
While GSIs are meant to be that, generic, I don't think this is a proper replacement for ROMs since there are many brands it tries to encompass and not to mention, the GSIs devs may not be able to fix bugs for your particular device or brand, it's just the nature of GSI.
Anyway, we currently have a secret testing group where almost daily builds are pushed, trying to polish the builds and fix some of the bugs that are still present. It's getting closer and closer to being bugless.
Here's the current state of AOSP ROMs for A52s:
Working:
- Bluetooth
- BT Audio
- NFC
- Casting
- Vibration
- Brightness and autobrightness
- Display at 60/120hz
- Audio/Mic
- Wifi/Tethering
- All Cameras (rear camera @ 4k 30fps)
- Face unlock
- Factory reset
- Pixel Features (unlim. google photos, game booster...)
- AOD & At a glance widget
Not working:
- RIL
- Fingerprint (only unlocking is broken)
Sensors:
Accelerometer: working
Geom. Field: working
Gyro: working
Light: working
Proximity: working
Gravity: working
GPS: working
The following devs have done an amazing job for AOSP development on this device, I know with their combined contribution, we'll soon start getting stable trees which will lead to better and more stable ROMs:
@Alone0316
@PauloWesley
@BlackMesa123
@Simon1511
@Ryzen5950XT
And of course special thanks to all the testers which have to reset their devices almost daily to get these tests done. You guys are a part of this too. I'll continue to update this thread when anything major breakthrough happens and/or it's stable for release. Most of this doesn't get reported on outside the testing group so I wanted to give this feedback so that users don't lose total hope on this device for people who love AOSP.

LOVE IT

Hats off to all the people trying hard to put a52s in development radar

!!!!!!!

Nice team work
Waiting for official lineage

AOSP? Love it.. very appreciate for those who will make it happens.. salute

thank you for the update, can't wait

Keep up the good work you guys

Is there a possibility to put Samsung apps (Like Samsung Store) in the AOSP version?

heal3r said:
Is there a possibility to put Samsung apps (Like Samsung Store) in the AOSP version?
Click to expand...
Click to collapse
Only AOSP-compatible apps can run on non-Samsung ROM's, such as Galaxy Watch, Samsung Health, Samsung Internet etc.

BlackMesa123 said:
Only AOSP-compatible apps can run on non-Samsung ROM's, such as Galaxy Watch, Samsung Health, Samsung Internet etc.
Click to expand...
Click to collapse
Oh that's sad. I love aosp but I can't give up Samsung Store for now. Guess I'll stick to samsung roms for now.

excellent news. i was always wondering why a hugely popular devices as A52s did not get proper custom ROMs yet, good to hear there is progress being made.

Will the official pixel experience repository be uploaded?

ShaDisNX255 said:
Wanted to write a thread to give feedback on where AOSP devs are currently at with AOSP ROMs for those who are interested. Don't want you to think that there is no development in this area.
While there are GSI out there, I think ROMs built from source are the better option.
While GSIs are meant to be that, generic, I don't think this is a proper replacement for ROMs since there are many brands it tries to encompass and not to mention, the GSIs devs may not be able to fix bugs for your particular device or brand, it's just the nature of GSI.
Anyway, we currently have a secret testing group where almost daily builds are pushed, trying to polish the builds and fix some of the bugs that are still present. It's getting closer and closer to being bugless.
Here's the current state of AOSP ROMs for A52s:
Working:
- Bluetooth
- BT Audio
- NFC
- Casting
- Vibration
- Brightness and autobrightness
- Display at 60/120hz
- Audio/Mic
- Wifi/Tethering
- All Cameras (rear camera @ 4k 30fps)
- Face unlock
- Factory reset
- Pixel Features (unlim. google photos, game booster...)
- AOD & At a glance widget
Not working:
- RIL
- Fingerprint (only unlocking is broken)
Sensors:
Accelerometer: working
Geom. Field: working
Gyro: working
Light: working
Proximity: working
Gravity: working
GPS: working
The following devs have done an amazing job for AOSP development on this device, I know with their combined contribution, we'll soon start getting stable trees which will lead to better and more stable ROMs:
@Alone0316
@PauloWesley
@BlackMesa123
@Simon1511
@Ryzen5950XT
And of course special thanks to all the testers which have to reset their devices almost daily to get these tests done. You guys are a part of this too. I'll continue to update this thread when anything major breakthrough happens and/or it's stable for release. Most of this doesn't get reported on outside the testing group so I wanted to give this feedback so that users don't lose total hope on this device for people who love AOSP.
Click to expand...
Click to collapse
Finally yessss

You are my only hope custom ROMs
I just bought this phone and it was a big mistake.
-It's full of bloatware
-There is 0 customization unless you register a samsung account
-The volume slider is only 15 steps instead of 30 so music is either too loud or too quiet for me
-I can't skip tracks by holding down the volume keys
-The notification at the top of the list doesn't get extended automatically
-When I view the opened apps it switches off the app I'm currently in. (SUPER ANNOYING)
Other than that there are actually a fiew things that are really cool:
-I can turn off the app drawer
-The camera app
-Full black background theme in samsung default apps (like calculator, messages, calendar, etc..)
-The calculator has some cool features
-No navigation bar at the bottom with gesture controls
-Keyboard can be positioned to the bottom of the screen without a gap.

FelixVyra said:
-I can't skip tracks by holding down the volume keys
Click to expand...
Click to collapse
You can download the Sound Assistant module from the Galaxy Store
FelixVyra said:
The notification at the top of the list doesn't get extended automatically
Click to expand...
Click to collapse
You can download Good Lock + QuickStar to have this activated
I think yeah you will need a Samsung account but I'm not sure

Oh! That would be awesome!
I switched from OP3 with HavocOS to A52s in May and... it's been "fine" but I do miss custom AOSP/Lineage features...

Any news about that?

No news, development has slowed down a bit

ShaDisNX255, thanks for the update. Please keep us updated. I keep checking daily for any news. If the development stops or slows down a lot to the point where it's months away before it's ready then I would go with your Android 13 ROM. I prefer bare bone simple ROMs but at the time I don't want to wait years either especially if your ROM is very good and ready to be installed. So if you come across any news please let us know. Thanks.