Anyone have a fix for the Snapchat-issue?
As far as I'm aware, this is a CM 10.1 issue.
And by the "Snapchat-issue" I mean that if you go into snapchat and try to use the camera everything is fine. Then if you go into the list over your recieved\sent snaps, then back to the camera again; it gets 0.1 FPS. Impossible to use it.
Currently I'm using stock over CM solely due to this reason.
And yes, I have tried several versions of different ROMs with Android 4.2.2;
Official CM 10.1, FXP 225\226, Avatar based off CM10.1, you name it.
Also have tried to remove the app completely and reinstalling it ofcourse.
So far no luck except changing back to stock ROM.
Then it works just fine.
The frontal camera is still awful ofcourse, but this is Sony's fault
I had that problem as well, and if I remember correctly, in the very short amount of time I was on CM (i.e. One day, switched back due to the terrible battery life), I figured that you can just go into developer options and enable hardware overlays or force gpu rendering (one of those two) and it'd work fine. However, that just leads to even more battery drain :/
Tapatalked from my Xperia V
Related
Hi everyone-
Unfortunately I'm new to these forums so I can't post to the developer forums myself (even though I'm an android developer in my 9-5), I just wanted to let people know my experience with the lastest FXP 216 ROM.
Firstly; 4.2.2 is a lot better at 4.1.2, especially when it comes to UI interactions - Project butter really works very well in this release of android, a lot of the garbage collector/kernel have been optimised, and you do get a better battery life as a result - I'm able to get a full day out of my Xperia Z without having to turn STAMINA mode on (of course... Stamina mode doesn't exist in FXP/AOKP).
In FXP 216, almost everything works as you expect it - Wifi, camera, auto screen brightness, FM Radio, most things are just flawless. I've only found three problems - One major (depending on your use).
1) GPS just doesn't work for all apps. Google Maps works fine but Runkeeper, and GPS Test fail to get a lock. I've tried Faster Fix to no avail. Definitely seems like a problem with the type of hardware - i.e. Google Maps works because it doesn't require such a perfect lock as Runkeeper. I suspect this is a problem with GLONASS support but it would merely be speculation.
2) And this is minor one for me - Headset buttons don't work - i.e. you can't play/pause/skip music with them.
3) FXP 216 has an "interesting" issue where it won't pick up UK phone networks without having to play with some of the settings. Play with the settings a couple of times, reboot a couple of times, and all comes good. Strangely the Xperia AOKP nightly doesn't have this problem.
But the GPS is a killer problem for me as I use Runkeeper every couple of days, so back to a rooted stock for me. I'll definitely keep my eye on FXP, and I might (if I find myself suddenly un-lazy on a Sunday) file a bug with them or Cyanogen alerting them to the GPS issues.
Anyway, I just wanted to put that out there seeing as I can't reply on the ROM boards as I'm a n00b and all.
-Soen
I've had this major problem for like a year now. Basically most third party camera apps just freeze after taking image. The program itself won't freeze but the part where you see the image. I can still use the cameras UI and if I go to some menu and come back, camera starts working again. I also found out that this doesn't occur in GB roms at all, only ics and newer. I asked from a Finnish tech forum about this issue and many people with same custom rom and phone didn't have this issue at all. I have installed over 30 roms and every time done full wipe so it shouldn't be the problem.
This hasn't been huge problem until now, because I've been satisfied enough with AOSP camera, but now with coming of CM10.2 roms I really would like to use new Focal app, but I can't because of this issue.
Is there any fix for this?
Khallerz said:
I've had this major problem for like a year now. Basically most third party camera apps just freeze after taking image. The program itself won't freeze but the part where you see the image. I can still use the cameras UI and if I go to some menu and come back, camera starts working again. I also found out that this doesn't occur in GB roms at all, only ics and newer. I asked from a Finnish tech forum about this issue and many people with same custom rom and phone didn't have this issue at all. I have installed over 30 roms and every time done full wipe so it shouldn't be the problem.
This hasn't been huge problem until now, because I've been satisfied enough with AOSP camera, but now with coming of CM10.2 roms I really would like to use new Focal app, but I can't because of this issue.
Is there any fix for this?
Click to expand...
Click to collapse
if you want stable camera you need to switch back to stock. :crying:
No solution jet for 4.0 and above.
Focal is acutally in an buggy state, so it will take a little time before we can use it ...
Khallerz said:
I've had this major problem for like a year now. Basically most third party camera apps just freeze after taking image. The program itself won't freeze but the part where you see the image. I can still use the cameras UI and if I go to some menu and come back, camera starts working again. I also found out that this doesn't occur in GB roms at all, only ics and newer. I asked from a Finnish tech forum about this issue and many people with same custom rom and phone didn't have this issue at all. I have installed over 30 roms and every time done full wipe so it shouldn't be the problem.
This hasn't been huge problem until now, because I've been satisfied enough with AOSP camera, but now with coming of CM10.2 roms I really would like to use new Focal app, but I can't because of this issue.
Is there any fix for this?
Click to expand...
Click to collapse
Dear all,
it is my first try to run cyanogenmod (10.1 Rel 7) on my SGS+. But when using it, I immediately found plenty of issues:
- Navigation is only partially working. After a while the maps starts jumping around and dark semi transparent overlay sections appear so that one cannot see the full map. In the forum I found the hint to deactivate Dithering. Done. Only little improvement.
- Alarm clock is not working when the phone is turned off.
- Screen goes off after dialing a number (workaround: lift phone to the ear and lower it back down -> screen is on again).
- No FM radio app (in comparison to the stock rom).
- Skype video is still upside down (as with stock rom).
My colleagues were very enthusiastic about cyanogen mod. In contrast, I haven't really detected the advantages. Are the developpers still working on the issues? Is there anything I can do to support you guys?
To answer your queries:
-Navigation- use the bug reporting method on the CM10.1 forums and submit it as a bug report either in the S CM10.1 thread or on JIRA. More details are given in the CM10.1 thread OP.
-This feature doesn't work even on stock. Its not a bug, and its not just CM10.1. MIUI allows this apparently however.
-This is normal, not a bug either. When you call someone the screen goes off because you're going to lift it to your ear anyway. The 'workaround' is actually the proximity sensor, and a similar thing happens on stock roms. The only solution to this is to press a button when the screen initially turns off.
-FM Radio isn't included in CM builds by default, as the API needed for it needs some intense changes made to it. There's Spirit FM if you want to run the risk. Check out the thread for more information.
-Skype on CM10.x is a known issue
Try CM10.2 and see if that helps the first issue, if not, report it using the methods in the CM threads. Otherwise everything else is as normal/known.
Sent from my GT-P7510 using Tapatalk HD
Irrespective of a few bugs there are definitely a number of advantages to using CM.
Have you noticed how smooth CM10.1 is? For me it's smoother than stock. Definitely a plus.
The pre-installed applications are more polished/work better and you actually have control over them. Don't like one? You can remove it. Unlike stock where you are stuck with a lot of junk (unless you have rooted your phone).
Bugfixes! We're no longer stuck with a 2 year old version of an OS for which we don't receive any bugfixes.
Customizability. CM gives you a lot more features to have your phone just the way you want it.
Overclocking and undervolting.
Not everyone had this problem, but my phone took > 5 minutes to get a GPS fix on stock. It takes < 10 seconds on CM.
And that's just what I came up with in a few minutes. Yes, there will be a few bugs and features which you think are weird (like the screen turning off when you make a call) but you'll find that on any piece of software. If you personally feel CM is a downgrade then it's your right to think so and go back to stock ROM. That doesn't mean the average xda-user is going to agree with you though.
(I think there are also a few ROMs based on the stock 2.3.6 versions, but since I've never used them I wouldn't know which ones are worth trying.)
Hallo,
I am sorry, to post it here, but I cannot post in the related forums below 10 posts.
So I had 4.1.5 and it was great. I flashed 4.2.3 now and it was great until after pretty much one day, when it becomes slow, had the same issues with 4.2.2 (becomes slow after a day until reboot or downgrade to 4.1.5) where I downgraded again, but it is not possible anymore without resetting the launcher3 due to some changes.
It will crash repeatedly.
Any help?
Kind regards
neox
I've been using CM based Mackay ROM for a long time now, updating to every new version as they have been released, and have not experienced anything like what you are describing.
Also, you should have really posted in the Mackay ROM thread...
Sent from my GT-I9000 using Tapatalk
@neox456! I am not sure I understand your problem fully. I have been using the same ROM since it came out for Kit Kat but never had a problem such as yours.
Could it be the no. of apps you have in your phone ? Or maybe because you aren't using low mem option (which was a feature of Kit Kat)?
It'd be good if you could explain your issues a bit briefly.
neox456 said:
Hallo,
I am sorry, to post it here, but I cannot post in the related forums below 10 posts.
So I had 4.1.5 and it was great. I flashed 4.2.3 now and it was great until after pretty much one day, when it becomes slow, had the same issues with 4.2.2 (becomes slow after a day until reboot or downgrade to 4.1.5) where I downgraded again, but it is not possible anymore without resetting the launcher3 due to some changes.
It will crash repeatedly.
Any help?
Kind regards
neox
Click to expand...
Click to collapse
Did you install CM10.2 (stable) or CM11 before Mackay 4.2.3? This increases your partition giving you better performance and is recommended for KK roms. Try again with 3 wipes plus Format System first, then the CM11, 3 wipes and format again then the Mackay Rom. If you get into trouble, go back to GB 2.3.6 with ODIN like you did when you first rooted your phone and back up from there. Hope it works for you.
The difference was between 4.1.5 and 4.2.2/3. But I played around a little and the main difference was, that KSM was on with the later ones and not with 4.1.5 so I am pretty sure that slowed my device down after a while.
I'll try 4.2.3 without KSM now and see if it won't slow down.
I cannot answer on the official Mackay-Thread until I reached 10 posts!
neither can I yet...
Naaah, it did not really help...
But I guess it is the KitKat slow downs... it is not as horrible as 4.3, but still far from well usable.
neox456 said:
Naaah, it did not really help...
But I guess it is the KitKat slow downs... it is not as horrible as 4.3, but still far from well usable.
Click to expand...
Click to collapse
Very strange.. I went all the way back to GB 2.3.6 then CM 10.2 (or 11) then SlimKat and it works really well with no FC or lags. (well maybe say max 2 second delay opening Whatsapp but I can live with that. Plus they all seem to have a 1 or 2 second delay when a call comes in for the screen to register.
Well... I am not sure... Maybe it is too many apps. At least they are not constanlty crashing like in JB4.3.
What about waking up the phone for you? Do you have a 2 seconds delay there, too? Well I sometimes have a more like 10-15 seconds delay. I press the power button and nothing happens and after a while you notice the phone is ready, because the LEDs are glowing and funnily you can already unlock it, although the screen does not show anything yet...
Well and sometimes it is only a few seconds...
I have always used CM or Mackay-CM... not sure, whether the other ROM will make such a big difference...
I had lags with CM in ICS so I went to Liquid smooth by aways .
http://forum.xda-developers.com/showthread.php?t=2223729
I like that one, no problems opening apps or answering phone call. Pkus he uses semaphore and the Nova Launcher which has a nice look and feel. Pluis customisable.
Then after to SlimKat, (after increasing partition using the CM11) which works pretty good. I will flash the mackay rom or the omni this weekend to see how it behaves in comparison.
I am down to CM9 (still Mackay) now and happy with it. :angel:
Some features got lost, but I am happy, because in general it is way more useable.
I'm using a Z3 compact with CM12.1, that means unlocked bootloader and no more warranty. All of sudden, the main/back camera has stopped working. It is black, OSD still working, front camera still working, other camera apps don't make a difference.
I don't know if that is a problem of some recent CM nightly or something else. Browsing the web I get the idea that this symptom also appears on stock firmware, and it seems that nobody has yet found a solution (neither factory reset nor hardware replacement of camera help).
My question:
Has somebody else this problem, is it CM related?
Is there a solution other than complete phone replacement?
Is there some logfile I might consult to find out if the camera HW should be replaced? I don't want to disassemble the phone only to find out that the camera still does not work.
Thanks!
Must be a software problem related to the nightlies unstableness.
Try flashing a stock firmware to see if it gets fixed.
I'd rather avoid going back to stock. Reverting to a previous CM nightly (from a time when the camera definitely worked) did not help.
Do you have any reports of CM nightlies problems with the camera? I'd love to hear that, because it would mean that I don't have hardware problems. However, searching the web I only found many reports of the camera suddenly stopping to work, but nothing that this is related with recent CM nightlies.
But if it's a Hardware problem, there should be a logfile somewhere, or?
just did trial and error on the same problem with the black camera for 2h
i did however not install CM to cause this
I have a custom debloated rom, which worked fine.
I had to switch phones so i did a TW recovery backup.
Changed the filename on the new phone so it is found when restoring.
Restored. Everything works well, except the camera app.
When i wipe from the systems menu i lose all my data but the camera app works again.
But of course i need my data exactly the way i had it backed up.
Tried all kinds of things around the camera app, backing and restoring with and without kernel, always the same.
Back camera stays black.
This is similar to other reports I found in the web: The hardware works (which means replacing the sensor is of no use), but somehow it is no longer accessible. I tried different hw info apps, which all report the back camera with all specs and no problems, but no camera app is able to get it to work. I flashed several new CM nigthlies since, it doesn't help
I don't really know how to read logs (with 3CToolbox), however this line caught my attention. Maybe somebody here can interpret it:
07:45:48.427 caladbolg( 301)
9530027 cald_parammgr_generic.c (4299) 301 E [PRM] Fail: camera eeprom status
Since my Kernel debugging skills are also not existent i simply factory reset it and transferred my data with titanium backup.
Everything works fine now.
So my advise is to stop wasting your time with it too, just go back to working software
Unfortunately reverting to stock firmware did not repair my camera. Afraid I have some hardware defect
No resolution to this problem it seems