Hi, after installing the latest update, the camera in my X10 does not work. After returning to 2.1 also does not work. After root and uploading the software from Wolf, the camera still does not work. Maybe someone has a fix for the camera? Do you have any suggestions?
radzix said:
Hi, after installing the latest update, the camera in my X10 does not work. After returning to 2.1 also does not work. After root and uploading the software from Wolf, the camera still does not work. Maybe someone has a fix for the camera? Do you have any suggestions?
Click to expand...
Click to collapse
What exactly do you mean "does not work"?
Does it FC? Does it freeze? Any other error message?
Can you post a log?
When I try to use the camera, the phone says that the camera is not available , other apps like camera 360 or viginette also doesn't work, it says An error has occurred ..etc. How i can make log?
radzix said:
When I try to use the camera, the phone says that the camera is not available , other apps like camera 360 or viginette also doesn't work, it says An error has occurred ..etc. How i can make log?
Click to expand...
Click to collapse
Install LogCat from the Market!
Then post the log here.
I suspect you have broken camera drivers.
Some people had the same issue when updating from 1.6->2.1
and if I remember correctly Bin4ry had made a fix.
Hi, Bin4ry fix didn't help im my case. Also after dwongrade to 2.1 it wasn't help me. Any other suggestion? Maybe any 1 have right camcorder driver, that i could replace?
don't know if this is helpfull or if it will work but have you tried repairing your phone with pc companion?
Problem
I think i have the same problem. But i havent downgraded from 2.3.3.
My mobile was in service until today and some hours playing with 2.3.3 i tested the camera and it didnt work.
I have also reseted the phone in SEUS.
It can be beacuse of bad service when they switched the motherboard but i post an log here if you can see if its the drivers,
Sorry for my crappy english!
08-09 18:11:05.349 W/IInputConnectionWrapper(2147): showStatusIcon on inactive InputConnection
08-09 18:11:05.639 D/dalvikvm(1323): GC_CONCURRENT freed 198K, 49% free 3358K/6471K, external 10111K/12159K, paused 2ms+4ms
08-09 18:11:07.819 I/ActivityManager(1151): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10100000 cmp=com.sonyericsson.android.camera/.CameraActivity bnds=[238,431][351,589] } from pid 1151
08-09 18:11:10.911 E/SemcCameraApp(1980): SemcCamera:Open camera device failed: exit.
08-09 18:11:10.969 E/SkLayout_wtle(1980): layout error:106 width:0 ellipsizedWidth:0
08-09 18:11:10.969 E/SkLayout_wtle(1980): layout error:106 width:0 ellipsizedWidth:0
08-09 18:11:10.969 E/SkLayout_wtle(1980): layout error:106 width:0 ellipsizedWidth:0
08-09 18:11:10.969 E/SkLayout_wtle(1980): layout error:106 width:0 ellipsizedWidth:0
08-09 18:11:10.989 E/SkLayout_wtle(1980): layout error:106 width:0 ellipsizedWidth:0
08-09 18:11:17.189 I/InputDispatcher(1151): Dropped event because of pending overdue app switch.
08-09 18:11:17.259 I/InputDispatcher(1151): Dropping event because the pointer is not down.
08-09 18:11:17.269 D/dalvikvm(2147): GC_CONCURRENT freed 733K, 60% free 2860K/7047K, external 2224K/2778K, paused 2ms+3ms
08-09 18:11:18.093 I/ActivityManager(1151): Starting: Intent {
I have a similar problem.
When I open the camera for the first time I get Unknown Error.
After I close it and open it again it works fine.
This is my log file. Maybe someone can see what's up...
i have the same problem :S...i installed wolfs rom yesterday the camera was fine infact its good then before ...but now it keep sayin camera not available or unkown error...but camera 360 is working fine but im wondering why my default camera application is not working ...
need help plz...
I had same problem. Delete all pics and videos from your sd card and it will be sorted.
Sent from my X10i using XDA App
curtis1982 said:
I had same problem. Delete all pics and videos from your sd card and it will be sorted.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
ahan so then Can i put all my pics and videoz back ?...then camera will be oki ?
curtis1982 said:
I had same problem. Delete all pics and videos from your sd card and it will be sorted.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
ahan,If i will delete all pics and videos then camera will be oki?...Can i copy my whole data of memory card and format memory card then restore back to it ?
Hello.can any one reply me back :s...
Sent from my X10i using XDA Premium App
Related
Hi everybody, i have a problem with my camera, the first time i open the app the scrren freezes, the second time it says "unknown mistake", and the third time it works well, but i want to know if i can use the app without open it 3 times. Also I fixed permissions but still remains with the problem.
I'm using XPERIA TW Gingerbread V3 2.3.3 with hotfix 3.1 ROM of wolfbreak
I had the same problem, i backed up my sd card and formatted hasn't been a problem since.
themoog said:
I had the same problem, i backed up my sd card and formatted hasn't been a problem since.
Click to expand...
Click to collapse
how did you format your SD, in your PC or in the cellphone in Xrecovery????
FerGT said:
how did you format your SD, in your PC or in the cellphone in Xrecovery????
Click to expand...
Click to collapse
better with phone
yep with phone
thanks everybody, I solved it, the problem was that I was using no media app.
FerGT said:
thanks everybody, I solved it, the problem was that I was using no media app.
Click to expand...
Click to collapse
Exactly what do you mean by "using no media app"? I'm having the same issue with my x10
has anyone installed vignette or any other good camera app which is as good as vignette which is working properly with this ROM ? whenever i try to open vignette, it FC`s and then not even the stock camera works. only after reboot does the stock camera come back to life. i tried fixing permissions but that didnt help. re-flashed and still no luck. any ideas ?
thanks
ok, i think i have found the reason for that. the circle battery mod is probably the one causing the problems. i didnt flash the apk and now both cameras work perfectly without any issues.
Hi all,
I've probably messed up something with my phone and now I can't call: when I try to call a number a black screen appears and it stops there. The phone still works for few minutes and then it freezes and I have to remove the battery.
My phone is a Samsung Galaxy S2 with CyanogenMod 10.1.
I think this problem is related with some app that overwrote something in the phone, maybe after an update that I did 10 days ago. Is there a way to restore the caller application? Maybe installing again the GApps? I don't exactly know what procedure to follow, could somebody help me, please?
Thanks in advance.
First off, I'd just go into Settings / Applications / All and wipe the cache and data of the Dialer and reboot. See if that will help. Then you can try reinstalling the rom and Gapps while just wiping cache and dalvik cache. If that doesn't do it, then wiping everything, including /system might be in order. Make sure you back up your contacts, apps, messages, etc that you want first in case you end up needing to reset completely.
es0tericcha0s said:
First off, I'd just go into Settings / Applications / All and wipe the cache and data of the Dialer and reboot. See if that will help.
Click to expand...
Click to collapse
I really didn't think of that. Thanks!! I'll give it a try :fingers-crossed:
es0tericcha0s said:
Then you can try reinstalling the rom and Gapps while just wiping cache and dalvik cache. If that doesn't do it, then wiping everything, including /system might be in order. Make sure you back up your contacts, apps, messages, etc that you want first in case you end up needing to reset completely.
Click to expand...
Click to collapse
I would like to avoid this... I have both a full nandroid backup and a titanum backup, but it will take some time to reset and check all the phone. I was looking for a solution that let me understand the problem and deal with it the next time.
Anyway... Thanks! :highfive:
EDIT: Find the dialer in cyanogenmod is not trivial
To figure out what the issue is you would need to run a logcat and then recreate the problem.
I've tried to wipe the data of the dialer without luck
I use Contact+ as contact manager and it has its builtin dialer. Usually, after I press the button "call" another application starts, from which I can see the call options, the speakerphone, terminate call button, ... And now it's always black. For this reason I'm not sure what really is the broken app.
es0tericcha0s said:
To figure out what the issue is you would need to run a logcat and then recreate the problem.
Click to expand...
Click to collapse
I've attached the log taken with logcat, it starts when I make the call.
A little update: while trying to make another call I was able to talk and hear the other person, but with the screen always black. After a while I received a message "Phone activity is not responding"
Well, I'm definitely not an expert in reading logcats (trying to get better...) but I see some stuff that seems important... I'm wondering though, have you removed the original Dialer/Phone app and / or are you using only the other app to dial - the one with your 3rd part Contact app manager? From browsing the logcats it seems like it's trying to connect with another app and something is missing and causing everything to fail. This is more of an educated guess at this point, but if that is the case, it might narrow down the issue a bit more. Curious : Why not make a nandroid backup and flash an updated version of the rom? I know there is a slightly newer stable version of CM for the S2...
Oh yea, which S2, by the way? There are quite a few variants of the S2 and some of them are so different that there is no reason they should even be called the S2 (different screens, bodies, processors, etc) so depending which one, there might be a better rom for it.
es0tericcha0s said:
Well, I'm definitely not an expert in reading logcats (trying to get better...) but I see some stuff that seems important... I'm wondering though, have you removed the original Dialer/Phone app and / or are you using only the other app to dial - the one with your 3rd part Contact app manager?
Click to expand...
Click to collapse
I changed dialer a long time ago, I remember I didn't remove the original one. Also searching in the app list I can see an app that looks like the original dialer. I use only the Contact+ dialer but I think it eventually uses the original one.
es0tericcha0s said:
From browsing the logcats it seems like it's trying to connect with another app and something is missing and causing everything to fail. This is more of an educated guess at this point, but if that is the case, it might narrow down the issue a bit more.
Click to expand...
Click to collapse
What lines are you talking about? The only interesting lines I can see are:
W/ActivityManager( 4082): Launch timeout has expired, giving up wake lock!
W/ActivityManager( 4082): Activity idle timeout for ActivityRecord{42229420 u0 com.android.phone/.SipCallOptionHandler}
They look related to the black screen after the call is started.
There is another interesting line
W/dalvikvm(21477): VFY: unable to resolve static method 1599: Landroid/provider/Telephony$Sms;.getDefaultSmsPackage (Landroid/content/ContextLjava/lang/String;
It can be due to a broken davlik cache after I've updated the apps. I've just cleaned the dalvik cache, I'll try if it works later.
I can also see a problem with the RIL:
E/TinyALSA-Audio RIL Interface( 2356): ril_connect() failed
I changed the RIL about one month ago with the app GetRIL (I am aware I should keep the CM one). I don't remember I've had any problems one month ago because I noticed the dialer not working only few days ago.
es0tericcha0s said:
Curious : Why not make a nandroid backup and flash an updated version of the rom? I know there is a slightly newer stable version of CM for the S2...
Click to expand...
Click to collapse
I want to fix the problem to avoid it next time. I prefer not to reset my phone every time there is only 1 thing that doesn't work!
Anyway I have a clean and fully functional rom backup taken about 2 months ago. If everything fails I'll go for that. It's CM 10.1.3 Stable. Or maybe for the new nightly build of CM11, as you suggested! :good:
es0tericcha0s said:
Oh yea, which S2, by the way? There are quite a few variants of the S2 and some of them are so different that there is no reason they should even be called the S2 (different screens, bodies, processors, etc) so depending which one, there might be a better rom for it.
Click to expand...
Click to collapse
System settings -> About phone
Model: GT-I9100
CPU: ARMv7 Processor rev1 (v7l)
Memory: 804 MB
CyanogenMod version: 10.1.3-i9100
Kernel version: 3.10.0-R93-Siyah-Dorimanx-V9.39-JB-SGII-PWR-CORE
And thanks for the help :highfive:
[0m[38;5;40mI/ActivityManager( 4082): Start proc com.contapps.android:ContactActionProcess for broadcast com.contapps.android/.utils.ContactActionReceiver: pid=21477 uid=10006 gids={50006, 3003, 1015, 1028}
[0m[38;5;75mD/Yamaha-MC1N2-Audio( 2356): yamaha_mc1n2_audio_modem_start()
[0m[38;5;75mD/Yamaha-MC1N2-Audio( 2356): yamaha_mc1n2_audio_route_start()
[0m[38;5;75mD/Yamaha-MC1N2-Audio( 2356): (yamaha_mc1n2_audio_params_route_find): device = 2, direction = 2
[0m[38;5;166mW/Trace (21477): error opening trace file: No such file or directory (2)
[0m[38;5;40mI/dalvikvm(21477): Could not find method android.provider.Telephony$Sms.getDefaultSmsPackage, referenced from method com.contapps.android.utils.GlobalUtils.a
[0m[38;5;166mW/dalvikvm(21477): VFY: unable to resolve static method 1599: Landroid/provider/Telephony$Sms;.getDefaultSmsPackage (Landroid/content/ContextLjava/lang/String;
[0m[38;5;75mD/dalvikvm(21477): VFY: replacing opcode 0x71 at 0x00b6
[0m[38;5;40mI/Crashlytics(21477): Initializing Crashlytics 1.1.10.12
[0m[38;5;75mD/TinyALSA-Audio RIL Interface( 2356): audio_ril_interface_open(0x400e9b50, 2, 0x40ffdc54)
[0m[38;5;75mD/TinyALSA-Audio RIL Interface( 2356): audio_ril_interface_set_route(2)
[0m[38;5;196mE/TinyALSA-Audio RIL Interface( 2356): ril_connect() failed
[0m[38;5;75mD/TinyALSA-Audio RIL Interface( 2356): audio_ril_interface_set_voice_volume(2, 1.000000)
[0m[38;5;40mI/dalvikvm(21477): Could not find method android.provider.Telephony$Sms.getDefaultSmsPackage, referenced from method com.contapps.android.ContactsPlusBaseSettings.b
[0m[38;5;166mW/dalvikvm(21477): VFY: unable to resolve static method 1599: Landroid/provider/Telephony$Sms;.getDefaultSmsPackage (Landroid/content/ContextLjava/lang/String;
[0m[38;5;75mD/dalvikvm(21477): VFY: replacing opcode 0x71 at 0x000a
[0m[38;5;40mI/dalvikvm(21477): Could not find method android.graphics.Bitmap.getAllocationByteCount, referenced from method com.contapps.android.utils.ImageCache.a
[0m[38;5;166mW/dalvikvm(21477): VFY: unable to resolve virtual method 927: Landroid/graphics/Bitmap;.getAllocationByteCount ()I
[0m[38;5;75mD/dalvikvm(21477): VFY: replacing opcode 0x6e at 0x001c
[0m[38;5;75mD/ImageCache(21477): Memory cache created (size = 4915)
[0m[38;5;166mW/ContApps(21477): Setting CallReceiver: false
[0m[38;5;40mI/ActivityManager( 4082): No longer want com.skype.raider (pid 21120): empty #17
That stretch right there seems like it is the culprit. Like it's trying to connect to the main dialer action of the phone and fails.
Could not find method android.provider.Telephony$Sms.getDefaultSmsPackage
That shows up twice in connection to the Contact+ app. Then it errors trying to pull something for the bitmap graphics which would probably explain the black screen part. The RIL part might be important as well, but I think the first thing to try might be something other than Contact+...?
As far as roms, I guess 10.1.3 was the last stable one for that. Thought it would have 10.2 If you get adventuresome, you should check out Slim. It's well supported with some nice features but not one of the everything but the kitchen sink type things.
es0tericcha0s said:
That stretch right there seems like it is the culprit. Like it's trying to connect to the main dialer action of the phone and fails.
Could not find method android.provider.Telephony$Sms.getDefaultSmsPackage
That shows up twice in connection to the Contact+ app. Then it errors trying to pull something for the bitmap graphics which would probably explain the black screen part. The RIL part might be important as well, but I think the first thing to try might be something other than Contact+...?
As far as roms, I guess 10.1.3 was the last stable one for that. Thought it would have 10.2 If you get adventuresome, you should check out Slim. It's well supported with some nice features but not one of the everything but the kitchen sink type things.
Click to expand...
Click to collapse
Cleaning the dalvik cache and installing a new dialer () didn't work. About the dialer... well I think the problem is not the dialer: I can dial! The problem is the application that manages the active call. And I don't know how it's called or I would try to clean or reinstall it! Can it be an activity contained in the app called com.android.phone?
Slim looks nice I can try it after I solve this problem!
My first instinct is to blame Contacts+.
I solved the problem, it was the RIL. I changed it to try different settings and in the end I was able to put back the original one.
Many thanks anyway!
So since installing CM12, I've been running into both "Unfortunately camera has stopped", and "Cannot connect to camera" errors. It's strange because when I flash a fresh install after wiping cache/dalvik/data/system...everything, then boot up, the camera works fine. It's not until a day or two later that I realize it just breaks itself and stops working.
This has happened multiple times now, and what I have to do to temporarily fix is wipe everything (including internal storage and sd card...yes on purpose), and then sideload CM12 and GApps back onto the phone. Once I do this and boot up, again, the camera is working fine...but sure enough a day or two later *poof*, it commits suicide...
This is the runtime exception that is being thrown:
Code:
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.camera2/com.android.camera.CameraActivity}: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at android.app.ActivityThread.performLaunchActivity(A ctivityThread.java:2329)
at android.app.ActivityThread.handleLaunchActivity(Ac tivityThread.java:2391)
at android.app.ActivityThread.access$900(ActivityThre ad.java:147)
at android.app.ActivityThread$H.handleMessage(Activit yThread.java:1296)
at android.os.Handler.dispatchMessage(Handler.java:10 2)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.jav a:5256)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCa ller.run(ZygoteInit.java:898)
at com.android.internal.os.ZygoteInit.main(ZygoteInit .java:693)
Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at com.android.camera.one.OneCameraManager.isCamera2S upported(OneCameraManager.java:107)
at com.android.camera.one.OneCameraManager.create(One CameraManager.java:84)
at com.android.camera.one.OneCameraManager.get(OneCam eraManager.java:71)
at com.android.camera.CameraActivity.onCreate(CameraA ctivity.java:1352)
at android.app.Activity.performCreate(Activity.java:5 933)
at android.app.Instrumentation.callActivityOnCreate(I nstrumentation.java:1105)
at android.app.ActivityThread.performLaunchActivity(A ctivityThread.java:2282)
... 10 more
I seem to be the only one facing this issue, and google is no help whatsoever. It can't possibly be hardware related, because each time I wipe internal storage and adb sideload the rom back on, the camera works great...EVERY TIME...and I've done it about 5 times now, but it's getting old, tedious, and inconvenient... Can anyone offer any insight at all, or does anyone have *any* idea what could be causing this?? Thanks in advance, and I appreciate all help...
Are you on the latest TWRP and the latest firmware? People have had that issue and that was the culprit. Read the first few pages of the CM12 thread santod made in the development section.
Sent from my HTC6500LVW using XDA Free mobile app
Hey guys!
I received a phone Alcatel 7040t which got just 4GB of internal storage. It is rooted.
I'm successfully able to link 16GB memory card by creating 2 partitions.
Everything is working fine. PlayStore works fine. I've installed many apps.
Install location is set to auto.
The problem now is that WhatsApp and Facebook is not installing and giving error 910. When try APK file, it shows out of space.
Solution:
Install Apps2SD PRO app.
Select Broken App Cleaner option.
Tick Select All option and it will scan data.
Clear it and restart the phone.
Hope problem will be solved!!!
Thanks to Tribes11 for the idea.
If have any problem, please share.
I'm having the same issue after updating to Magisk 18.1 and having issues, needed to go back to Magisk 18.0 but after that, I can't install apps from play store anymore.
Now I don't know what to do, my bigger games and some apps are on 2nd partition.
I'm using MIUI 9 on Redmi 4 Prime 32gb.
Hi my friend I've managed to get past the error, I can assure you that everything can be done within app2sd. You need to clear the unbound apps data and then restart. It's a script run through the app itself.
Tribes11 said:
Hi my friend I've managed to get past the error, I can assure you that everything can be done within app2sd. You need to clear the unbound apps data and then restart. It's a script run through the app itself.
Click to expand...
Click to collapse
Wowwww!!!!:laugh: The magic happens...
I have Apps2SD Pro app.. There's an option Broken App Cleaner.. It found 72 Mb data and cleared it. Then phone restarts.. Voila....!!!! Problem solved.
Apps are now installing fine. Thanks:good:
That's the power of community..:highfive:
fahadboss said:
Wowwww!!!!:laugh: The magic happens...
I have Apps2SD Pro app.. There's an option Broken App Cleaner.. It found 72 Mb data and cleared it. Then phone restarts.. Voila....!!!! Problem solved.
Apps are now installing fine. Thanks:good:
That's the power of community..:highfive:
Click to expand...
Click to collapse
Glad to hear you could fix it! I'm happy for you! Best regards!
Whenever i open MIUI gallery app i creates a weird file on sd card root storage. It creates new file each time gallery app is launched. Anybody else facing this weird issue ? It just stacks up hundreds of files on sd card. Anyway to resolve this issue ? Help would be appreciated. I'm using curtana.
Thanks in advance
talalahmad said:
Whenever i open MIUI gallery app i creates a weird file on sd card root storage. It creates new file each time gallery app is launched. Anybody else facing this weird issue ? It just stacks up hundreds of files on sd card. Anyway to resolve this issue ? Help would be appreciated. I'm using curtana.
Thanks in advance
Click to expand...
Click to collapse
I have joyeuse running the EEA v11.0.4.0.QJZEUXM rom and I have exactly the same happening. I have noticed that the files all seem to be 0 bytes (empty) and they seem to be created daily including days when I don't use the gallery app. I have moved them all to "trash" which doesn't seem to affect the gallery app. I'll try few tests to see if I can identify when it creates them.
eemNote3 said:
I have joyeuse running the EEA v11.0.4.0.QJZEUXM rom and I have exactly the same happening. I have noticed that the files all seem to be 0 bytes (empty) and they seem to be created daily including days when I don't use the gallery app. I have moved them all to "trash" which doesn't seem to affect the gallery app. I'll try few tests to see if I can identify when it creates them.
Click to expand...
Click to collapse
It seems like some kind of cache file. i noticed that when i delete these files gallery takes a bit longer to load thumbnails of pictures. i also tried different apks of miui gallery but issue remains there
Hi there, is there any optoin to avoid MIUI Gallery to create these 0Byte files? I am on 11.0.5(QJZMIXM) and the 0Byte files are stored in the SD Card.
dc_01 said:
Hi there, is there any optoin to avoid MIUI Gallery to create these 0Byte files? I am on 11.0.5(QJZMIXM) and the 0Byte files are stored in the SD Card.
Click to expand...
Click to collapse
I'm on version 11.0.10.0 still the issue remains there and so far the only solution i've found is to stop using stock galley it just creates new 0byte file on every time you open the app. MIUI Gallery app isn't well optimized if you try to move a picture within sd card from one folder to other it moves it to internal storage for no reason. Stock gallery app is just a mess.
talalahmad said:
... Stock gallery app is just a mess.
Click to expand...
Click to collapse
yes, I agree. The only reason I remain with the MIUI Gallery, if you make a screenshot and want to share it e.g. in WhatsApp, this action will fail, if MIUI Gallery is disabled or deleted. Unfortunately I could not "motivate" Google Photos to do this job, thus MIUI Gallery remains.
what is ****ing miui gallery messing with sd card .its really annoying .multiple file just creating with zero size.i format phone twice to check issue solve but nothing happen . still my sd card have trashing file that really annoyed in RN9 pro.hope they fix
EonJone said:
what is ****ing miui gallery messing with sd card .its really annoying .multiple file just creating with zero size.i format phone twice to check issue solve but nothing happen . still my sd card have trashing file that really annoyed in RN9 pro.hope they fix
Click to expand...
Click to collapse
Hoping they'll fix these issues in miui v12 otherwise we'll have to void our warranty and go for custom roms. This android skin is literally trash
I'm using INDIA Rom: v11.0.8 and same problem. How to fix it?
Same problem here :crying: rn9p global
I'm experiencing the same problem. (rn9s global, MIUI 11.0.10.0)
When I launch the MIUI Gallery app, it creates *.miuigallery (garbage file) on my sd card.
Yes me too
Several files with larg number on sdcard crated by miuigallery
Xiaomi must fix this
Redmi note 9s miui11
zakaria9 said:
Yes me too
Several files with larg number on sdcard crated by miuigallery
Xiaomi must fix this
Redmi note 9s miui11
Click to expand...
Click to collapse
They are just treating their users as beta testers miui is full of small bugs and not polished enough and so far there's no fix for this issue.
Did you guys reported to the services and feedback section in settings?
You should. Otherwise it'll never be fixed.
Sent from my Redmi Note 9 Pro using XDA Labs
whisper1101 said:
Did you guys reported to the services and feedback section in settings?
You should. Otherwise it'll never be fixed.
Sent from my Redmi Note 9 Pro using XDA Labs
Click to expand...
Click to collapse
i reported the issue there too. The device even got 2 to 3 updates after that but issue still remains there. I'm hoping it'll be fixed in MIUI 12 update.
whisper1101 said:
Did you guys reported to the services and feedback section in settings?
You should. Otherwise it'll never be fixed.
Sent from my Redmi Note 9 Pro using XDA Labs
Click to expand...
Click to collapse
sure, already done, but no reply so far. See attached pic.
dc_01 said:
sure, already done, but no reply so far. See attached pic.
Click to expand...
Click to collapse
They do not respond or reply anyway. But hopefully noting the bugs and doing something about it.
Sent from my Redmi Note 9 Pro using XDA Labs
for a previous message i received a reply, so they can if they want
I found a solution.
They already fixed it on the latest version of the gallery but it seems that its not yet available via the system apps updater.
A workaround for this is to download it via a 3rd-party apk site (I use apkmirror). The one I installed is v2.2.16.19 and that fixed the issue for me
Thanks....this worked for me
laconix00 said:
I found a solution.
They already fixed it on the latest version of the gallery but it seems that its not yet available via the system apps updater.
A workaround for this is to download it via a 3rd-party apk site (I use apkmirror). The one I installed is v2.2.16.19 and that fixed the issue for me
Click to expand...
Click to collapse
Thanks....this worked for me