[BUG] Why installing a custom Rom based on AOSP changes the rotation parameters - Xiaomi Redmi Note 4 Questions & Answers

When rom is miui based the rotation sensor is pretty good and gives no excessive rotation. But when we change Rom to rr, Aex it just keep rotating with even a slight movement. Any way to make it like before?

Help
kamrantahir said:
When rom is miui based the rotation sensor is pretty good and gives no excessive rotation. But when we change Rom to rr, Aex it just keep rotating with even a slight movement. Any way to make it like before?
Click to expand...
Click to collapse
I also have the same problem, but also the camera presents me problems when I switch to video or unlike

Related

[Recommendations] Stable daily driver ROM for Mi 5

Hey guys, recently my father got tired of ****ty MIUI and wanted something better for his Mi 5. Since it's not my phone, I cannot test various ROMs and kernels by clean flashing them.
I just need one ROM that I can switch to on his phone from MIUI.
It needs to be 100% stable (he is sick of bugs), needs to have great calling and bluetooth connection, and great battery life.
Please let me know if such ROM exists for Mi 5, and which one is it
(Do you guys face any issues with bluetooth speakers or taking calls via bluetooth in car?)
You can start with jdcteam's aosp. Has been really solid for me.
arnavbatra said:
Hey guys, recently my father got tired of ****ty MIUI and wanted something better for his Mi 5. Since it's not my phone, I cannot test various ROMs and kernels by clean flashing them.
I just need one ROM that I can switch to on his phone from MIUI.
It needs to be 100% stable (he is sick of bugs), needs to have great calling and bluetooth connection, and great battery life.
Please let me know if such ROM exists for Mi 5, and which one is it
(Do you guys face any issues with bluetooth speakers or taking calls via bluetooth in car?)
Click to expand...
Click to collapse
I've been using LineageOS with 0 problems so far. But it does take some time to set it up that way. For instance, you need to flash the MIUI camera to improve camera performance, and under display calibration adjust the RGB values to 90% to prevent image retention (a problem on MIUI too).
I can confirm that Bluetooth works fine, calling is clear and battery life is good but not better/worse than MIUI. I haven't tried taking calls over a car's Bluetooth.
You should also check out the Xiaomi.eu weekly MIUI 9 builds as they usually fix what Xiaomi broke in their MIUI builds and are actually supported by Xiaomi.
Mr.201 said:
You can start with jdcteam's aosp. Has been really solid for me.
Click to expand...
Click to collapse
xdadevet said:
I've been using LineageOS with 0 problems so far. But it does take some time to set it up that way. For instance, you need to flash the MIUI camera to improve camera performance, and under display calibration adjust the RGB values to 90% to prevent image retention (a problem on MIUI too).
.
Click to expand...
Click to collapse
Thank you for the recommendations guys. Are you using the stock kernel or any custom kernel like BB kernel, Nagatobimaru etc?
What is your opinion about AOSPA and RR ?
AOSP Extended all the way. Using it from past 3 months.
arnavbatra said:
Thank you for the recommendations guys. Are you using the stock kernel or any custom kernel like BB kernel, Nagatobimaru etc?
What is your opinion about AOSPA and RR ?
Click to expand...
Click to collapse
Nagatobimaru kernel has terrible battery life for me (like 1h30m SOT even though I was initially excited to try it out because it incorporates EAS). I use LOS stock freq kernel, which removes the underclock of the 32GB Mi5 from 1.8GHz to 2.15GHz but is otherwise just the stock LOS kernel. On this kernel I get between 3-4h30m SOT.
AFAIK LOS is the only ROM with display calibration and all the others have no way to fix the severe image retention which is my main reason for sticking with it. If it doesn't bother you or affect your unit then I can highly recommend AEX which seems to be the ROM 90% of the devs are on.
xdadevet said:
Nagatobimaru kernel has terrible battery life for me (like 1h30m SOT even though I was initially excited to try it out because it incorporates EAS). I use LOS stock freq kernel, which removes the underclock of the 32GB Mi5 from 1.8GHz to 2.15GHz but is otherwise just the stock LOS kernel. On this kernel I get between 3-4h30m SOT.
AFAIK LOS is the only ROM with display calibration and all the others have no way to fix the severe image retention which is my main reason for sticking with it. If it doesn't bother you or affect your unit then I can highly recommend AEX which seems to be the ROM 90% of the devs are on.
Click to expand...
Click to collapse
What do you mean by the image retention issue? And what have you calibrated? As far as I understand, you have just tweaked the RGB values of the screen. Can you tell me your values? I think the same thing can be done via Kernel Adiutor if you are on a kernel that supports KCAL. AFAIK, stock LOS kernel doesn't have it but most ROMs and all custom kernels have it.
What about AOSP by JDC team, it appears very stable with EAS?
xdadevet said:
Nagatobimaru kernel has terrible battery life for me (like 1h30m SOT even though I was initially excited to try it out because it incorporates EAS). I use LOS stock freq kernel, which removes the underclock of the 32GB Mi5 from 1.8GHz to 2.15GHz but is otherwise just the stock LOS kernel. On this kernel I get between 3-4h30m SOT.
AFAIK LOS is the only ROM with display calibration and all the others have no way to fix the severe image retention which is my main reason for sticking with it. If it doesn't bother you or affect your unit then I can highly recommend AEX which seems to be the ROM 90% of the devs are on.
Click to expand...
Click to collapse
Does this problem have anything in common to the top edge of phone bleeding? Isnt that hardware's fault?
RootNightmareX said:
Does this problem have anything in common to the top edge of phone bleeding? Isnt that hardware's fault?
Click to expand...
Click to collapse
Yes, it's the same problem - I am unaware whether this is a software or hardware problem, but you can correct it 100% with software. It looks like lightbleed right around the border of the phone and you can see ghosting of previus apps around the corners (especially on a grey background). It's easy to fix in LineageOS, but I've had trouble in every other ROM I tried so far.
xdadevet said:
Yes, it's the same problem - I am unaware whether this is a software or hardware problem, but you can correct it 100% with software. It looks like lightbleed right around the border of the phone and you can see ghosting of previus apps around the corners (especially on a grey background). It's easy to fix in LineageOS, but I've had trouble in every other ROM I tried so far.
Click to expand...
Click to collapse
Its not ghosting its more like a radiant, something like a glow that increase and decrase...
..
arnavbatra said:
What do you mean by the image retention issue? And what have you calibrated? As far as I understand, you have just tweaked the RGB values of the screen. Can you tell me your values? I think the same thing can be done via Kernel Adiutor if you are on a kernel that supports KCAL. AFAIK, stock LOS kernel doesn't have it but most ROMs and all custom kernels have it.
What about AOSP by JDC team, it appears very stable with EAS?
Click to expand...
Click to collapse
It looks light an orange tinted lightbleed right around the borders of the display and some ghosting of previous apps are overlayed on the current app (especially visible on grey backgrounds). Check the attached image to see what mean, and this is only about 50% of how bad it can get if you don't adjust for it.
Yes I just tweaked the RGB values to 90% (anything more and you can still notice the effect).
I tried using Kernel Adiutor to fix this problem to no avail, using different ROM and kernel combinations. I never checked if the kernel supports KCAL specifically though.
It's been too long since I used JDC's ROM, but if I remember correctly it was stable and fast but lacked essential features at the time (music playback controls, lockscreen torch, display calibration settings). Their Oreo ROM is far ahead of Lineage 15 in in terms of stability though, not that it's DD ready.
xdadevet said:
It looks light an orange tinted lightbleed right around the borders of the display and some ghosting of previous apps are overlayed on the current app (especially visible on grey backgrounds). Check the attached image to see what mean, and this is only about 50% of how bad it can get if you don't adjust for it.
Yes I just tweaked the RGB values to 90% (anything more and you can still notice the effect)
Click to expand...
Click to collapse
Woah thanks for sharing this man, I didn't know about this, can you please share the screenshot of the settings you have made?
I have the same issue and I can't decide which ROM to flash. MIUI 8 is too laggy, MIUI 9 is faster but all apps crash randomly. I will unlock my phone tomorrow (after the stupid 72 hours waiting period) and I am hoping that this discussion will help us decide. Most probably it will be a choice between Xiaomi.eu or LOS.
arnavbatra said:
Woah thanks for sharing this man, I didn't know about this, can you please share the screenshot of the settings you have made?
Click to expand...
Click to collapse
Sure, no problem. You can find these Settings under Settings > Display > Live Display > Colour Calibration
Xpme said:
I have the same issue and I can't decide which ROM to flash. MIUI 8 is too laggy, MIUI 9 is faster but all apps crash randomly. I will unlock my phone tomorrow (after the stupid 72 hours waiting period) and I am hoping that this discussion will help us decide. Most probably it will be a choice between Xiaomi.eu or LOS.
Click to expand...
Click to collapse
As someone who recently used both Xiaomi.eu and LOS14.1 I might be able to clear that up.
Xiaomi.eu MIUI9 build is almost identical to MIUI 8. There are a few minor tweaks to the UI such as the task switcher which is now more immersive and the new icon pack. Settings are now more bundled together and ROM/System info is graphically displayed. Split screen multitasking seems to be the only new feature. I haven't experienced a single app crash, but the system animation speed was set way to fast by default and transition animations show tearing each time you switch apps. In short, it's fast but not smooth.
I switched back to LOS quite quickly. The only feature MIUI has that LOS doesn't is Dual Apps, and since I don't use that the choice was very simple. LOS is much smoother and faster, with minimal features on top of AOSP. I enjoy the additions, it doesn't feel bloated or barebones.
If you are going to use LOS, I recommend doing the following:
-If you have a 32GB Mi5, flash the LOS stock freq kernel
-Set the display calibration as per my previous posts
-Activate touch home button, always on fingerprint unlock
-Install Magisk
-Flash MIUI camera Magisk module + OISprop-Magisk
-Flash iYTBP Magisk module
-Flash unified hosts Adblock Magisk module (make sure to select systemless hosts in Magisk settings)
-Install Google camera HDR+
-Use Nova (paid) or Lawnchair (free) as the launcher
That should get you going and solve most if not all annoyances coming from MIUI. You'd be amazed with the quality of Google Camera HDR+! Just check the attached samples (they are all compressed due to Xda but you'll get the point).
xdadevet said:
As someone who recently used both Xiaomi.eu and LOS14.1 I might be able to clear that up.
Xiaomi.eu MIUI9 build is almost identical to MIUI 8. There are a few minor tweaks to the UI such as the task switcher which is now more immersive and the new icon pack. Settings are now more bundled together and ROM/System info is graphically displayed. Split screen multitasking seems to be the only new feature. I haven't experienced a single app crash, but the system animation speed was set way to fast by default and transition animations show tearing each time you switch apps. In short, it's fast but not smooth.
I switched back to LOS quite quickly. The only feature MIUI has that LOS doesn't is Dual Apps, and since I don't use that the choice was very simple. LOS is much smoother and faster, with minimal features on top of AOSP. I enjoy the additions, it doesn't feel bloated or barebones.
If you are going to use LOS, I recommend doing the following:
-If you have a 32GB Mi5, flash the LOS stock freq kernel
-Set the display calibration as per my previous posts
-Activate touch home button, always on fingerprint unlock
-Install Magisk
-Flash MIUI camera Magisk module + OISprop-Magisk
-Flash iYTBP Magisk module
-Flash unified hosts Adblock Magisk module (make sure to select systemless hosts in Magisk settings)
-Install Google camera HDR+
-Use Nova (paid) or Lawnchair (free) as the launcher
That should get you going and solve most if not all annoyances coming from MIUI. You'd be amazed with the quality of Google Camera HDR+! Just check the attached samples (they are all compressed due to Xda but you'll get the point).
Click to expand...
Click to collapse
Wow! that was very informative. Thanks a lot man :good: . And yes, I get the point about the photo samples are amazing.
I have the 32 GB version and I already purchased Nova Launcher and use no matter what. I will have to find the addons you mentioned as I have no idea what they do. It's the first time I install a custom ROM on my MI 5. One final question, do you have any thoughts on AOSP Extended?
@xdadevet
Hi, where is OISprop module ?
Wysłane z mojego MI 5 przy użyciu Tapatalka
Xpme said:
Wow! that was very informative. Thanks a lot man :good: . And yes, I get the point about the photo samples are amazing.
I have the 32 GB version and I already purchased Nova Launcher and use no matter what. I will have to find the addons you mentioned as I have no idea what they do. It's the first time I install a custom ROM on my MI 5. One final question, do you have any thoughts on AOSP Extended?
Click to expand...
Click to collapse
I can add all the files you need to a dropbox folder and share the link if that would be easier? I find that the Mi5 is super easy to modify, you shouldn't worry too much. I'll add the firmware you need and GAPPS if that would help you transition.
Yes, AEX is a great ROM with many features. Most Devs seem to be on it (going by their discussions). I haven't found a way to fix my LCD issues on AEX yet, which is the main reason for not using it currently.
rafix96 said:
@xdadevet
Hi, where is OISprop module ?
Wysłane z mojego MI 5 przy użyciu Tapatalka
Click to expand...
Click to collapse
You need to run the apk after you flashed the magisk module and rebooted your phone to calibrate the OIS.

