Question rom & niggles - Redmi Note 9T

Hi.
Being on the latest version, is there a better (unofficial) ROM than the stock one?
Have constant problems re:
# camera hanging/stuck frequently
# usb connection drops after about 20s seconds
# miui slow with its moving squares in the middle of the otherwise blank screen too often
# xiaomi unreachable for feedback/advice/improvements
Any solution/tip appreciated!
Thx

Debloat it using universal android debloater tool from GitHub. It runs much better after that. In fact pretty fast. Ram is the main issue.

Related

[Q&A] [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)

[Q&A] [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
Q&A for [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Google Now
Is Google Now working? I tried to use it and didn't work. My GNex starts to go on a "loop" with the error in google search.
---------- Post added at 08:25 PM ---------- Previous post was at 08:19 PM ----------
Esteves85 said:
Is Google Now working? I tried to use it and didn't work. My GNex starts to go on a "loop" with the error in google search.
Click to expand...
Click to collapse
Now i'm having problem with the process "com.android.systemui" it´s always showing that was interrupted
Backlight occasionally off
Sometimes, when I wake the device, the backlight is off. Changing the brightness setting will get the backlight to turn on, but this is only really possible to do in a well lit area so I can see the screen without the backlight being on. If this a bug or am I being stupid with something.
Using standard kernel and haven't played with the brightness meter settings.
Came here from LiquidSmooth
I'm using LS 3.1 with the Dirty-V kernel and 1350 MHz overclocked CPU, it's a very fast/smooth ROM but it takes too much RAM... GNL is often killed and I've a max of 4 average sized apps at once.
What do you advice me ? Is the Beta stable enough as a daily setup ?
Also I had lot of issues with PA GApps by the past, I'd like to know if it's OK to use Slim GApps with this ROM
Thanks in advance
Just wanted to say that the beta version on my vzw galaxy nexus has been running great since Saturday! Only one freeze, but everything I've tried (except stock camera, as noted) works great! Had to install the older Netflix apk and zoom fx but WiFi tether, gmail, NFL mobile streaming live games and red zone yesterday works with no problems. Its very smooth too!! Data and cache on f2f and dalvick, not art as suggested.....
Quandrant standard was a 3965. I don't really pay much attention to benchmarks but I thought I would run it and post results but I can't seem to load the screenshot? Ha
Certainly planning to run this as my daily and really happy too!!
Thank you for your hard work guys!!
Edit: has anyone running the beta version messed with force GPU rendering and/or disable HW overlays to see how the GPU drivers respond?
No baseband
I can also confirm that after upgrade to 15.10.2014 there is no network.
Baseband version: Unknown
mobile data not enable
i flashedd this rom..but my mobile data is no service..sorry my bad english..
It works with flashing the older boot.img from 08.10.2014
After flashing the boot.img from the 08.10.2014 rom image, now I have mobile network on 15.10.2014 image.
No service
I have installed just the rom and i dont have service, did i do something wrong ..
can you say me what i have to do "step-by-step"
hi
i have one question , is this ROM stable enough for daily usage?
i dont flash nightlys every day, so i wonder if there's a stable nightly with the new GPU drivers
thanks
IIEtCII said:
hi
i have one question , is this ROM stable enough for daily usage?
i dont flash nightlys every day, so i wonder if there's a stable nightly with the new GPU drivers
thanks
Click to expand...
Click to collapse
For me it is stable enough, i use camera mx for taking a pic
Sent from my Galaxy Nexus using XDA Free mobile app
The only problem that I have encountered with omnirom is the inability to use a USB stick with the otg dongle. I believe I read somewhere that it is an unresolved issue with the ROM. Does anyone have any additional info on this? Also, has anyone found a workaround solution to this issue? Thanks.
LCD density?
I'm taking the "stable" version of this ROM for a spin now, and I like it very much. The only thing I miss is the LCD density setting that some ROMs have (slimkat, c-rom). Did I miss this somewhere in the settings? Setting the font to small is the closest thing I found.
thanks for that
Google Camera
Google Camera 2.4.023 appears to fix the camera crash on 20141015 beta. It seem to be working just fine, for me at least. Is it the same for everyone else?
Installed FML yesterday, the only problem I have is this:
pictures will not load. neither on gallery, nor on wallpaper selection or third party apps like QuickPic. The image files are definetily there (can see them through my pc) but the phone cannot load them. Tried clearing the data on Media manager, cleared cache/dalvik cache but nothing yet. What's the issue here?
volume wake
Hello
thanks for the rom and can you put volume to wake device because my power botton is broken.
thanks
Thanks for the fast and smooth ROM. I'd like to put a request for a kernel update that allows color settings (color balance, gamma and contrast) to be changed, as the Galaxy Nexus screen is notoriously poorly calibrated. Trickster mod and other kernel tweakers expose these settings with most kernels but not here.
I read at the main thread. I've bootloop to. I did the right instructions, but it doesn't work. TWRP 2.8.1.0, latest version of bootloader
Beta KitKat
Is the KitKat ROM Beta stable enough ?
I've read about too many issues (screenshot, camera, ...)
Thanks

[Q&A] [ROM][LOLLIPOP][UNOFFICIAL] Cyanogenmod: cm-12.0 for SM-T800 16gb - download b

[Q&A] [ROM][LOLLIPOP][UNOFFICIAL] Cyanogenmod: cm-12.0 for SM-T800 16gb - download b
Q&A for [ROM][LOLLIPOP][UNOFFICIAL] Cyanogenmod: cm-12.0 for SM-T800 16gb - download broken
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][LOLLIPOP][UNOFFICIAL] Cyanogenmod: cm-12.0 for SM-T800 16gb - download broken. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
maxal said:
+1 :good::
Click to expand...
Click to collapse
Looking forward to trying it!!!!!
Good Rom but i have one problem
SD card not working
I just wanted to confirm that the 20150128 build is working on my T800.
SD Card reads and writes fine.
Wifi works fine.
It seems stable enough for my daily use, so far.
Thank you.
freddy0077 said:
SD card not working
Click to expand...
Click to collapse
SDcard working.
Does it support multiple windows? What about playing HD mkv files using KMPLAYER or MX player?
p0k3y said:
Does it support multiple windows? What about playing HD mkv files using KMPLAYER or MX player?
Click to expand...
Click to collapse
Standard cm features read OP in development. (Short: no.)
Depends on what codecs the matroska container contains. mkv is like avi: you can put some really strange surprises in... So: may be... You can examine wit mkvinfo from mkvtools whats in you containers. MX Player brings it's own hw and hw+ codecs, so I would guess, if it plays your files on stock sammy it would play them on NVertigo/cm12, too.
I can't seem to transfer apps to my sd card, i get a not enough space error. However i seem to be able to read and write to my sd card just fine. Running latest version of the ROM, T800.
Sent from my HTC One M8 using Tapatalk
jinxpad said:
I can't seem to transfer apps to my sd card, i get a not enough space error. However i seem to be able to read and write to my sd card just fine. Running latest version of the ROM, T800.
Sent from my HTC One M8 using Tapatalk
Click to expand...
Click to collapse
It's known. Haven't added it to known issues yet - will do soon. Thanx.
power on
excelent very fast rom
I found 2 problems
1- when the tablet is carrying the same league not
2- sdccard apps disappear from folders
Excuse my English
alexwfonseca said:
excelent very fast rom
I found 2 problems
1- when the tablet is carrying the same league not
2- sdccard apps disappear from folders
Excuse my English
Click to expand...
Click to collapse
I don't understand 1-.
They does only if you are unpatient: read my notes on moving to sdcard in the Changelog and Download sectipn of OP of development thread.
wifi random issues
Considering wifi issues with channels, it probably comes with country limitations at some point.
For exemple, i know US wifi 2,4 range is allowed from channels 1 to 12.
In France, you are allowed to use 1 to 14.
I guess it's the same with 5 ghz wifi.
So there probably is some "country" related parameter in the Rom or when choosing the country at instalation setup option...
Tom31000 said:
Considering wifi issues with channels, it probably comes with country limitations at some point.
For exemple, i know US wifi 2,4 range is allowed from channels 1 to 12.
In France, you are allowed to use 1 to 14.
I guess it's the same with 5 ghz wifi.
So there probably is some "country" related parameter in the Rom or when choosing the country at instalation setup option...
Click to expand...
Click to collapse
That's an other part of the problem. We have set the region to "00". I'm not sure, if the localizationmsettingsmwhilemsetup have an effect here. I hope we soon het the localization setting in wifimsettings (like in cm11) back.
Smooth running
Installed latest build . . . no problems at all so far.
Lost root
Any reason this would not work on 32gb version?
Oversaturated screen makes this ROM unusable
I use the S4MiniSettings.apk fix in CM11 to avoid the frankly ludicrous colour over-saturation that the T800 has by default (the stock ROM has an option to fix the problem - all the reviews of the tablet I read told everyone to turn off the gaudy, eye-searing saturation that Samsung insists on shipping by default).
Now that nvertigo67 has stopped cm11 development and cm12 looks good enough to try out, I duly flashed to cm12 and was a) disappointed that there's still no built-in options to de-saturate the display and b) the CM11 apk no longer works in CM12. This meant going back to cm11 sadly - I'm a little mystified that the cm12 thread doesn't have more people complaining about the colour saturation level of the display!
Maybe everyone but me wears sunglasses whilst using the cm12 rom - it's the only logical explanation. Putting my T800 next to my Nexus 10 just shows the saturation madness on the former.
Any chance of a CM12 de-saturation option in the Settings of the T800 ROM?
rklrkl said:
I use the S4MiniSettings.apk fix in CM11 to avoid the frankly ludicrous colour over-saturation that the T800 has by default (the stock ROM has an option to fix the problem - all the reviews of the tablet I read told everyone to turn off the gaudy, eye-searing saturation that Samsung insists on shipping by default).
Now that nvertigo67 has stopped cm11 development and cm12 looks good enough to try out, I duly flashed to cm12 and was a) disappointed that there's still no built-in options to de-saturate the display and b) the CM11 apk no longer works in CM12. This meant going back to cm11 sadly - I'm a little mystified that the cm12 thread doesn't have more people complaining about the colour saturation level of the display!
Maybe everyone but me wears sunglasses whilst using the cm12 rom - it's the only logical explanation. Putting my T800 next to my Nexus 10 just shows the saturation madness on the former.
Any chance of a CM12 de-saturation option in the Settings of the T800 ROM?
Click to expand...
Click to collapse
Please read OP. I will not extend cm12 settings. So as soon as "CM12 de-saturation option" shows up in cm12 it will be in our rom. Remember that cm12 is in a very early state and there are many features that wait to be implementet.
On the other hand: if you know what sysfs value is manipulated for the desaturation, I'm glad to put a commented out line in /system/etc/init.d/10systemtuning you can use. I would guess it's one of /sys/devices/platform/s5p-mipi-dsim.1/lcd/panel/mdnie/*
OK, this inspired me to play with the apk settings and I think I have the lines for your 10systemtuning file:
# set mDNIe colour mode
# 0 = Standard
# 1 = Dynamic
# 2 = Movie (note: this is the only non-saturated mode)
# 3 = Natural
# 4 = Auto
# echo 2 >/sys/devices/platform/s5p-mipi-dsim.1/lcd/panel/mdnie/mode
This works great in CM11 and also CM12 with mode 2 without the apk present (even the CM11 and CM12 boot animations are non-saturated for the first time ever for me - yay!). I'm quite happy to do this change in CM12 myself, but other folks might benefit from it if you put the one-liner in a future CM12 build (even commented out...someone might see the option and realise the colours are "wrong" ).
BTW, I suspect we'll not see the above mDNIe colour mode setting in CM12, because it was never standard in CM11 either. I'm not sure if it's because it's a Samsung-specific thing that the CM team didn't want to cater for.
rklrkl said:
OK, this inspired me to play with the apk settings and I think I have the lines for your 10systemtuning file:
# set mDNIe colour mode
# 0 = Standard
# 1 = Dynamic
# 2 = Movie (note: this is the only non-saturated mode)
# 3 = Natural
# 4 = Auto
# echo 2 >/sys/devices/platform/s5p-mipi-dsim.1/lcd/panel/mdnie/mode
This works great in CM11 and also CM12 with mode 2 without the apk present (even the CM11 and CM12 boot animations are non-saturated for the first time ever for me - yay!). I'm quite happy to do this change in CM12 myself, but other folks might benefit from it if you put the one-liner in a future CM12 build (even commented out...someone might see the option and realise the colours are "wrong" ).
BTW, I suspect we'll not see the above mDNIe colour mode setting in CM12, because it was never standard in CM11 either. I'm not sure if it's because it's a Samsung-specific thing that the CM team didn't want to cater for.
Click to expand...
Click to collapse
Great. Thanx. I will put it in. Special Thanx for the documentation.
We have the kerneldriver mini-mdnie and not mdnie - if I find the time I wil t4y to adapt the mdnie display settings from cm11 s3 to our tab - but I don't promise anything. For the short run we take 10systemtuning.
Hi everyone, I am new here but have been following development progress on the t800 for a while and am very impressed!
I just flashed this ROM as Im no fan of touchwiz and its great. The only issue I'm having is that I experience some lag/stuttering when navigating through certain menus. Also typing is very delayed in some text fields. Is anyone else experiencing this or just me? Should i try reflashing and see what happens?
Either way, great work. You have done a better job than Samsung in my opinoin!

N&N vs Fulmics

I am currently on Fulmics and want to try N&N 7.1.
Could someone who have used these 2 ROMs tell me the main differences between them ?
ones named N&N and the other is fulmics
lapocompris said:
I am currently on Fulmics and want to try N&N 7.1.
Could someone who have used these 2 ROMs tell me the main differences between them ?
Click to expand...
Click to collapse
im sorry but this thread is not going anywhere, just nandroid bkup and flash with a checklist of things that ur looking for
I happened to use both of them. I used them both with their respective stock kernels, and running the kppd script to get kcal support on stock rom. Anyways, in short N&N 7.1 is the best ROM that I have had on my G3. Fulmics was not as smooth, buggy at times causing random reboots, and most importantly it gave me just 2.5 hrs of SoT. I had Greenify and Amplify installed on both ROMs. Both ROMs heat the device up to some degree but Fulmics temperature was definitely higher doing similar tasks, especially while capturing videos. So, in light of this I have switched to the N&N rom. Its is buttery smooth. The memory management is very good and the battery life is 3.5 hrs of SoT now, though sometimes it can be as low as 3 hrs. The only drawback I have noticed is that it doesn't have the Roboto font in its choice of fonts. Using 3rd party software to change fonts only changes parts of the ROMs fonts...for e.g. in Viber, the font in the message typing box is the one that the 3rd party font changer set up....but the messages themselves are in the system font. Other than that minor issue, N&N is the way to go. I must admit that I have used several version of Fulmics in the past but haven't tested the latest 6.0-6.1 version since I am very satisfied with N&N rom. Hope that helps.
On a side note, Limitless was similar to Fulmics with respect to fluidity and battery life. But, it had a serious issue wherein opening more than 2 or 3 apps or opening more than 2 tabs in browsers caused a huge lag and caused the phone to freeze up and reboot sometimes. If it were upto me I wouldn't recommend that ROM to anyone due to this issue.
So basically my order of preference of Custom ROMs based on Stock are N&N > Fulmics> Limitless
thanks for sharing knowledge
soms_2 said:
I happened to use both of them. I used them both with their respective stock kernels, and running the kppd script to get kcal support on stock rom. Anyways, in short N&N 7.1 is the best ROM that I have had on my G3. Fulmics was not as smooth, buggy at times causing random reboots, and most importantly it gave me just 2.5 hrs of SoT. I had Greenify and Amplify installed on both ROMs. Both ROMs heat the device up to some degree but Fulmics temperature was definitely higher doing similar tasks, especially while capturing videos. So, in light of this I have switched to the N&N rom. Its is buttery smooth. The memory management is very good and the battery life is 3.5 hrs of SoT now, though sometimes it can be as low as 3 hrs. The only drawback I have noticed is that it doesn't have the Roboto font in its choice of fonts. Using 3rd party software to change fonts only changes parts of the ROMs fonts...for e.g. in Viber, the font in the message typing box is the one that the 3rd party font changer set up....but the messages themselves are in the system font. Other than that minor issue, N&N is the way to go. I must admit that I have used several version of Fulmics in the past but haven't tested the latest 6.0-6.1 version since I am very satisfied with N&N rom. Hope that helps.
On a side note, Limitless was similar to Fulmics with respect to fluidity and battery life. But, it had a serious issue wherein opening more than 2 or 3 apps or opening more than 2 tabs in browsers caused a huge lag and caused the phone to freeze up and reboot sometimes. If it were upto me I wouldn't recommend that ROM to anyone due to this issue.
So basically my order of preference of Custom ROMs based on Stock are N&N > Fulmics> Limitless
Click to expand...
Click to collapse
thanks for sharing your experience , I tried almost all G3 D855 roms available ,with all its versions but I didn't try [email protected]
the only 2 I had recommended to others was Fulmics 5 an Resurrection Remix 5.7.3
I need Fulmics for (smart screen "keep screen on while detecting face" - Quick remote -knock code "while screen off" )
and I need RR for (long battery life - privacy "restrict data for both mobile data and wifi as well" - themes - and BEST OF ALL Recent apps tweak " hiding apps from recent panel " that I never found such option in any rom.
I dream of having a rom with all these features

XZ1 Compact Fw's: PROs & CONs

Help me to create mini FAQ.
Stock
PROs:
CONs:
AOSP
PROs:
CONs:
crDroid [AlexKarimov]
PROs:
1 - Fast: Very responsive and loads quick. Example: stock used to delay when using google maps at all the wrong times. This ROM is lightning quick and I never miss a turn or exit.
2 - Stable: I've had only one or two random reboots but it's very rare.
3 - Customization: There is a high level of customization in this ROM. A LOT of options. At this point, I can't even tell you what I'm missing.
Bonus: Stock launcher is very nice. I usually upgrade to Nova for one reason or another but this has almost all the same features as Nova.
CONs:
1 - Data speed: I hesitate to put this here because I'm not sure if it's my ROM or incorrect APN settings(I don't remember stock so I've had to experiment). I've played around with different APNs and found one that works really good but data speed still seems a little slower than stock but only on Play Store for some reason.
Pixel Experience
PROs:
CONs:
LineAge OS 15.1
PROs:
CONs:
LineAge OS 16
PROs:
CONs:
I've had crDroid for about 2 months now, here's what I've observed:
crDroid
PROs:
1 - Fast: Very responsive and loads quick. Example: stock used to delay when using google maps at all the wrong times. This ROM is lightning quick and I never miss a turn or exit.
2 - Stable: I've had only one or two random reboots but it's very rare.
3 - Customization: There is a high level of customization in this ROM. A LOT of options. At this point, I can't even tell you what I'm missing.
Bonus: Stock launcher is very nice. I usually upgrade to Nova for one reason or another but this has almost all the same features as Nova.
CONs:
1 - Data speed: I hesitate to put this here because I'm not sure if it's my ROM or incorrect APN settings(I don't remember stock so I've had to experiment). I've played around with different APNs and found one that works really good but data speed still seems a little slower than stock but only on Play Store for some reason.
General Impression: I love this ROM! It has just about everything I want(minus a few tweaks that are in AEX) but any drawbacks I've found are very minimal compared with the benefits.
Thank you for this comparison. I've recently purchased a second xz1c and just loaded AEX on it, so I'll give some impressions in a few weeks on that.
AlexKarimov said:
I've had crDroid for about 2 months now, here's what I've observed:
Thank you for this comparison. I've recently purchased a second xz1c and just loaded AEX on it, so I'll give some impressions in a few weeks on that.
Click to expand...
Click to collapse
Thanks for review! Together we can bring up neat comparision of xz1 FW's!
Stock fw
pro:
Good battery life and has ultra stamina mode. Also Sony stock apps and audio tuning if you are into that kind of stuff. With combining firmware bits you can get volte and fingerprint working in US T-mobile.
con:
September 2019 is the last security patch, since then multiple vulnerabilities have been found including bluetooth "Bluefrag" vulnerability.
Lineage OS 17
Overall very clean and snappy rom. It's currently my daily driver.
Pro:
-Android 10.0 and everything that comes with it:
Built in gesture navigation
Re-worked permission management
New launcher/recents menu
-average battery life
-stock camera
-passes safetynet check
-trebuchet launcher with app lock functionality
-very stable, so far I have had no random reboots or anything of the sort.
Con:(not a lot)
-does not have picture preview after picture was taken on back camera in stock cam
-stock cam cannot save to sd card
Thanks for sharing your findings! Would you recommend LOS 16 or 17 over stock fw? How stable is it and how's the battery life? I have stock oreo and don't want to update due to the complaints. I've experienced some lag and restarts lately but I wonder if the long process of unlocking bl and flashing custom fw is worth it.
moist_line said:
Thanks for sharing your findings! Would you recommend LOS 16 or 17 over stock fw? How stable is it and how's the battery life? I have stock oreo and don't want to update due to the complaints. I've experienced some lag and restarts lately but I wonder if the long process of unlocking bl and flashing custom fw is worth it.
Click to expand...
Click to collapse
Big thanks also from me to MDomokos for sharing the experience.
I'm also very interested in answers for the questions posted by moist_line.
moist_line said:
Thanks for sharing your findings! Would you recommend LOS 16 or 17 over stock fw? How stable is it and how's the battery life? I have stock oreo and don't want to update due to the complaints. I've experienced some lag and restarts lately but I wonder if the long process of unlocking bl and flashing custom fw is worth it.
Click to expand...
Click to collapse
Using LOS 16.0 for 2 weeks with 47.2.A.11.228 stock firmware. Working perfectly and no problems with any app (no GAPPS installed and only using openSource apks such as: Signal, Telegram, K-9, QKSMS, OsmAnd, etc...)
Battery life, better than with stock Android 8.0 ( i never used Android 9 from Sony, just when i updated firmware to reboot and install LineageOS )
Since i'm working from home, is true that my XZ1C uses wifi all the time, but anyways, 3 days of battery is awesome
moist_line said:
Thanks for sharing your findings! Would you recommend LOS 16 or 17 over stock fw? How stable is it and how's the battery life? I have stock oreo and don't want to update due to the complaints. I've experienced some lag and restarts lately but I wonder if the long process of unlocking bl and flashing custom fw is worth it.
Click to expand...
Click to collapse
I've been using Lineage OS 17 by modpunk for the last three weeks and it's been very reliable. I have nano Gapps installed and get about 7% of battery used per hour with the screen on, and about 0.4% of battery drained per hour in stand by mode as reported by Franco Kernel Manager. Battery life for me is a bit worse than stock as there is no fine control over battery modes such as with stamina mode. I can get two days battery life with about 5 hours of screen on time, though I limit my charging to between 85%-15% which makes it a bit shorter.
I like the android 10 gestures as it frees up more space on the screen and I also like the new permission management for location. And I can't live without adaway which requires root.
I personally am happy with unlocking the boot loader and there is no significant difference besides when initially turning on the phone it shows a boot loader unblocked message. And the newer security patches are worth it in my opinion.
There is a easy to follow PDF guide that can explains all of the steps in the thread about DRM Key backups. https://forum.xda-developers.com/xperia-xz1-compact/development/devonly-exploits-temp-root-to-backup-t3795510
I'll link it here if I find it.
But I wouldn't recommend it if you are planning on selling your phone in the near future.
Edit:
Found the PDF https://forum.xda-developers.com/showpost.php?p=78255334&postcount=382
Make sure to read all instructions thoroughly and donate to developers if possible.
Hope this all helped.

Question A few questions from a new owner.

Hello everyone, I'll be getting my Poco F3 tomorrow and I have a few questions. Most of them were asked already but they're relatively old already and I'm unsure whether it got fixed or not. Anyways, here are my questions.
1) Was the proximity sensor issue patched/fixed? Is it any better than the release? I've seen quite a few commentaries regarding it's poor quality.
If it didn't get fixed, what are some workarounds?
2) In Samsung phones (at least a few years back) your camera quality used to be ABSOLUTELY TRASH if you used an AOSP ROM. Does the same happen with this phone? If so, GCam is the only workaround?
3) Is the real world performance (gaming, scrolling, app loading times) lower in AOSP ROMs?
Please reply to this one only if you have measured the performance on both ROMs yourself instead of repeating what somebody else said (we don't know the variables they had during testing).
4) Is it possible to flash an official recovery ROM with a locked bootloader? If so, would this tool be the safest way to do?
GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot - GitHub - Szaki/XiaomiADBFastbootTools: A simple tool for managing Xiaomi devices on desktop using ADB and Fastboot
github.com
5) Is it possible to downgrade a update through flashing a recovery ROM? (e.g. 12.5.7 to 12.5.6).
6) Is the screen dimming when gaming still an issue? If not, are there any workarounds?
7) Are there any other issues that I didn't mention or things you'd like to say?
Notes:
- When I say "AOSP ROMs" I'm mainly thinking about Lineage and MicroG for Lineage.
- Feel free to only reply to one or two of them, I'll be happy as long as the information is legitimate.
1. ROMs based on the ROM that was banned from here due to its name trees generally don't have much issue with it, as long as the hardware goes - it is as inaccurate on MIUI. With some lower quality ROMs it may be better or worse, as with anything else
There was one workaround with disabling the proximity sensor and turning off the screen when in-call, but that's rather a half measure.
2. There is MIUI camera port for Alioth somewhere, but as now most ROMs are based on A12 the compatibility may vary.
Gcam by BSG works well even with default settings and it supports all the hardware, so there's that. Needless to say, it doesn't support upscaling present in MIUI cam (so the front camera will take ~5 Mpix photos, compared to the fake 20 Mpix in MIUI).
3. I've used MIUI and some AOSP/Pixel ROM for some time and although benchmarking apps indeed show a little lower scores on AOSP (at least the few I've tried), AOSP ROMs generally feel more snappy - the difference may stem from the UX itself tho (i.e. janky MIUI gestures vs AOSP gestures).
4. I'd say it's always safer to go with official fasboot ROMs. Alioth is a bit messy when it comes to recovery in general; some ROMs work only with their own recovery images, some are recommended to use with the AOSP recovery, and both official and unofficial TWRPs aren't stable enough (or really worth it, IMO).
5. No idea; I believe Alioth has ARP, so you may need a workaround for it.
6. Never happened to me (MIUI or AOSP), it may be either vendor or screen panel specific.
7. Some people report slow charging speeds, which (as long it doesn't take over two hours) may be considered a feature as constant charging with full power is known to exhaust PMIC chips leading to hardware failures in the long run.
Apart from that, there is the green tint, which may happen in 120 Hz mode on some panels, but it is calibrated in some ROMs. It does occur on MIUI too.
EDIT: Also idle drain, but that's again ROM specific. Iirc LineageOS is generally stable when it comes to that.
Thank you very much for your reply, I have the device for a day and I have no issues with it.
My only qualm is the display panel on low brightness which looks rather bad (colors seem to shift only on certain areas, probably because it's not dimming it evenly) but that's fair considering the price point of the phone.
Also, the camera isn't even as bad as I thought, a happy surprise.

Categories

Resources