Database Develop

moto x 2013 xt1052 camera issue

motorola x xt1052 camera clarity wrost after flashing to cm 12.1 , gapps r stopped working,

malli8043 said:
motorola x xt1052 camera clarity wrost after flashing to cm 12.1 , gapps r stopped working,
Click to expand...
Click to collapse
To use Stock camera, you've to be in Stock ROM.
May be you'll need to check and flash another set of Gapps or wipe cache

@malli8043 hi, I'm having the same issues with the camera crashing on and on. I've been trying to change settings, cleared cashe, cleaned up dalvik, but ended up getting the error after a while. I installed a different rom (from Lineage 6.1 to Mokee) But after the optimization of the applications it stops working. The problem is that the front camera only works on, but the back camera has some issues with. I opened a discussion on this but no one is answering.

dritank said:
@malli8043 hi, I'm having the same issues with the camera crashing on and on. I've been trying to change settings, cleared cashe, cleaned up dalvik, but ended up getting the error after a while. I installed a different rom (from Lineage 6.1 to Mokee) But after the optimization of the applications it stops working. The problem is that the front camera only works on, but the back camera has some issues with. I opened a discussion on this but no one is answering.
Click to expand...
Click to collapse
No one is answering...without offence, dude, your cross posting is kinda spam, and will lead you to nowhere! Let's say, more honesty, that you already got your answer, but maybe you didn't like it. For example, I personally adviced you to erase everything in your phone and perform a fully clean flash... Your problem doesn't exist on board the other moto x, do you understand it? So, no one could give you an answer about the how and why you experience such issue. Erase everything, also internal memory, then flash rom + gapps! Good luck

Hi @stefanowall, I didn't get any answer and I'm still waiting for one. I did twice a full clean flash, install the rom, install gapps(nano or pico) but it didn't work. Actually it stops working after the app updates, when it does the optimization of them, I did erase xposed framework, greenify, and all that was suspected in interfering. But the problem still persist. I think it is a binary that gets corrupted along with something else, or is a conflict of camera permission, because I don't understand why the camera settings are changed and only the front camera works, that's why I posted the pictures of the camera settings. The only solution I found was that I flashed a Motorola camera from Lolipop version and after that both cameras were working surprisingly. So I'm testing it now and will let you know if this works. But still I think that there is a conflict or a something like that...
---------- Post added at 05:53 AM ---------- Previous post was at 05:52 AM ----------
Hi @stefanowall, I didn't get any answer and I'm still waiting for one. I did twice a full clean flash, install the rom, install gapps(nano or pico) but it didn't work. Actually it stops working after the app updates, when it does the optimization of them, I did erase xposed framework, greenify, and all that was suspected in interfering. But the problem still persist. I think it is a binary that gets corrupted along with something else, or is a conflict of camera permission, because I don't understand why the camera settings are changed and only the front camera works, that's why I posted the pictures of the camera settings. The only solution I found was that I flashed a Motorola camera from Lolipop version and after that both cameras were working surprisingly. So I'm testing it now and will let you know if this works. But still I think that there is a conflict or a something like that...

[Ask][Troubleshooting] Magisk Makes the ROM Super Laggy

What I did:
- Wipe all (clean install).
- Flash latest Official MoKee ROM (Nougat).
- Flash latest GApps.
- Flash latest Magisk.
- Reboot.
After finished the Wizard Setup and before doing anything, my phone got very laggy, open menu, open Settings, etc.
Then I clean install again like the steps above, but this time using SuperSU, and everything normal, so I stick with SuperSU for now.
My questions, what is the cause of the lags? Is it known bug in Magisk, the ROM itself (not compatible), or GApps? I also heard ResurrectionRemix had the same problem after installing Magisk, so many people revert back to SuperSU.
Thanks,

I have Resurrectionremix and Magisk 14.3
No any lag on my phone.
Tapatalk - Xiaomi Mi6

You need to list what modules you're using.

BIGWORM said:
You need to list what modules you're using.
Click to expand...
Click to collapse
I only flash the ROM, GApps and Magisk without any additional flashable ZIPs.

Honestly that doesn't sound like Magisk. I've ran Magisk on literally probably 20 ROMs between Angler and Pixel XL and never Magisk caused lag... Did u try a different rom? Just curious, or maybe it's some incompatibility with that specific rom and magisk

