Basically, every AOSP 4.4.x rom I have tried (I prefer AOSP) on my device has had camera problems. Unfortunately, I came from a device with a buggy camera already and just cannot deal with camera bugs anymore, so I'm stuck on stock 4.4.2 for now.
My camera bugs are namely that snapchat cannot take videos with the front camera (the one facing my face) and that it vertically stretches any front camera images. I haven't tested many other apps, but I am sure that if problems are popping up in snapchat, they will pop up elsewhere in apps like instagram, etc. Moreover, the camera is very laggy on snapchat. These problems are nonexistent on stock 4.4.2.
Aside from that, Open Camera was the only camera app I could find that wouldn't break the camera until a reboot, which was a tolerable problem because I like that app nonetheless.
I've tried CM11 M12, Liquid Smooth, and Gummy Rom. All have some sort of snapchat camera problem. On Gummy, I couldn't even get the stock camera app to take videos without breaking the camera.
I'm sort of desperate for a solution because I LOVED the battery life and performance I was achieving on CM11. But I just cannot deal with the snapchat camera bugs. I'll take everything working the way it should be over a performance and battery increase.
Does anyone have any ideas on how to fix this? ANY help or advice is appreciated!
Will try bumping this a time or two.
Anyone know if these problems are still present in Lollipop? From what I've read they are, at least the typical CM camera crashes are, so I assume the stretching in apps like snapchat also persists.
WHib96 said:
Will try bumping this a time or two.
Anyone know if these problems are still present in Lollipop? From what I've read they are, at least the typical CM camera crashes are, so I assume the stretching in apps like snapchat also persists.
Click to expand...
Click to collapse
From what I have read in the CM12.1 LP thread by Matrixzone the issue has been resolved. A search of that thread should confirm or deny if that is correct.
dawgdoc said:
From what I have read in the CM12.1 LP thread by Matrixzone the issue has been resolved. A search of that thread should confirm or deny if that is correct.
Click to expand...
Click to collapse
Okay. I checked it out and things are a little unclear. Looks like the camera is pretty much working for normal stuff in the regular camera app. Instagram is reported to not be working, but there's pretty much nothing on the stretching. I may just go over to CM12.1 and try it myself.
Related
So I've searched and found a few mentions of this, but no possible hints as to why it's happening...
Most (not all) of the time, my camera view looks like there is a pink solarize filter applied. I've flipped on and off all filters, and it shows the same in my camcorder app, Camera360, RetroCamera, every app that uses my camera lens.
I am running MynWarm TwoPointTwo RLS5, and noticed it on RLS4 as well as on CM6.1.1. I am running the Netarchy SBS CFS kernel. I notice the issue when plugged in and when on battery power.
Any ideas what may be happening, and how I can fix my camera? Seems like it has to be a software issue, doesn't it?
Just curious but does it happen on both cameras? If so then it seems more likely a software issue. Was not mentioned in the OP...
budroux said:
Just curious but does it happen on both cameras? If so then it seems more likely a software issue. Was not mentioned in the OP...
Click to expand...
Click to collapse
Sorry for neglecting to mention that - the front camera is fine, the back camera is the only one that's all pink.
Of course the obvious reply would be to double check the lens to make sure it is clean and not damaged...LOL!!! I am sure you have done that. If it were me at that point I would flash the latest stock rom and kernel which has stock code and stock camera software. This would at least point to a software or actual camera problem.
My hopes would be that stock would fix it...then you could re-flash the setup you had and see if it is the culprit...my way of troubleshooting before panic...LOL!!!
I'm thinking that's what I'm going to have to do. It'll have to wait until I have just a bit more time - I'll search for a rooted RUU and stock kernel to flash - making sure I have a good nandroid of this one before I do.
pusht down to reattach the thing. the cam comes loose
Hi guys.. I finally installed jellybean on the phone, but there was some issues regarding some crucial(for me) functionalities of the phone;
Mainly the camera, It takes pictures with the green thing of course (I don't mind this one), It shoots videos with focusing and all, but it doesn't really shoot 30fps (I tried apps like lg camera and camera ics but it's all the same). There was some talk here about changing some system configuration file to make the camera shoot in 26fps, but that doesn't seem to be making any sense... Now the second thing is third party apps that use the camera, as for example camscanner that has some weird issues inside of it.. I open the program, I switch to batch mode(this one takes a lot of pictures), I take the first image which goes normally but after that all I see is what I had taken, I can take new images, but there is no preview(and no focusing). Notice that this app worked in gb, and had no problems, And that the whole range of apps that shoot multiple images has the same problem (handy scanner for example) . So did any one get around those issues... I heard that CM9 is better so can anyone confirm if camscanner is working there (the batch mode), Or maybe if someone is using a different one that doesn't have those issues ; These are really some serious drawbacks to the available custom roms, So I think they should have been at least mentioned.
Thanks in advance !
Dude you should really read what Arco said about the SGW camera in CM before claiming it´s not working that well like in GB. It´s a dirty hack to make it work at all so it will also not work well with all the camera apps out there. In CM9 its working a bit better than in CM10 but regarding smoothness and compability with other apps it´s about the same. So you are not telling us something new and everyone who is using CM9 or CM10 is also aware of this.
So if this is a big issue for you, flash back to GB and use this instead.
honeyx said:
So if this is a big issue for you, flash back to GB and use this instead.
Click to expand...
Click to collapse
Thanks for the response, I might do that ... As for now can someone confirm that camscanner is not working on CM9 as well ?
I also have the same problem with the app above in camera jb+ (Takes the first picture, freezes), and I heard that some people are using it flawlessly... So please what rom are you using ?
varexnet32 said:
Thanks for the response, I might do that ... As for now can someone confirm that camscanner is not working on CM9 as well ?
I also have the same problem with the app above in camera jb+ (Takes the first picture, freezes), and I heard that some people are using it flawlessly... So please what rom are you using ?
Click to expand...
Click to collapse
camera is working well in cm9 eol which is i'm using. spend some time reading cm9 thread and cm9 bug report thread to avoid redundant questions.
dec0der said:
camera is working well in cm9 eol which is i'm using. spend some time reading cm9 thread and cm9 bug report thread to avoid redundant questions.
Click to expand...
Click to collapse
Thanks for the response. I myself noticed that the camera even in CM10 is faster than stock, except for some issues... However someone just confirmed to me that the issue that I'm talking about here is present in cm9 too, so it seems that the camera is the same in all avaiable cyanogenmods for this phones !
Basically, every time I install ANY AOSP ROM, these problems occur:
1) Proximity sensor during a call. [This has been discussed before on this thread but I've tried everything and I couldn't get it to work. I know for a fact that it isn't hardware and IS software because the proximity sensor works fine when I use the stock ROM. It's a problem with AOSP.]
2) Snapchat front camera [Whenever I use my front camera to take a video, it freezes, and then when the video is done recording it says "video cannot be played." Again, this only happens in AOSP ROMs. Touchwiz works fine.]
I REALLY hate Touchwiz based ROMs and I want AOSP but it's not usable for me if these problems occur.
If anyone can help, that'd be awesome!
Thanks in advance.
Why don't you just avoid all these issues that will probably not get fixed since they have been in existence for quite a while. Have you ever tried a TW ROM with an Aosp theme? You get complete look and feel of Aosp. Check out this theme and see for yourself http://forum.xda-developers.com/showthread.php?t=2304251
Sent from my SGH-M919
anuderpins said:
Basically, every time I install ANY AOSP ROM, these problems occur:
1) Proximity sensor during a call. [This has been discussed before on this thread but I've tried everything and I couldn't get it to work. I know for a fact that it isn't hardware and IS software because the proximity sensor works fine when I use the stock ROM. It's a problem with AOSP.]
2) Snapchat front camera [Whenever I use my front camera to take a video, it freezes, and then when the video is done recording it says "video cannot be played." Again, this only happens in AOSP ROMs. Touchwiz works fine.]
I REALLY hate Touchwiz based ROMs and I want AOSP but it's not usable for me if these problems occur.
If anyone can help, that'd be awesome!
Thanks in advance.
Click to expand...
Click to collapse
I'm assuming that you've tried the Google Play edition ROMs? They are AOSP but offer much less customization than, say.. CM, Pac-man, etc. Lack of built-in customization options can easily be remedied though by using xposed GravityBox and other nifty modules.
lordcheeto03 said:
I'm assuming that you've tried the Google Play edition ROMs? They are AOSP but offer much less customization than, say.. CM, Pac-man, etc. Lack of built-in customization options can easily be remedied though by using xposed GravityBox and other nifty modules.
Click to expand...
Click to collapse
I have tried Google Play edition ROMs, but the customization wasn't enough for me. I'm not familiar with xposed GravityBox, but I'll check it out and I'll see what I find! What exactly does it do?
anuderpins said:
I have tried Google Play edition ROMs, but the customization wasn't enough for me. I'm not familiar with xposed GravityBox, but I'll check it out and I'll see what I find! What exactly does it do?
Click to expand...
Click to collapse
Gives you ton of customization, check it on the thread or xposed, gives you all the info you need
Sent from my SGH-M919 using Tapatalk
Hello all,
First post, sorry its a question..
The back camera on M8 is making strange pictures, if any at all (see attachment).
Front camera is working fine.
Got my M8 for 1 year now, never had problems with the camera.
mm-qcamera-daemon is running high on batt usage.
Stock camera app will most of the time open and then close again, sometimes i can make strange pictures like above.
I don't have an other camera app running
It's rooted and i'm running
InsertCoin version 3.0.8
Android 4.4.2
HTC sense v6.0
HTC SDK API 6.17
I do know there are a lot of updates from the above versions. But its running so wel all these time that i don't need a upgrade (still up to 5 days on a full batt :good
I did clear the cache from the camera app, I don't have lastpass installed.
Does anyone seen a picture like this (except from a good/bad trip)? And how did they fix it.
All input is appreciated.
Thanks, Peter.
One of two things is going on. Either the camera module has gone bad OR you dont have the correct software to run the camera or that software has gone corrupt.
I see your running a custom rom so my suggestion would be go back to complete stock and re-test. If it fails its a hardware issue.
IAmSixNine said:
One of two things is going on. Either the camera module has gone bad OR you dont have the correct software to run the camera or that software has gone corrupt.
I see your running a custom rom so my suggestion would be go back to complete stock and re-test. If it fails its a hardware issue.
Click to expand...
Click to collapse
Thanks for your answer.
Do you have any clue if the same software is used for the front and back camera? Front is working perfect so that would mean a hardware issue.
I will start with returning to stock, quickest way to see if it's hardware related.
The camera modules are different. Back has ultra pixel and front is a megapixel.
Since its easier to change software it makes sense to go back to complete stock for testing. Then if it still fails its probably hardware.
Hi everyone, I recently bought a new camera module for the Z1C to replace my old one which had dark spots all over it, scratched lense etc. However, with the new camera (supposedly an original sony part), I experience a strange brightness and distortion problem, with the former one being rather obvious from the attached pictures. Note the large brightness artifact on the right side of the picture (inverted L shape).
I had sent the module back to the camera supplier, they tested it on their Z1C and found no problems whatsoever, telling me it was a (supposedly well known) software bug in my phone. Unfortunately, I was unable to find any occurence of other users reporting this particular problem. Maybe you can help me out?
I have an unlocked bootloader, currently running on the most recent DstrikersZ1 Mod (Android 5.1.1), but have also tried wiping everything and going back to the latest Sony Stock without getting rid of the problem. Could still be an incompatibility issue in terms of camera module hardware revisions? Interestingly, the problem does not occur in CM or AOSP firmwares, suggesting indeed a Sony-related software issue. Still, I find it hard to believe that this cannot be fixed while remaining on Sony-based firmwares. I have tried to flash every single Camera Mod available (Z5 camera, Cyberian, and many more) plus trying many alternative Camera softwares from the Google Play store without any success.
Thank you all very much!
Azzip said:
Hi everyone, I recently bought a new camera module for the Z1C to replace my old one which had dark spots all over it, scratched lense etc. However, with the new camera (supposedly an original sony part), I experience a strange brightness and distortion problem, with the former one being rather obvious from the attached pictures. Note the large brightness artifact on the right side of the picture (inverted L shape).
I had sent the module back to the camera supplier, they tested it on their Z1C and found no problems whatsoever, telling me it was a (supposedly well known) software bug in my phone. Unfortunately, I was unable to find any occurence of other users reporting this particular problem. Maybe you can help me out?
I have an unlocked bootloader, currently running on the most recent DstrikersZ1 Mod (Android 5.1.1), but have also tried wiping everything and going back to the latest Sony Stock without getting rid of the problem. Could still be an incompatibility issue in terms of camera module hardware revisions? Interestingly, the problem does not occur in CM or AOSP firmwares, suggesting indeed a Sony-related software issue. Still, I find it hard to believe that this cannot be fixed while remaining on Sony-based firmwares. I have tried to flash every single Camera Mod available (Z5 camera, Cyberian, and many more) plus trying many alternative Camera softwares from the Google Play store without any success.
Thank you all very much!
Click to expand...
Click to collapse
I can see why you're bewildered. Very strange... I would initially think hw for sure, and someone sold you a bad part, but to hear that it goes away on custom ROMs is very confusing. Anyway, personally, I think I would probably send it back and get a refund, and try a different one. Whatever the problem is, that seems like the simplest first thing to try.
levone1 said:
I can see why you're bewildered. Very strange... I would initially think hw for sure, and someone sold you a bad part, but to hear that it goes away on custom ROMs is very confusing. Anyway, personally, I think I would probably send it back and get a refund, and try a different one. Whatever the problem is, that seems like the simplest first thing to try.
Click to expand...
Click to collapse
Thank you for your quick feedback and sympathy! Unfortunately, they refused to give me a refund based on the fact that they could not reproduce it on their Z1C test device. I had sent them my item and requested a refund/replacement, but they (supposedly) tested my module in detail and even sent me some pictures taken with their Z1C as proof. So now they just delivered the same camera module back to me and I'm kind of stuck with it.
Not sure why they cannot see it, given that it happens for me even on a clean Sony stock firmware. In theory, the only remaining difference between their phone and mine (HW revisions aside) would be my unlocked bootloader and with it the deleted TA partition and DRM for Bravia engine. I still have a TA backup somewhere but I'm not exactly willing to relock my bootloader and to loose TWRP. On a sidenote, the EXRxTHS functional DRM "restoration" did not help with my specific problem.
As you said, the mystery really lies in why the problem is not visibile on custom ROMs. I'd love to get a glimpse on the RAW image data from the camera because I believe that an error in post-processing causes the problem on the Sony ROM. But as far as I could see from searching, there is still no way of getting RAW image data when using a Sony firmware on Z1C, right?