Related
The point of the topic:
Post your issues found in STOCK / CM11 or post a solution.Simple as that,very productive.
I'll start with a list of bugs:
CM11 ISSUES:
-Video recording lags in reduced luminosity.
-The phone heats too much when playing/watch videos for long time and so on.
-Volume during call is too low.
-Ocasionally freezes & crashes.
-Some graphical issues when the phone freezes.
-Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
STOCK ISSUES:
-Video blinks in low light(from what I've read it focuses wrong on the light source and starts blinking).
-The proximity sensor remains on after a missed call.
-Multi touch doesn't work as well as on CM11.
-Some weird freezes during call ( the screen remains off / freezes and you can't end the call / sometimes even answer )
-Camera doesn't have as much detail as in CM11 ( if you zoom in,the image doesn't clarify).
-Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
CM11 FIXES:
-Lag in video recording can be reduced by lowering the exposure.In medium to low light " - 1 " works pretty good and in very low to low light " - 2 " .However,when you use " - 2 " ,the recorded video will be very dark.Still haven't found a solution for this.
-About heating problem,you might want to try @Shivam Kuchhal 's kernel.He reported that his phone doesn't get heat up more than normal.
-About volume during call,it's been solved partially in newer releases by editing snd_soc_msm file.However,if the value is too high,the phne volume will also be too high and the speaker will produce distorsioned sound.However,I see they found a resonable value and both,the volume during call & speaker is about fine.
-For headset buttons not working,you must edit Generic.kl file.Here's a short tutorial to help you:
Go to: system/usr/keylayout/Generic.kl and change as below
key 226 HEADSETHOOK
key 256 BUTTON_1
change to
key 226 BUTTON_1
key 256 HEADSETHOOK
STOCK FIXES:
-For proximity sensor and weird freezes during a call use this tutorial .Haven't tested it personally,but people reported it works even on latest .17 fw.
-For Mac issue [ works for cm11 as well ]
1)Restore original MAC Address
Open /data/etc/wlan_macaddr0
Copy it's content. Ex: 01:12:13:14:15:16
Open /etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
Find this line
Code:
Intf0MacAddress=000AF58989FF
Replace 000AF58989FF with the content of wlan_macaddr0, but write back to front. Ex: from 01:12:13:14:15:16, write to 161514131201. So it will look like this
Code:
Intf0MacAddress=161514131201
Save & Exit, Reboot the phone
That's all for now,continue to post bugs&fixes and most important:
HELP EACHOTHER
Marius Cristian said:
The point of the topic:
Post your issues found in STOCK / CM11 or post a solution.Simple as that,very productive.
I'll start with a list of bugs:
Click to expand...
Click to collapse
Proximity fix not working!!!
More Kitkat Bugs List:-
1. Headset buttons
2. Camera experiencing crashes randomly, sometimes cause overexposure and being unstable at flash mode
3. Black graphical glitch/scanning effect first time after you turn your screen off then on again after first restart/turning on phone.
4. Call bugs(e.g. distortion etc.)
5. Lag when using the video camera
6. battery draining faster then on stock rom. (was improved on early nightly releases....now its back again)
7. GPS not working again (for some it does...others it doesnt....again...wasnt there on first nightlies)(Mostly Happens In CM11)
8. Camera quality is much,much worse then on stock rom
9 . Phone may left hanging and screen wont turn on for several seconds...
10. Some apps are unsupported on playstore...
CM11 bugs
CM11:
1. Switch to HDR mode and within 3 snaps camera app will FC.
2. Headset buttons.. I have to manually edit that Generic.kl after every nightly update.
3. As mentioned above, graphical glitch after updates.
Some of bugs that u mentioned @David pro has been fixed by users, but device maintainer didn't merged it for some reason in official builds. So, get started:
1. These buttons can be fixed, someone(I don't remember who, Sorry) has created a modified Generic.kl. You can find that file somewhere on this forum.
2. Camera quality is medium, but videos are very poor..
3. Still exist
4. @up
5. As I said, videos are bad
6. Caused by Google Play Services, 1st method is use xposed Framework and one of its add-ons, 2nd is just disable Services from Settings>Apps(i'm using second one, because I just don't like Xposed)
7.GPS is working fine, at least for me. No fix needed
8.Yep, on stock it is better.
9.It's caused by "Black graphical glitch/scanning effect first time after you turn your screen off then on again after first restart/turning on phone."
10.Well, some of them are only for one platform or type of devices,eg. Tegra 4 games.
No heating issues noticed so far(I use my kernel obviously) and yeah the camera and video quality isn't anything worth praising. Also the hwcomposer issue happens only one time after every boot, after that its all fine.
I normally use AOSPA.
Actually,I think the cm11 camera takes better photos than stock,but it can be buggy sometimes :silly:
About GPS,it's working fine for me too.
About video camera being laggy...I think it's because our phone lacks drivers update.It's hard to believe the video camera will ever be 100% fixed.
I'm sorry I'm kinda busy those days and I don't have time to administrate this thread.I'll edit the main post as soon as I can with solution you guys posted.But it's true,there are things which can't be fixed.Until I come back, HELP EACHOTHER
an another bug with stock rom is that "camera not available "or the camera takes a long time to recover after taking a shot
chrome browser restarts the phone or makes the phone to hang
vishalaestro said:
an another bug with stock rom is that "camera not available "or the camera takes a long time to recover after taking a shot
chrome browser restarts the phone or makes the phone to hang
Click to expand...
Click to collapse
Haven't experienced those kind of issues when I used stock.Try to do a factory reset or flash the ftf again.Maybe you added some mods or apps which affected the system.
Overall,we have to admit that CM11 is blazing fast and that's why I'm still using it.I'll update the OP now with your solutions.Thanks guys and keep helping eachother.
Marius Cristian said:
Haven't experienced those kind of issues when I used stock.Try to do a factory reset or flash the ftf again.Maybe you added some mods or apps which affected the system.
Overall,we have to admit that CM11 is blazing fast and that's why I'm still using it.I'll update the OP now with your solutions.Thanks guys and keep helping eachother.
Click to expand...
Click to collapse
another BUG with the stock ROM
1)walkman app flickers in the widget lockscreen
2)poor memory management need to restart the phone daily else the phone lags like a hell
3)camera app didn't respond ,it doesn't even the focus sometimes ,clearing the app data solves this problem temporarily and i think it was not present with the .12 update ,so if anybody could extract the camera app from the .12 update similar to the phone app freeze issue the problem might be solved.
3)walkman app or any other music player makes music to stutter when the same song is played more than one time provided if the songs are stored in memory card also i know that my sdcard doesn't have any problem because it worked fine with galaxy s3.my sd card is sandisk ultra class 10 32 gb
4)battery drain heavy when wifi is switched on compared to previous android 4.1.2
note:i have not rooted my phone or modded my firmware .all i run is the apps taken from the playstore.i have done a factory reset for more than 4 times.
CM11 / Stock (using custom kernel) bug:
Wifi MAC Address is always 00:0a:f5:89:89:ff.
If there are 2 Xperia L using CM11 / Custom Kernel connected to the same wifi, both connections will be dropped.
Solution:
Restore original MAC Address
Open /data/etc/wlan_macaddr0
Copy it's content. Ex: 01:12:13:14:15:16
Open /etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
Find this line
Code:
Intf0MacAddress=000AF58989FF
Replace 000AF58989FF with the content of wlan_macaddr0, but write back to front. Ex: from 01:12:13:14:15:16, write to 161514131201. So it will look like this
Code:
Intf0MacAddress=161514131201
Save & Exit, Reboot the phone
solution for Play Services battery drain in CM11
CM11 issues
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.
chinmay1234 said:
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.
Click to expand...
Click to collapse
Nfc icon not in statusbar is on all cyanogenmod/aosp based rom
chinmay1234 said:
1. GPS Not Working
2. NFC not Working.
3. NFC icon not provided in Status bar when NFC is ON.
4. Frequent Crashes : Blue Screen on latest Nightlies 20140827.
5. Camera quality getting worse.
Click to expand...
Click to collapse
1. For many people works,for some don't.I don't understand how's possible...
2.Haven't tested it...for me it's a useless feature.
4.Well,crashes happens.However,they're not too frequent.
5.I really like the photos cm11 takes.About video...another story.Try to notice the details in the photos in comparison with stock.
I am going back to stock in order to see if I can obtain(with all the bug fixes from here) a more stable software than cm11.I'll report to you soon guys.Until then, help eachother
@underd0g
Nice fix for WiFi-Mac interference problem. :good:
Marius Cristian said:
1. For many people works,for some don't.I don't understand how's possible...
2.Haven't tested it...for me it's a useless feature.
4.Well,crashes happens.However,they're not too frequent.
5.I really like the photos cm11 takes.About video...another story.Try to notice the details in the photos in comparison with stock.
I am going back to stock in order to see if I can obtain(with all the bug fixes from here) a more stable software than cm11.I'll report to you soon guys.Until then, help eachother
Click to expand...
Click to collapse
guys please try to solve the issues with stock ROM because they are the stable ones and the bugs are easily repairable if the bugs are reached to right hands.so pls first concentrate on stock ROM
I've been playing around with 4.4 video recording..what i think is the lags occurs when we record in low lights related with the kernel..i'm testing with snapcam as its has auto flash when recording in low lights..First result is same as stock..but in snapcam it has touch to focus when recording..after touch,the recording will get a bit darker when it refocus and walla..no lags..
What i found is, the camera will automatically reduced the exposure to -1 for avoiding the lags even it is on default setting..
When moving the camera in low lights,the recording will lags again after few second..that is with continuous focus..set to normal or auto..no lags..so our stock cam using continuous focus for recording..
Back to the kernel thing..from what i see from the recording is same like this when i'm playing with cnt rom to to get wifi and overclock working.
Ok,so I went back to stock.I'm amazed by the battery life,it lasted 2 days and I used the phone a lot ( especially for calls ).
However,after using the fix for freezes during call and so on,I still have experienced this morning an issue.While I was talking to someone,someone else called and the phone was beeping but the screen was frozen.I had to press the power button to lock the device then unlock it to get the screen to show who's calling and to give me the possibility to answer the call.What do you think I should do?For now I'll wipe phone app data,but I'm also waiting if someone knows a good,another solution to post.
Anyone know a way to remove the automatic shutdown?
My phone shuts down if it reaches 25%
The stock camera crashes when I:
-enable RAW
-select slow shutter
-select a shutter speed of 2, 4 or 8s in camera settings
The annoying part is that I have to reboot every time to fix the camera as it seems to be unable to connect again after crashing. Is there any way to fix this without rebooting? There is a play store app but it doesn't work.
Edit:
If you want, vote for the issue.
https://jira.cyanogenmod.org/browse/BACON-1554
Is this with the new update that came out today?
Sent from my OnePlus One®
minicoop7 said:
Is this with the new update that came out today?
Click to expand...
Click to collapse
Yes with 38R.
No issues here just tested
shamo42 said:
The stock camera crashes when I:
-enable RAW
-select slow shutter
-select a shutter speed of 2, 4 or 8s in camera settings
The annoying part is that I have to reboot every time to fix the camera as it seems to be unable to connect again after crashing. Is there any way to fix this without rebooting? There is a play store app but it doesn't work.
Edit:
If you want, vote for the issue.
https://jira.cyanogenmod.org/browse/BACON-1554
Click to expand...
Click to collapse
Question:
Stock?
Bootloader unlocked?
Rooted?
Custom Rom?
Custom Kernel?
Any tweaks to the device other than stock?
I'm just curious...if stock users are having trouble, or is it just the tweakers?
Have you tried a factory reset? And as above, any mods or running 100% stock?
Rooted with stock rom and stock kernel. Clearing the camera cache doesn't help.
I'll try a factory reset as some users don't seem to have the bug.
I've noticed that too. I've also noticed two more things:
- 4k UHD + RAW = bad time. As soon as I hit record it gives me a black screen, I stop the recording and it freezes. I have to force close the camera app to be able to do anything with it again. Oddly enough, 4k DCI works fine.
- Slow-mo video + RAW = choppy. The video seems to be playing back at a super low frame rate. Everything seems to have a lot more motion blur too.
Using raw any time there is low light results in camera crash as well
Sent from my A0001 using XDA Free mobile app
rooted, with stock everything. after taking 8 sec slow shutter, when saving it lags, then black screen then crash. then when i reopen all the menu still there but black screen. anything i do from there it will just crash.
I have the same problem as the poster above.
Any clue?
The other problems described here were correct with the latest update.
Anyone with anything on this?
Same issue here. Will it be fixed ever?
Yep, this has been a known bug from day 1 bro.
Just to put my 10 cents, same problem here even in Auto mode.
This is the only issue I have with my phone now. Hoping CM12 fixes it.
Hello, in CM12, as says Spectre, camera works well, but is there way, to fix this problem in latest official CM13.1, or Lineage14? Thanks much
edit: well, sorry, in CM12.1 problem still here, seems aka HW problem... overheating?
No working solutions? ((
Anyone else having issues with the Night Shot mode?
It seems inconsistent in that it will either crash or produce a terrible low light picture.
Seems the following occurs for me (MHA-L09 stock firmware):
- load the camera app up and enter Night Shot mode, crashes (see pic 1 of it "processing") - though can see it is processing the low light and the image looks good, but it fails to process the image and save (also had to use another phone to take pic of it as was unable to screenshot it
- try and get back to the app after closing (clearing from memory) and cannot enter it
- reboot, open camera, take a few normal pics and then use Night Shot mode. Successfully captures and processes but the resulting low light image is terrible - full of noise! (see pic 2)
- After trial and error it managed to take a decent pic (see pic 3)
Pretty dam disappointed with this brand new device performing like this...
Hopefully an update could solve this?
Running MHA-L09C432B138
Are you using an sd card?
Try clearing camera data from app settings.
gm007 said:
Are you using an sd card?
Try clearing camera data from app settings.
Click to expand...
Click to collapse
Hi, thanks for the reply.
I have tried both clearing the app data and not saving to SD card - just tried that now and it saved (didn't crash on processing) but saved a low quality 'noisy' image.
It's strange though, as whilst processing the image on the display looks great - it's the finished product that lets it down!
In night mode did you changed the iso or auto?
That's weird shouldn't be bad,all you can do is a factory rest and try.
If it's still noisy something is faulty,need a replacement.
gm007 said:
In night mode did you changed the iso or auto?
That's weird shouldn't be bad,all you can do is a factory rest and try.
If it's still noisy something is faulty,need a replacement.
Click to expand...
Click to collapse
Will try that for sure. I don't believe it's hardware fault, must be software.
cd993 said:
Will try that for sure. I don't believe it's hardware fault, must be software.
Click to expand...
Click to collapse
Why you didn't mention that u have unlocked bootloader and flashed ur phone with funky?
Anyway did you factory reset ur phone from settings menu?
gm007 said:
Why you didn't mention that u have unlocked bootloader and flashed ur phone with funky?
Anyway did you factory reset ur phone from settings menu?
Click to expand...
Click to collapse
Regrettably I missed out that detail! I think at the time of writing then I had restored back and so regarded that as 'stock', but I potentially suspect that restoring with Funky MAY be an aspect....
I am tempted to do a full system restore with HiSuite with pure stock (non-Funky) and test that out
cd993 said:
Regrettably I missed out that detail! I think at the time of writing then I had restored back and so regarded that as 'stock', but I potentially suspect that restoring with Funky MAY be an aspect....
I am tempted to do a full system restore with HiSuite with pure stock (non-Funky) and test that out
Click to expand...
Click to collapse
As far as i know hisuite wont work for non Chinese phones.
Do a factory reset from settings,with stock recovery installed,it will do a low level format, could be ur internal storage is corrupted and this can help.
gm007 said:
As far as i know hisuite wont work for non Chinese phones.
Do a factory reset from settings,with stock recovery installed,it will do a low level format, could be ur internal storage is corrupted and this can help.
Click to expand...
Click to collapse
Ok yes that's a great suggestion, will try that out!
Many thanks
I have the same problem. I'm on stock (MHA-L29C432B138), SD-Card or internal storage, same result like in OP.
Edit:
I noticed something. When I take a picture and it shows "in progress" and wait until the lockscreen comes and relock the phone, the pic is taken. Sometimes the camera is still enabled, sometimes it's closed
I tried the same with my Mate 8 (NXT-L29C432B560) , it's the same result.
Looks like it is a Firmware (EMUI/Nougat) bug..
I have the same problem with night shot mode but after change the animation scale to 0.5 in developer option the problem solved. before that i set to off. sorry for my english.
breyt0n said:
I have the same problem with night shot mode but after change the animation scale to 0.5 in developer option the problem solved. before that i set to off. sorry for my english.
Click to expand...
Click to collapse
Hi, thanks so much! It works! :good:
Solved it thanks!
are you using HDR mode?
if so disable it, HDR mode makes low light look bad.
Animation scale settins in Developer options fix Night mode camera crashes
breyt0n said:
I have the same problem with night shot mode but after change the animation scale to 0.5 in developer option the problem solved. before that i set to off. sorry for my english.
Click to expand...
Click to collapse
Excellent suggestion. It also worked for me! I also changed the 3 animation settings (Window animation Scale, Transition animation scale, Animator duration scale) and set the value at 0.5x and the camera is now fine.
Excellent, thank you so much!!
Thanks so much! I'm new here, signed in just so I could say thank you since this solved my camera problem. Anyone have opinions after owning the Mate 9 for a while? I just got it to replace my Nexus 6P with battery issues- not sure I love it yet.
I'm amazed how well smartphone cameras in general, work, given their size.
A typical 8mp sensor, should be able to print an A3 (11x17) image, but who prints anymore?
They keep placing more and more sensors in these things. More megapixels, typically is only
good for crop/zooming. Increasing the sensors can sometimes backfire because the signal to
noise ratio (crosstalk) increases due to the very small spacing between signal paths.
I wish they would just increase the SIZE of the sensor, put a real 5-10x optical zoom lens on the back
similar to the non phone Samsung Zoom a few years back. But with the trend still that phones have
to be "slim, sexy, colorful & stylish", don't see that happening.
sensor size_zps8s6u0xix by Rusty Harris, on Flickr
Hi all,
after the last security update (plus some bugfix I think) to G930FXXU1DQEI sw version, brand Vodafone, I'm facing the following issues on my S7 flat:
A wrong background shape for some popups and a strange black spot on the selector , only in google now settings. Please check the attached pictures
I already tried to fix them by recovery with an hard reset without success.
rikiko1g said:
Hi all,
after the last security update (plus some bugfix I think) to G930FXXU1DQEI sw version, brand Vodafone, I'm facing the following issues on my S7 flat:
A wrong background shape for some popups and a strange black spot on the selector , only in google now settings. Please check the attached pictures
I already tried to fix them by recovery with an hard reset without success.
Click to expand...
Click to collapse
Hi
Definitely odd
I would flash (odin) firmware again , use home-csc ( same CSC that is in your phone right now) so you do not loose any data
After some attempts I can say this issue happens moving the screen resolution from FHD to HD.
I flashed the rom by Odin and worked fine, at the beginning.
After the screen resolution mod the issue is still there.
Moving the resolution to FHD again and switch off/on the issue is not present.
rikiko1g said:
After some attempts I can say this issue happens moving the screen resolution from FHD to HD.
I flashed the rom by Odin and worked fine, at the beginning.
After the screen resolution mod the issue is still there.
Moving the resolution to FHD again and switch off/on the issue is not present.
Click to expand...
Click to collapse
Really odd , i would not expected
Thanks for letting us know
Hi,
I can confirm this is a bug, to be honest I don't know if it was present in the previous build. I tried to reproduce on another S7 (brand tim) and it is present.
Basically the steps to reproduce this issue are:
Change the screen resolution to HD and restart the phone. Uninstall an app and check the text box shape.
Probably you will find other problem in google now search bar or settings
To fix this issue move from HD to FHD.
Hello,
maybe someone can help with my issue.
I got a new OP8 Phone some days ago and transferred all data from my old phone. While setting up the banking app "Deutsche Bank Mobile" i experienced a weird issue with the screen starting to flicker and inputs are recognized only randomly. It only happens in the screen where you have to set up you personal app pin. It seems like an app problem, since it only occurs in this app in that particular sceen. You also see a blue dot appearing randomly on the middle of the screen. See this video for Details:
File on MEGA
mega.nz
What ive tried so far:
- Clear app data and cache
- Clear system cache
- Set display refresh rate to 60hz and vice versa
- enable/disable dc dimming
- set screen to full brightness
- change graphics driver for the app in developer setting (idk if this makes a difference, theres only the choice between standard and another specific setting)
I dont know if its a system or an app related problem. Maybe someone can help?
MrSliff said:
Hello,
maybe someone can help with my issue.
I got a new OP8 Phone some days ago and transferred all data from my old phone. While setting up the banking app "Deutsche Bank Mobile" i experienced a weird issue with the screen starting to flicker and inputs are recognized only randomly. It only happens in the screen where you have to set up you personal app pin. It seems like an app problem, since it only occurs in this app in that particular sceen. You also see a blue dot appearing randomly on the middle of the screen. See this video for Details:
File on MEGA
mega.nz
What ive tried so far:
- Clear app data and cache
- Clear system cache
- Set display refresh rate to 60hz and vice versa
- enable/disable dc dimming
- set screen to full brightness
- change graphics driver for the app in developer setting (idk if this makes a difference, theres only the choice between standard and another specific setting)
I dont know if its a system or an app related problem. Maybe someone can help?
Click to expand...
Click to collapse
What OOS version were you on when it happened? It's a bug that usually occurs when playing video games, but has been fixed since the latest update.
Check the updates, install them and if it keeps doing that maybe contact the customer service to get a new one