Hi there,
as you know the pictures taken with stock camera on 10.1 are rotated by 90 degrees.
So I decided to play around with some config files.
I found /etc/nvcamera.conf where one parameter is for orientation. Default for back-cam is 90
After the first modification not the taken picture was rotated, but the visible image in the camera app.
So I decided to turn the value back to 90. But after the reboot the image had not rotated back.
I restored the original file from the rom's zip, wiped cache & dalvik cache but my rotation is even broken.
Does anyone have an idea how to get this fixed?
Edit: Ok, meanwhile I reflashed the rom without wiping data. This fixed my problem.
Related
Hi everyone, three days ago i updated my Galaxy Nexus to the latest 4.2 version, from the stock 4.2 (the one without december in the people app).
Yesterday i started to realize some weird behaviors with overall apps, and here are some of them:
. Câmera app : Photo is taken, but can't visualize it
. Galery app : Shows ammount of photos in each album, but all the thumbnails are solid gray, and no photo can be selected for visualization
. Swiftkey Keyboard : Keeps raising error related to "Dynamic Language Packs" (since swiftkey stores the dynamic packs in the sdcard/internal storage, this might be another access issue)
. All apps that use camera activity : Camera is loaded but once i took the photo, it does not return to the app, and the camera app keeps open. No photo is returned to the app that invoked the camera aswell
. Dropbox : Can't export to internal storage any file, sometimes it manages to finally "read" the internal storage and show me directories structure, and sometimes it doesn't. In both situations, file "fails to export".
This seems a really weird behavior to me, and i thought that it might be a "Permission" issue, so i got in recovery mode and fixed permissions, but nothing got solved.
Is there any other step i might take before having to actually try a full wipe / factory reset ?
Having to reinstall / reconfigure all the apps is a pain in the butt, and since i can't backup them with titanium because of the internal storage issue, i would have to do it "manually".
By the way : Play store can update and download apps with no problem at all, so this is not a hardware issue for sure.
Try this wipe cache via recovery and dalvik cache and then flash latest root.
This should work.
manumanfred said:
Try this wipe cache via recovery and dalvik cache and then flash latest root.
This should work.
Click to expand...
Click to collapse
Wiping cache and Dalvik Cache will not erase all my internal storage right ?
EDIT: Wiping Cache and Dalvik have not worked
Weird Issue:
After booting up into recovery mode, and try to Install .ZIP from sdcard, the CMW does not actually find any other folder in my sdcard than some weird ones like "0", "odb" and "legacy".
What are those folders ?
Why it does not sees the other folders ?
marcelloLins said:
Weird Issue:
After booting up into recovery mode, and try to Install .ZIP from sdcard, the CMW does not actually find any other folder in my sdcard than some weird ones like "0", "odb" and "legacy".
What are those folders ?
Why it does not sees the other folders ?
Click to expand...
Click to collapse
Nevermind, i just reinstalled the Factory Stock 4.2 Android and updated to 4.2.1 OTA
Then i rooted it and everything is ok now.
So this is the weirdest thing ever, somehow i lost the option to crop the wallpapers and now my wallpapers do not scroll, the weird part in it beying that not ever after a backup restore from TWRP i get the function back.
This all appened yesterday when i was trying differente wallpapers and then i wanted to return to my "default" one, which i downloaded and setup since day one, and then i just had an option to set wallpaper and not crop it anymore.
I'm really lost here guys, here is the list of my tryed and failed attempts to correct the problem.
- Delet the cache and data from every wallpaperish app that i could see
- Restore factory defaults and use my normal google account
- Restore defaults and setup without a google account
- Restore backup from TWRP
This last one should have keeped the option as i had it by the time of the backup, but dosen't
OK so i'm stupid (insert facepalm), it seems kitkat does not give the crop option anymore
Just saw an article on kitkat that says it inteligently disables and enable scrolling
But can anyone explain how this "inteligent" thingy works
Hey! I have an annoying problem with camera & photos on my OP3...
Camera launches fine but when I take a photo its not saved. If I try the Google Camera it says error while trying to snap a photo. Same issues on both OxygenOS and CM13.
Solved it once by formatting the whole internal memory (factory wipe didnt help), but now the bug is back again without reason - it worked earlier today but not now anymore?!?!? :S
The thing is, I really don't wanna format and set all things up all over again... Restoring a backup doesn't help... its like its another "external" thing thats broken.
I tried looking over permissions and clearing app data and what not... all the basic stuff is already tested out without progress!
Usually solve most stuff myself but this is just wierd. Anyone else had this problem? Solution? :angel: :good:
SOLVED: By doing a full backup in TWRP (system, data, boot) then copying it to PC. Then format data, copy back the backup from PC and restore it in TWRP. Voila, now it works by restoring the exact same backup where taking photos didn't work before. So its definently something else, which is solved by formatting everything on the phone!
I've had the same issue on my OnePlus 3 running stock OxygenOS (3.2.1).
I managed to resolve it by clearing the data on the camera app, which can be done by opening the Settings and going to the Apps list. Select the Camera app and click on the Storage information which then gives you the option to 'Clear Data'. This in effect resets the Camera app and seems to resolve the issue.
Hi, first of all, I apologise for my english, I'm not very good at it, but I'll try to write the best I can.
I'm posting this because I'm having troubles with the rear camera in my Lenovo Vibe K5 plus running LineageOS 14.1-20170515-NIGHTLY-A6020. Last week i've used the camera a lot, and then suddenly some photos started to appear half-black (bottom half), and others just can't be opened. I've backuped all the SD card (with photo files in it) and then format it with FAT32 filesystem, but then I've realized that the trouble was with the camera app, and after wipe dalvik and cache and erase the app data, I've decided to format the phone storage and make a clean install of LineageOS 14.1-20170515-NIGHTLY-A6020 (before I was using AOSP-extended in his last version). Lineage OS works better than AOSP-extended in my phone, but the camera doesn't open, it just show a black screen with the capture button, and sometimes shows image for a few seconds and then freezes... A very few times it shows the image properly and works just right, and even I can take some pictures, but if I close the camera app and I open it again, the trouble comes back.
This problem occurs also in every app that uses camera, like Facebook Messenger or WhatsApp.
Any idea? I've erase app data, erase system cache, wipe dalvik, installed Google camera and nothing works for me
Hey Guys,
Few weeks ago my camera started giving the "cant connect to camera" error and couldnt use the camera. Sometimes it did work but then crashed again.
- I tried force stop of the camera app and clearing the app data and cache, no effect.
- Next i went to TWRP and cleared cache/dalvik, no effect.
- Then tried updating to a newer xiaomi.eu MIUI Weekly ROM, no effect.
- Now i went to TWRP and deleted everything except Cust (so i deleted dalvik/ART cache,System, Data, Internal Storage, Cache).
Afterwards installed the latest 7.8.24 weekly and after installing cleared cache/dalvik. After booting for the first time again the camera error. Weird thing, i just installed Whatsapp again, when i use the camera i see a frozen screen so it gets an image and i can switch to front camera that is working correctly.
Does anybody have other ideas or is it unfortunately an hardware error?