I added this permission, but unfortunately the situation has not changed... Тhanks for the answer...I'm not an expert here but it seems you need to give your application the permissions to change system settings.
I added this permission, but unfortunately the situation has not changed... Тhanks for the answer...I'm not an expert here but it seems you need to give your application the permissions to change system settings.
picture quality is badthe date version 2022-10-08 extremely good. More battery saving, more stability. I believe it is close to the final version.
the resolution of the camera is very low on the original software resolucion is 9000 of 7000Test gcam:
![]()
MGC_8.5.300_A10_V9_ruler.apk
Option 2: https://apkadmin.com/aigubj5alx75/GCam8.2.204_Greatness.220901.2139Release_Biometrics.apk.html
View attachment 5732159
data roaming didn't work on mineHi, 4 questions:
1) Is data roaming working and has anyone tested it?
2) Has anybody tested AFWall?
3) Anyone using MicroG successfully?
4) Any plans to have the Tele camera accessible in Gcam for the A52?
Thanks!
I can happily report that data roaming DOES work on mine. A525M/DS
For A52, I find the LMC one a bit better, with BSG Morgenmann XML file. They're in a pinned post on the telegram group. It has more settings and Auto-White Balance works better than on the BSG Gcam. However I agree that not being able to capture 64MP shots is disappointing. However I did try the stock camera before flashing Lineage and the larger resolution picture helps but the quality of the 64MP pictures is not overwhelmingly better than what Gcam produces (16MP) or the non-64MP mode on the stock camera (also 16MP I think).
I think the latest builds are just auto-generated by Lineage right? I thought I would be able to get those changes through OTA but I see no updates are available unfortunately. Not sure when something will be available via OTA updates.the date version 2022-10-08 extremely good. More battery saving, more stability. I believe it is close to the final version.
Are you on an official lineage build already? (anything newer than 20221003)I think the latest builds are just auto-generated by Lineage right? I thought I would be able to get those changes through OTA but I see no updates are available unfortunately. Not sure when something will be available via OTA updates.
Pudiste solucionarlo?Así que obtuve mi A52 y comencé a instalar la ROM hoy. ¡Gracias por su apoyo hasta ahora!
En TWRP, después de flashear multidisabler, flasheé Lineage (originalmente probé la compilación microg, luego probé la última noche), sin embargo, el sistema no arranca. Vuelve a la recuperación si intento iniciar el sistema. Usé el TWRP vinculado en tu publicación original @Simon1511 .
Intentar borrar Dalvik/ART Cache o Data en TWRP muestra los siguientes errores:
[CÓDIGO] No se puede montar /data/media/TWRP/.twrps
No se puede montar /data/media/TWRP/.twrps
No se pudo montar '/data' (argumento no válido)
Error al borrar dalvik
Actualizando detalles de la partición...
...hecho
No se puede montar el almacenamiento[/CODE]
No tengo nada que deba guardar en el teléfono, ya que es nuevo.
¿Alguna idea sobre cómo continuar?
As @Simon1511 suggested: Please try to format data instead of wiping it, and then after that wipe metadata. That worked for me.
I am on this build, official, from Sep 15 https://download.lineage.microg.org/a52q/lineage-19.1-20220915-microG-a52q.zip . In the Updater app, when I allow it through AFWall, I get "No new updates found." I was hoping to get all the latest changes in Lineage since that September build, those found on this page https://download.lineageos.org/a52q/changes/ . Maybe the Lineage team only produces intermittent releases every so often?Are you on an official lineage build already? (anything newer than 20221003)
Because you will only get OTA updates if you are on an official lineage build, OTAs won't work on the old unofficial ones.
Ah, you're on MicroG, that explains it.I am on this build, official, from Sep 15 https://download.lineage.microg.org/a52q/lineage-19.1-20220915-microG-a52q.zip . In the Updater app, when I allow it through AFWall, I get "No new updates found." I was hoping to get all the latest changes in Lineage since that September build, those found on this page https://download.lineageos.org/a52q/changes/ . Maybe the Lineage team only produces intermittent releases every so often?
I've never had that on normal LineageOS, so I guess it's a MicroG-specific bug.Also, I noticed a bug tonight: the LTE signal strength indicator in the status bar is stuck at the value it had at boot time while travelling through places I know have very different signal strength. This happened again after I rebooted. I checked the signal strength with an app and obviously did not match what the indicator showed. Not sure if this is an issue with my setup, Lineage or the ROM but it would be nice to get this solved.
-Encryption/Decryption support for AOSP 12 and 13 ROMs
-Updated kernel to latest
-Fixed USB OTG and enabled NTFS support
-Switched to using FFS for MTP
-Added busybox bins
-Fixed ADB sideload
speaking of Android 13, do you plan on upgrading anytime soon?Ah, you're on MicroG, that explains it.
As far as I know LineageOS and Lineage for MicroG aren't made by the same developers, so it's not the same as normal Lineage.
Apart from that I guess they're waiting for LineageOS to move to Android 13 before continuing with new builds.
I've never had that on normal LineageOS, so I guess it's a MicroG-specific bug.
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
-Updated to Lineage 19.1
-May security patch
-Enabled freeform windows
-Build SamsungDAP for dolby audio
-Fixed color calibration in livedisplay settings (Please note that not all display modes support color calibration)
-Show download mode instead of bootloader in advanced restart menu
-Re-enabled FM-Radio
-Enabled night display/bluelight filter
-Fixed audio with USB headphones/speakers/etc
-Correctly detect phone variant and set props accordingly
-Enabled encryption (FBE)
-Removed unused partitions from fstab
-Fixed USB mode not being select-able
-Enabled MAC randomization for WiFi
-SeLinux enforcing
-Use correct default network mode (4G)
-Enabled adoptable storage to work with FBE
-Set props from stock ROM to make Netflix select DRM L1
-Fixed proximity sensor not working at all
-Updated kernel to A525FXXS4BVA2
-Enabled burn-in protection
-Updated to Lineage 19.0
-February security patch
-Updated all blobs and configs to A525FXXS4BVA2 (Android 12)
-Updated kernel to A525FXXU4BUL8 (Android 12)
-Unified more blobs
-Fixed screen rotation on A72
-Switched to AOSP WifiDisplay implementation
-Corrected status bar padding
-Built more blobs from source
-Switched to Clang r383902
-Disabled APEX compression
-Switched to UDFPS
-Fixed FOD on AOD
-Make FOD stay always on for working FOD on AOD
-Increased the amount of time the screen lights up when touching the fingerprint sensor
-Switched to stock health blobs
-Overall cleanup
-Enabled F2FS support for system partition
-Switched to newer AIDL libperfmgr power HAL
-Updated vibrator to AIDL to switch to manifest level 5 and match stock
-Fixed audio in bluetooth phone calls on A52 (for somehow still broken on A72)
-Imported APTX BT encoder from Pixel 5
-Enabled unofficial monet implementation
-Latest lineage sources with december security patch (january one wasn't released yet)
-Updated blobs to A525FXXU4AUJ2
-Added initial A72 support -- see more information below
-Switched to OSS fingerprint HAL by @Grarak
-Cleaned up unused config files
-Built lineage recovery for both devices
-Added missing overlay for the system to know that we have a notch
-Built more blobs from source
-Fixed A2DP offload and switched to AOSP bluetooth audio implementation
-Correctly boost brightness when the fingerprint sensor is touched
-Fixed fingerprint sensor not working when screen brightness is low
-Corrected size and position of the fingerprint sensor (And yes, the sensor is REALLY that big)
-Disabled screen off FOD for now since it doesn't work anyway
-Limit fingerprints to max 4 per user
-Temporary disabled FMRadio since it somehow broke with latest sources
-Built QCOM audio effects from source