Manual focus on custom rom?

Just wondering, is it possible and how to get manual focus on any custom roms?
There was manual focus option in stock lollipop rom, but i never managed to find some camera app that will let me focus manually so far on custom roms. Im currently using Ressurection Remix 7.1.2.
Any help would be appreciated.
momirsarac said:
Just wondering, is it possible and how to get manual focus on any custom roms?
There was manual focus option in stock lollipop rom, but i never managed to find some camera app that will let me focus manually so far on custom roms. Im currently using Ressurection Remix 7.1.2.
Any help would be appreciated.
Click to expand...
Click to collapse
You mean tuch fokus? Does work for me. I use
this
camera app, as far as i can remember the stock camera app has the option, too.
DrAcula04 said:
You mean tuch fokus? Does work for me. I use
this
camera app, as far as i can remember the stock camera app has the option, too.
Click to expand...
Click to collapse
No,not touch focus. Manual,where you could set fixed distance for focus.
momirsarac said:
No,not touch focus. Manual,where you could set fixed distance for focus.
Click to expand...
Click to collapse
Yes I know what you're talking about, a fixed slider. It was a nice feature to LG's stock camera app but i'm afraid that's within their closed software and framework and I highly doubt it can be ported to AOSP correct me if im wrong

Is anyone Facing Image Retention issue on Oreo based ROMs?