yung40oz84 said:
Honestly that doesn't sound like Magisk. I've ran Magisk on literally probably 20 ROMs between Angler and Pixel XL and never Magisk caused lag... Did u try a different rom? Just curious, or maybe it's some incompatibility with that specific rom and magisk
Click to expand...
Click to collapse
I tried several ROMs that based on LOS and all same, maybe it's caused by LOS base that used in those ROMs. And since you say so, probably it's not an issue in Magisk, but the ROM itself.
I'll try Magisk again later when some ROM's builds available for my device.
-
I think my questions has been answered (it's appear not issue in Magisk side) and this thread can be closed.

irfanfadilah said:
I tried several ROMs that based on LOS and all same, maybe it's caused by LOS base that used in those ROMs. And since you say so, probably it's not an issue in Magisk, but the ROM itself.
I'll try Magisk again later when some ROM's builds available for my device.
-
I think my questions has been answered (it's appear not issue in Magisk side) and this thread can be closed.
Click to expand...
Click to collapse
Ya I was gonna say cause I use all AOSP and CAF based

I had this issue with Lineage 14.1 and AEX before.
Now I don't have this issue anymore.
What I do is:
- Wipe everything
- Install ROM
- Install GApps
- Reboot and finish Setup Wizard (then I install some or all apps that I use)
- Reboot to TWRP and flash Magisk.
The first time I reboot after flashing Magisk it's still a little slower than normal. Then I reboot one more time and never faced this anymore.
Now I do this everytime I make a clean install and everytime it works.

Danilo-Sanchez said:
I had this issue with Lineage 14.1 and AEX before.
Now I don't have this issue anymore.
What I do is:
- Wipe everything
- Install ROM
- Install GApps
- Reboot and finish Setup Wizard (then I install some or all apps that I use)
- Reboot to TWRP and flash Magisk.
The first time I reboot after flashing Magisk it's still a little slower than normal. Then I reboot one more time and never faced this anymore.
Now I do this everytime I make a clean install and everytime it works.
Click to expand...
Click to collapse
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks

irfanfadilah said:
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks
Click to expand...
Click to collapse
Yes.
Try it and let me know if this also fix the problem for you.

Yes, Magisk is the thing that's causing lag and stutter. My Nexus 5X is also barely responding to any commands if I flash Magisk right after a ROM clean installation. If you flash only the ROM, then you can finish setting up the device without much stutter or hiccups in performance.
If, after a clean installation (or after installing Magisk - didn't try this though) you use the phone without Magisk for a bit, maybe install some apps, etc, you'll see that everything is nice and smooth.
Now, you can check the smoothness without Magisk and with Magisk installed like this:
- Without Magisk: Update 'Google App' to the latest version then try to open the side panel from the latest Pixel Launcher. You'll see that opening/closing it is nice and smooth, and scrolling up and down is also smooth.
- With Magisk installed (without using any modules): The moment the phone turns on, at first, things might seem OK. First wait for the phone to settle down after the reboot for a few minutes. Then try opening the side panel. You'll see some stutter while dragging that panel to the right, maybe not huge, but it's there. Scrolling up and down is also stuttery. At first I thought it was because of the latest version of Google App, or the new cards design, or even the images in there, but that wasn't the issue. Then I thought maybe the launcher was somehow influencing Google App's performance, but that wasn't either the issue.
AND it was like I completely forgot about SuperSU and didn't even think of trying it in order to see how things were.
I even rebased my ROM in the hope that I'd find the culprit, and still nothing. Nothing weird appeared in any logs, which was so annoying. And a few hours ago, after finishing up cleaning up my sources (for other reasons), I compiled a fresh new build, and it crossed my mind to try SuperSU, just for the hell of it, and BOOM ! No more lag and stutter. The phone is snappy and responsive again.
I'll try to contact the dude behind Magisk and see what he has to say, or leave a comment in his thread.
The thing is, those with more recent phones, like the Pixels or any other phones than are more powerful than mine, might not notice what I described above, but there should be some stutter there, no matter how small, maybe in other scenarios as well.
The thing is, Magisk kinda slowly took the place of Xposed, at least that's what it looks like to me, and I personally don't like that but that's how things are, I suppose. All those modules or at least one of them WILL cause issues sooner or later, just like on Xposed.
But in the end, yes, it's Magisk what's destroying your phone's performance and nothing else. So if you're not really in the need to have your phone pass SafetyNet, and want to have your phone snappy and lag-free, use SuperSU, at least until things get better on Magisk.

dragos281993 said:
Yes, Magisk is the thing that's causing lag and stutter. My Nexus 5X is also barely responding to any commands if I flash Magisk right after a ROM clean installation. If you flash only the ROM, then you can finish setting up the device without much stutter or hiccups in performance.
If, after a clean installation (or after installing Magisk - didn't try this though) you use the phone without Magisk for a bit, maybe install some apps, etc, you'll see that everything is nice and smooth.
Now, you can check the smoothness without Magisk and with Magisk installed like this:
- Without Magisk: Update 'Google App' to the latest version then try to open the side panel from the latest Pixel Launcher. You'll see that opening/closing it is nice and smooth, and scrolling up and down is also smooth.
- With Magisk installed (without using any modules): The moment the phone turns on, at first, things might seem OK. First wait for the phone to settle down after the reboot for a few minutes. Then try opening the side panel. You'll see some stutter while dragging that panel to the right, maybe not huge, but it's there. Scrolling up and down is also stuttery. At first I thought it was because of the latest version of Google App, or the new cards design, or even the images in there, but that wasn't the issue. Then I thought maybe the launcher was somehow influencing Google App's performance, but that wasn't either the issue.
AND it was like I completely forgot about SuperSU and didn't even think of trying it in order to see how things were.
I even rebased my ROM in the hope that I'd find the culprit, and still nothing. Nothing weird appeared in any logs, which was so annoying. And a few hours ago, after finishing up cleaning up my sources (for other reasons), I compiled a fresh new build, and it crossed my mind to try SuperSU, just for the hell of it, and BOOM ! No more lag and stutter. The phone is snappy and responsive again.
I'll try to contact the dude behind Magisk and see what he has to say, or leave a comment in his thread.
The thing is, those with more recent phones, like the Pixels or any other phones than are more powerful than mine, might not notice what I described above, but there should be some stutter there, no matter how small, maybe in other scenarios as well.
The thing is, Magisk kinda slowly took the place of Xposed, at least that's what it looks like to me, and I personally don't like that but that's how things are, I suppose. All those modules or at least one of them WILL cause issues sooner or later, just like on Xposed.
But in the end, yes, it's Magisk what's destroying your phone's performance and nothing else. So if you're not really in the need to have your phone pass SafetyNet, and want to have your phone snappy and lag-free, use SuperSU, at least until things get better on Magisk.
Click to expand...
Click to collapse
I'm glad I'm not the only one experienced this issue, that's mean it's not entirely user fault. Maybe you're right, on more high-spec phones they won't really notice the lags/stutters.
Looking forward to the news/updates regarding this issue.

irfanfadilah said:
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks
Click to expand...
Click to collapse
I don't mean to necrobump, but did it work? I have an LG G4 (H815) and suffered the same issue. Like you, I only flashed magisk right after flashing the ROM (LG nougat).
Thanks

Camandros said:
I don't mean to necrobump, but did it work? I have an LG G4 (H815) and suffered the same issue. Like you, I only flashed magisk right after flashing the ROM (LG nougat).
Thanks
Click to expand...
Click to collapse
I haven't got the chance to try it.
Currently I'm using SuperSU to root my device.

I tried installing magisk on my currently in use ROM, i.e., a long time after flashing it, and although it got less laggy, there still was a heavy lag impact in some applications. Maybe it has less impact on lineage or on lighter ROMs? I'm using official LG nougat.

I'm using Mi 6 in Xiaomi.eu rom
YES, magisk causing laggy.

Same here
Mi5, tested on MIUI 9 and 10
Without Magisk everything was great and after flashing Magisk, the phone got laggy!

I have the same problem with my LG G6

interesting, first I thought that emmc will be broken. because the problem is the same (lag). but after i replace emmc, all back is fine. I just think emmc is broken because it is often flashing rom.

ChessPiece said:
What I did:
- Wipe all (clean install).
- Flash latest Official MoKee ROM (Nougat).
- Flash latest GApps.
- Flash latest Magisk.
- Reboot.
After finished the Wizard Setup and before doing anything, my phone got very laggy, open menu, open Settings, etc.
Then I clean install again like the steps above, but this time using SuperSU, and everything normal, so I stick with SuperSU for now.
My questions, what is the cause of the lags? Is it known bug in Magisk, the ROM itself (not compatible), or GApps? I also heard ResurrectionRemix had the same problem after installing Magisk, so many people revert back to SuperSU.
Thanks,
Click to expand...
Click to collapse
what magisk version 16.0 or beta? magisk can't make the phone lag but kernel or something in ROM may interrupt try to change kernel or flash the lastest Gapps

Front camera doesn't popup in custom ROM (only Cosmic OS tested)

Hi guys
I'm quite new to the K20 Pro. Last night, my friend asked me to install some custom AOSP ROMs for him. I chose Cosmic OS first since it just got updated recently. Installed and booted up just fine, BUT here's the problem :
- First boot up and installed GCam : front camera pops up fine
- Installed 81Hz mod and Immensity kernel : still pops up fine
- Some Magisk modules like NFS, Viper4android v2.7, Google dialer framework : still pops up fine
- Substratum app and apply Liv Dark theme : front camera STUCKS after a reboot, can't even use the Motor Control app to get it pop up again
So I thought the problem lies in the Substratum and the theme but uninstalling those didn't help, EVEN clean flashing the ROM again. Changing to MIUI 11 EU rom, front camera works fine again.
If anyone knows whether the problem is in the ROM itself or conflict with the modules/theme/mod/kernel or it's a common issues in custom AOSP ROMs then please let me know asap, I'll be very appreciated.
THANK YOU !!!!!!

S.N.A.P said:
Hi guys
I'm quite new to the K20 Pro. Last night, my friend asked me to install some custom AOSP ROMs for him. I chose Cosmic OS first since it just got updated recently. Installed and booted up just fine, BUT here's the problem :
- First boot up and installed GCam : front camera pops up fine
- Installed 81Hz mod and Immensity kernel : still pops up fine
- Some Magisk modules like NFS, Viper4android v2.7, Google dialer framework : still pops up fine
- Substratum app and apply Liv Dark theme : front camera STUCKS after a reboot, can't even use the Motor Control app to get it pop up again
So I thought the problem lies in the Substratum and the theme but uninstalling those didn't help, EVEN clean flashing the ROM again. Changing to MIUI 11 EU rom, front camera works fine again.
If anyone knows whether the problem is in the ROM itself or conflict with the modules/theme/mod/kernel or it's a common issues in custom AOSP ROMs then please let me know asap, I'll be very appreciated.
THANK YOU !!!!!!
Click to expand...
Click to collapse
Front Camera just works fine except you don't mess with the sensors while downgrading. For a flawless experience either stick to Q or P.
Sent from my Redmi K20 Pro using Tapatalk

Sukhi said:
Front Camera just works fine except you don't mess with the sensors while downgrading. For a flawless experience either stick to Q or P.
Click to expand...
Click to collapse
well the custom ROM is Pie-based and I'm pretty sure I didn't do anything related to sensors
anyway thanks for your answer

S.N.A.P said:
well the custom ROM is Pie-based and I'm pretty sure I didn't do anything related to sensors
anyway thanks for your answer
Click to expand...
Click to collapse
Jumping b/w Q and P roms does break the sensors.
Sent from my Redmi K20 Pro using Tapatalk

S.N.A.P said:
Hi guys
I'm quite new to the K20 Pro. Last night, my friend asked me to install some custom AOSP ROMs for him. I chose Cosmic OS first since it just got updated recently. Installed and booted up just fine, BUT here's the problem :
- First boot up and installed GCam : front camera pops up fine
- Installed 81Hz mod and Immensity kernel : still pops up fine
- Some Magisk modules like NFS, Viper4android v2.7, Google dialer framework : still pops up fine
- Substratum app and apply Liv Dark theme : front camera STUCKS after a reboot, can't even use the Motor Control app to get it pop up again
So I thought the problem lies in the Substratum and the theme but uninstalling those didn't help, EVEN clean flashing the ROM again. Changing to MIUI 11 EU rom, front camera works fine again.
If anyone knows whether the problem is in the ROM itself or conflict with the modules/theme/mod/kernel or it's a common issues in custom AOSP ROMs then please let me know asap, I'll be very appreciated.
THANK YOU !!!!!!
Click to expand...
Click to collapse
Hey, how good is the fingerprint sensor with this rom? And also can you try watching a YouTube
To see how stable the audio is.

Sukhi said:
Jumping b/w Q and P roms does break the sensors.
Click to expand...
Click to collapse
oh
I was from MIUI china stable 10.3.17 Pie, so it's just Pie-MIUI to Pie-AOSP
Does it break the sensors too ???

m1chb3ltr3 said:
Hey, how good is the fingerprint sensor with this rom? And also can you try watching a YouTube
To see how stable the audio is.
Click to expand...
Click to collapse
audio works as it should, completely normal
fingerprint works fine too

S.N.A.P said:
oh
I was from MIUI china stable 10.3.17 Pie, so it's just Pie-MIUI to Pie-AOSP
Does it break the sensors too ???
Click to expand...
Click to collapse
Nope ! I thought you came back from MIUI 11. If you're jumping within Pie, it's not a problem. There should be no other reason why the Cam won't Pop-up other than the Camera sensor fail. Did you wipe Vendor?.
Sent from my Mi A3 using Tapatalk

Sukhi said:
Nope ! I thought you came back from MIUI 11. If you're jumping within Pie, it's not a problem. There should be no other reason why the Cam won't Pop-up other than the Camera sensor fail. Did you wipe Vendor?.
Click to expand...
Click to collapse
(S.N.A.P here, just my other account)
Yes, I did wiped Vendor
At first I used TWRP 3.3.1-15 by Mauro, 5 wipe and flashing Vendor 10.3.17 + Rom + Gapps but failed at the vendor so I switched to LRTeam TWRP. This time only 4 wipe since there's no Vendor option. Flashing was ok and the phone booted up
And then everything went like the first post

75_TZ said:
(S.N.A.P here, just my other account)
Yes, I did wiped Vendor
At first I used TWRP 3.3.1-15 by Mauro, 5 wipe and flashing Vendor 10.3.17 + Rom + Gapps but failed at the vendor so I switched to LRTeam TWRP. This time only 4 wipe since there's no Vendor option. Flashing was ok and the phone booted up
And then everything went like the first post
Click to expand...
Click to collapse
Never ever touch vendor again. It's the set of drivers for your device. Go back flash the complete MIUI stock Pie rom and then continue with the Cosmic flash w/o any system/vendor wipes. Data,Cache,Dalvik wipes should be more than enough.
Sent from my Redmi K20 Pro using Tapatalk

Sukhi said:
Never ever touch vendor again. It's the set of drivers for your device. Go back flash the complete MIUI stock Pie rom and then continue with the Cosmic flash w/o any system/vendor wipes. Data,Cache,Dalvik wipes should be more than enough.
Click to expand...
Click to collapse
OH
My fault
Just check back some tutorials of some custom ROMs, only wipe system, data, cache, dalvik cache, no Vendor wipe needed
No wonder when I flashed MIUI 11 EU rom, popup cam works fine again
Thank you so much
I'll try again and see if it works

75_TZ said:
OH
My fault
Just check back some tutorials of some custom ROMs, only wipe system, data, cache, dalvik cache, no Vendor wipe needed
No wonder when I flashed MIUI 11 EU rom, popup cam works fine again
Thank you so much
I'll try again and see if it works
Click to expand...
Click to collapse
People are just copy pasting tutorials from old devices which have dedicated System, Recovery, Vendor etc partions and and wiping one of these won't crash the device. K20P is a system as a root device and wiping system wipes of everything except vendor. Moreover, wiping System isn't required at all as most of the roms these days have System wipe scripts already baked in and would wipe the system irrespective of whether you wipe it or not. There's no real added advantage of wiping system before you flash the rom. System wipes should only be done occassionally whenever you have really messed up something or getting FC's.
Sent from my Redmi K20 Pro using Tapatalk

Sukhi said:
People are just copy pasting tutorials from old devices which have dedicated System, Recovery, Vendor etc partions and and wiping one of these won't crash the device. K20P is a system as a root device and wiping system wipes of everything except vendor. Moreover, wiping System isn't required at all as most of the roms these days have System wipe scripts already baked in and would wipe the system irrespective of whether you wipe it or not. There's no real added advantage of wiping system before you flash the rom. System wipes should only be done occassionally whenever you have really messed up something or getting FC's.
Click to expand...
Click to collapse
OH :fingers-crossed:
That's a great tip
I'm very appreciated
Thank you :highfive:

Camera not working anymore, and it may have something to do with Magisk

I just realized my camera isn't functioning anymore.
Each timeI try to open the stock camera app, the app will now say "can't connect to camera" and then quits. Other apps that make use of the camera will also complain about a problem with it.
Coincidentally, I upgraded magisk (canary build) to version ce7cb1ee (20706) last night. And I was using my camera just yesterday with no problems at all.
So I strongly suspect it may have something to do with the latest magisk build. Anything I can do to revert it back to the previous version?
(also note to self: do a full TWRP backup, and backup my own data too using methods like tar, next time before flashing new magisk)

seemebreakthis said:
I just realized my camera isn't functioning anymore.
Each timeI try to open the stock camera app, the app will now say "can't connect to camera" and then quits. Other apps that make use of the camera will also complain about a problem with it.
Coincidentally, I upgraded magisk (canary build) to version ce7cb1ee (20706) last night. And I was using my camera just yesterday with no problems at all.
So I strongly suspect it may have something to do with the latest magisk build. Anything I can do to revert it back to the previous version?
(also note to self: do a full TWRP backup, and backup my own data too using methods like tar, next time before flashing new magisk)
Click to expand...
Click to collapse
Try to flash magisk 20.3 via twrp and delete cache and dalvik

Maybe stupid question, but have you tried to reset your phone? Xd
Have you any camera mods in Magisk modules, like Camera 2 API enabler or sth?

SzczufFun said:
Maybe stupid question, but have you tried to reset your phone? Xd
Have you any camera mods in Magisk modules, like Camera 2 API enabler or sth?
Click to expand...
Click to collapse
Thanks for replying !
I am now all but certain the latest Magisk canary build (edit: version 20306) as a compatibility bug with MIUI 10.
Ended up flashing to MIUI 11, installed Magisk, no issues.
Just for the sake of testing, I used MiFlash to do a fresh install of MIUI10, then installed Magisk. Camera became useless. Flashed previous version of Magisk canary. Things went back to normal.
Because of this I spent hours upgrading to MIUI 11 (so it gave me extra motivation to finally made the move), figuring out what to debloat, and did a slow and arduous operation of moving data slowly back to the system (so I can have a clean fresh MIUI11 with empty data partition and empty storage to begin with). So all is still good i guess.

Pop-up camera won't go down, after using GCAM.

I downloaded the latest Urnyx Gcam build. I am currently on LineageOS 17.1
I went to take a selfie video. The app froze and the front pop-up camera refuses to close itself.
- I used the stock camera app to bring down the front camera, it doesn't work.
- Restarted the phone couple of times
- Factory reset
- Change ROMs
- Used the motor.apk to manually bring down the camera, doesn't work too. It says "camera alread retracted" Link: https://forum.xda-developers.com/attachment.php?attachmentid=4930537&d=1579448949
I already tried flashing an AOSP based ROM, still didnt work.
- Dropping down the phone to my bed, doesn't work
Please I am in need of help. I can't put my phone on the pocket.

Not sure if it helps, I had the same issue on lineage yesterday and for some reason this app was able to retract it.
https://m.apkpure.com/popup-camera-no-sound/com.sjh.popupcamera

harry_turtle said:
Not sure if it helps, I had the same issue on lineage yesterday and for some reason this app was able to retract it.
https://m.apkpure.com/popup-camera-no-sound/com.sjh.popupcamera
Click to expand...
Click to collapse
Thanks for the reply. I am on Lineage when this happened too.
That app you sent me didn't work tho.

Fixed the issue by formatting data and flashed back to EU ROM MIUI 12.0.3.0