As we all Know, Some Tianma Screen Panel has Image Retention Issue, but on Custom ROMs, we adjusted Color Calibration via Either Kernel tweak or inside Display Settings. But with Oreo (8.0 and 8.1) Things have changed. UI turned Whitish Material Color and Display Settings for adjusting Different stuffs too. So Anyone Of u Facing same issue with 8.0/8.1 based ROMs?? I'm on Omni right Now and till now not faced. But What About U all..
Waiting for valuable Response..
TIA..
I installed omnin 8.1 twice in my redmi note 4 and rolled back to LOS 14.1 because just after 15 minutes of usage I got image retention in omni 8.1 .
I also got the same in RR 6 (oreo).
parthopgogoi said:
I installed omnin 8.1 twice in my redmi note 4 and rolled back to LOS 14.1 because just after 15 minutes of usage I got image retention in omni 8.1 .
I also got the same in RR 6 (oreo).
Click to expand...
Click to collapse
Wait for next Build of Omni. It will have Manual RGB Calibration options. Till then U can keep Night Mode On with minimum Intensity. Or with Franco Kernel, Adjust RGB Value to 240 each.
hoshang.govil12 said:
As we all Know, Some Tianma Screen Panel has Image Retention Issue, but on Custom ROMs, we adjusted Color Calibration via Either Kernel tweak or inside Display Settings. But with Oreo (8.0 and 8.1) Things have changed. UI turned Whitish Material Color and Display Settings for adjusting Different stuffs too. So Anyone Of u Facing same issue with 8.0/8.1 based ROMs?? I'm on Omni right Now and till now not faced. But What About U all..
Waiting for valuable Response..
TIA..
Click to expand...
Click to collapse
On firehound. Gotta say the burn in is quite bad. Even though it fixes over time, but still.
MyNameIsRage said:
On firehound. Gotta say the burn in is quite bad. Even though it fixes over time, but still.
Click to expand...
Click to collapse
If it's in warranty, Get screen Replaced.
i had same problem i just change screen panel and set everything on 50% (picture https://www.androidpolice.com/wp-content/uploads/2016/03/nexus2cee_cal.png) everything is fine now
Found Fix
I found the solution.. Just flash havoc rom will fk kernal.. Use smart pixel feature. Set the smart pixel setting to 25 percentage... And in display setting go to colour and set all the value to 95 percentage.. Done ??

[MOD][TESTING] Camera Sensor Fix and Google Camera

[SIZE=+2][MOD][TESTING] Camera Sensor Fix and Google Camera[/SIZE]
Please test, share issues, questions and offer help!
What does this mod do?​
It replaces the libmmcamera_imx318*.so and libmmcamera_imx268*.so files inside /system/vendor/lib/ with ones I edited.
It also adds a missing reference to libadsprpc.so in /system/etc/public.libraries.txt on custom firmwares.
Warning​From my experience this mod can't really break anything. At most you'll have a non working camera. In this situation you need to either flash your ROM again or restore these files from a backup.
If you're on MIUI use the installer that doesn't change your public.libraries.txt file! Otherwise your device won't boot.​
What does it fix?​
It fixes a sensor and active array size mismatch issue in our devices. It makes a lot of google camera mods work (to some degree).
It seems to have also fixed the cropping bug everyone has been complaining about. Since the array size mismatch appears to be cropping the resolution down to the next working one.
Shut up already, I just want to take some great looking photos!​
Go ahead and flash one of these zip files:
CFW: https://mega.nz/#!sfAERYxL!WdJO3u9sFwddB22echsp0-2AYsW1nVIynROo3rVjeqQ [v5] [14-05-2018]
MIUI: https://mega.nz/#!UexHDThY!O2CUQ1GVqG9CSAqfgMRXthKVq4vgPPq6-wbKflAGbio
Install the following gcam mod:
https://www.celsoazevedo.com/files/android/google-camera/f/GCam_5.1.018_by_SerJo87_1.6RC2_test4c.apk
What's working:
HDR+ and HDR enchanced (Back and Front)
Portrait Mode (Back and Front)
Zero Shutter Lag
Motion Photos
Video Recording
Slow Motion (120 and 240 fps)
What's Not Working:
Nothing!
What isn't working very well:
Light flickering in 240fps slowmo.
Low exposure in Lens Blur. (The current fix is to set the Lens Blur resolution to the default 5MP)
Low exposure in Panorama.
Cropped 4k Recording (Hardware enabled EIS. Doesn't seem to be a bug.)
Missing toggle between HDR modes on the back camera (It takes photos with HDR+)
Recommendations
If you don't mind losing Motion Photos on the Back Camera turn on the Use Hexagon DSP option for slightly better performance and stability
Change the HDR+ parameters to Pixel 2017 stable.
Turn on Portrait ZSL mode
Change Base model inside Tuning back cam to Nexus 6P. (More detailed photos plus better and faster autofocus)
SerJo87 Google Camera's default tuning settings are tweaked for another smartphone's camera sensor. As a personal recommendation go into Tuning back cam and disable the Tuning master switch for it to use the default Base Model values. I've spent hours tweaking and have found the default Nexus 6P values to be the best ones.
Change the Lens blur megapixels to 5MP. (Fixes the low exposure issue)
Compatibility​
Personally tested and fully working on the latest AospExtended.
Reported semi-working on the latest unofficial Resurrection Remix.
Reported working on the latest Lineage 15.1.
Reported working on crDroid.
Reported working in MIUI.
This mod is not needed on the latest Cardinal-AOSP. Psy_Man has included this fix.
Google Camera Mod Repository​
Go grab a bunch of other google camera mods if you're feeling adventurous and hope to find a more compatible one.
https://www.celsoazevedo.com/files/android/google-camera/
I need testers, helpers, anything and everything is welcome!​
Why I did it​
Coming from a Redmi Note 4X, I was pretty letdown by the lack of a working google camera mod for my new Mi Note 2. I upgraded my phone in almost every aspect except I was taking far inferior quality photos. This drove me to find out what was going on with our device.
Getting technical​
Going through several gcam mods I noticed a pattern. This error to be exact:
E/QCamera (510): <MCI><ERROR> update: 102: invalid input: active_array [5344, 4016], sensor size [5488, 4112]
For some reason, the active array size is smaller than the sensor size. Which cannot happen. This is what I fixed in the libmmcamera_imx318_primax.so file.
If you want a detailed explanation of what I changed in the file go over here https://forum.xda-developers.com/mi-note-2/development/fix-mi-note-2-camera-blobs-t3794443
The missing reference to libadsprpc.so prevents the google camera (and any other non system app) from accessing the Snapdragon 821's hexagon DSP. The reference is needed for apps to offload processing to the DSP and the google camera tries to use it for HDR background processing. It should make the app and the phone a lot more stable and responsive even when taking consecutive shots.
Changelog​
[v3] In version 3 I started replacing both libmmcamera_imx318.so and libmmcamera_imx318_semco.so as well, with the same fixes. I'm assuming these files are for the different possible CMOS our phones can have (sony, semco or primax).
[v4] In Version 4 I also replace libmmcamera_imx268.so and libmmcamera_imx268_sunny.so. These Front Camera files were also fixed and no longer crash the app when switching to and from Portrait mode.
Very interesting! I'm flashing it in a moment!
Thank you for your work!
not booting up after install on miui 9.5.1.0
Keep up man. Wonderful job!
Very good progress!
I'm running the latest RR. Flashed and booted up no problem.
Just having issues with Urkill's camera:
It stops working when switching from mode to mode (modes work correctly)
Video on the back camera is wayyyy zoomed it. I think "Double stabilisation" is on. Note 2 is EIS by default, AFAIK, then, paired with the app's stabilization, it might be cropping out a lot of video real-estate. But this is just a guess.
Thanks for your work! Very happy with the progress!
Knz7777 said:
not booting up after install on miui 9.5.1.0
Click to expand...
Click to collapse
Hmm maybe miui's public.libraries file has libs that are missing from the file I'm flashing. I'll confirm that tonight.
I also forgot to mount /vendor in my installer script and that may have caused some issues. I'll also upload a fixed version later tonight.
Sorry for any headaches.
empy16 said:
Very good progress!
I'm running the latest RR. Flashed and booted up no problem.
Just having issues with Urkill's camera:
It stops working when switching from mode to mode (modes work correctly)
Video on the back camera is wayyyy zoomed it. I think "Double stabilisation" is on. Note 2 is EIS by default, AFAIK, then, paired with the app's stabilization, it might be cropping out a lot of video real-estate. But this is just a guess.
Thanks for your work! Very happy with the progress!
Click to expand...
Click to collapse
Yeah. UriKill's mod is optimized for the redmi note 4. But is still the most stable of the bunch. I've noticed things like switching to the front camera and then switching to portrait mode will crash the camera but doing it the other way around works.
The note 2 does have built in image EIS and UriKill's mod enables Google camera's stabilization on 1080p. But shouldn't be doing it in 4k and yet the image gets cropped a lot more in 4k. I need to figure out what's going on.
New version of the script is up. I forgot to mount /vendor, so it wasn't really working unless you had manually mounted /vendor before flashing it.
Give it a try again if it didn't work last time.
Knz7777 said:
not booting up after install on miui 9.5.1.0
Click to expand...
Click to collapse
Something just crossed my mind. Did you flash LazyFlasher on your miui rom?
Editing the /system partition makes miui roms unbootable unless you disable both dm-verify and forced encryption.
More info: http://en.miui.com/thread-310923-1-1.html
Portrait mode doesn't work
pasquale_kun said:
Portrait mode doesn't work
Click to expand...
Click to collapse
False. Portrait mode works perfectly for me.
empy16 said:
False. Portrait mode works perfectly for me.
Click to expand...
Click to collapse
For me no. The app crashes in front and back camera with portrait mode
Camera app also crash on mine when choosing portrait mode.
Although if I switch very fast to front cam it works.
Video doesn't work though.
I am on Pixel Exprerience if that helps.
Otherwise awesome work, looks promising. ?
pasquale_kun said:
For me no. The app crashes in front and back camera with portrait mode
Click to expand...
Click to collapse
If you had another google camera mod installed usually just uninstalling doesn't delete all data. And some mods have the camera.enable_pd and camera.enable_pd_blur flags turned on in Developer Settings.
These need be to off. Check if that's the issue.
Front camera Portrait Mode also needs the camera.gouda.front flag to be on.
Mimi Mix said:
If you had another google camera mod installed usually just uninstalling doesn't delete all data. And some mods have the camera.enable_pd and camera.enable_pd_blur flags turned on in Developer Settings.
These need be to off. Check if that's the issue.
Front camera Portrait Mode also needs the camera.gouda.front flag to be on.
Click to expand...
Click to collapse
Should all these flags be available in developer settings? Because I don't have them except for camera.gouda.front.
azngl said:
Should all these flags be available in developer settings? Because I don't have them except for camera.gouda.front.
Click to expand...
Click to collapse
Yes they should, at least in UriKill's port. It depends on the gcam mod you're using.
So can we flash it on miuipro 9.5.1.0 or will it bootloop?
---------- Post added at 04:49 PM ---------- Previous post was at 04:48 PM ----------
Mimi Mix said:
Something just crossed my mind. Did you flash LazyFlasher on your miui rom?
Editing the /system partition makes miui roms unbootable unless you disable both dm-verify and forced encryption.
More info: http://en.miui.com/thread-310923-1-1.html
Click to expand...
Click to collapse
I have flashed miuipro+magisk+custom kernel
Knz7777 said:
So can we flash it on miuipro 9.5.1.0 or will it bootloop?
---------- Post added at 04:49 PM ---------- Previous post was at 04:48 PM ----------
I have flashed miuipro+magisk+custom kernel
Click to expand...
Click to collapse
It shouldn't bootloop. I don't think miuipro enforces dm-verifiy. And my mod doesn't change any important system files.
If it does bootloop, try installing LazyFlasher and see if that fixes it.
Either way, put the miuipro, kernel and magisk installation files in your internal storage before testing.
If you run into a bootloop, just reflash those 3 files, in the above order, and everything will be back as it was.
Testing is really appreciated! Thank you!
pasquale_kun said:
Portrait mode doesn't work
Click to expand...
Click to collapse
Flash the first zipfile

Custom rom

I'm currently using official stable global 10.1.3 however I'm planning to switch to custom rom. Can you suggest any custom rom that is stable for daily driver? Is the performance and battery life of custom roms holds up against stock miui?
P.s. open for all suggestions and please no hate. Thanks
Heard crDroid is good but then that depends. As of now every rom has its own issue.
itscooltime said:
Heard crDroid is good but then that depends. As of now every rom has its own issue.
Click to expand...
Click to collapse
I'm using crdroid atm but the only problem I'm facing is the camera. It's their any stable camera you can suggest?
therealMarcGeneson said:
I'm using crdroid atm but the only problem I'm facing is the camera. It's their any stable camera you can suggest?
Click to expand...
Click to collapse
These are some option and are also the ones I use.
-GCAM
-Camera FV-5 Lite
-Open Camera
-A Better Camera
-MIUI Camera Port
Although I might switch to MIUI 9.1.X once that comes out as they have a new hide notch feature that fixes the notification issue I had with MIUI.
Also note that Pixel Experience is currently on pause as the dev doesn't actually have a POCO f1, and Syberia Rom is suspended for now. But I heard PE is actually quite stable. My reason for choosing crDroid is because its stable and has great features and it also has great signal strength.
( i like the miui port but for some reason when I am normally using the phone and my finger touches the FP reader it open the camera app)
itscooltime said:
These are some option and are also the ones I use.
-GCAM
-Camera FV-5 Lite
-Open Camera
-A Better Camera
-MIUI Camera Port
Although I might switch to MIUI 9.1.X once that comes out as they have a new hide notch feature that fixes the notification issue I had with MIUI.
Also note that Pixel Experience is currently on pause as the dev doesn't actually have a POCO f1, and Syberia Rom is suspended for now. But I heard PE is actually quite stable. My reason for choosing crDroid is because its stable and has great features and it also has great signal strength.
( i like the miui port but for some reason when I am normally using the phone and my finger touches the FP reader it open the camera app)
Click to expand...
Click to collapse
Got a miui port cam working without fp bug. I'm currently using latest nos and everything is perfect for me.
therealMarcGeneson said:
Got a miui port cam working without fp bug. I'm currently using latest nos and everything is perfect for me.
Click to expand...
Click to collapse
NOS as in Nitrogen OS?
I checked the thread for MIUI cam port and seems like there are others with the issue, can you tell me which link you used to download it?
itscooltime said:
NOS as in Nitrogen OS?
I checked the thread for MIUI cam port and seems like there are others with the issue, can you tell me which link you used to download it?
Click to expand...
Click to collapse
I tried the bleeding edge version and then boom no more fp bug
therealMarcGeneson said:
I tried the bleeding edge version and then boom no more fp bug
Click to expand...
Click to collapse
Ok thanks will check it out!

Categories

Resources