I thought to flash a 4.4.4 zip of my stock ROM after updating my boot loader via 5.0 ota.
After that I went back to 5.0 stock.now the stock camera app doesn't seem to show pics in the gallery. Other camera apps work. Also if I try to share the blank image in say WhatsApp the picture suddenly appears.
This happens with cm roms as well.
Any ideas to what might fix this.
I'm using xt1031 on LP bootloader
same issue on my phone, please help how to fix it
I got this problem on my camera results. The color and texture of the images produce is such a big difference before capturing and after it captured. Its quite annoying and disappointing to see such images not quite good in quality after the update to lollipop. Im using a stock rom with Build number 18.6.A.0.175 and says that its my latest rom, I dont receive any OTA update such as 182.
Is there someone who can solve this problem?
Thanks!
if you don't receive update, i think you have root.
if you have root, flash this: http://forum.xda-developers.com/xpe...ashable-camera-blobs-morpho-settings-t3281766
if you haven't root, flash .182 ftf to your phone via flashtool.
Still the problem
I've alredy flash that camera file zip via recovery but nothing has change, still the results are just like using old one which is the stock camera app of. 175. Help please
sorry for my bad english ?
It does work I've flashed it myself to get the updated files. Try clearing the data from all the camera apps and wiping caches
Hi
My M2 is running on build 18.6.A.0.182 lollipop and tried to downgrade to kitkat 4.4.4 using flashtool. But it resulted in a bootloop.
After that using PC companion I repaired it back to 5.1.1 and got it back working .But now the camera is showing some white noise lines while shooting pictures on indoors where there is a bright highlighted area. This happens only in HDR mode. One time I saw it also in Superior auto mode where the auto scene selection was shown as Backlight HDR. So is this a sensor problem or a software issue?
I had a backup firmware of lollipop that I copied from C:\ProgramData\Sony Mobile.
I copied that to the location before repairing it using PC Companion so that the PC Companion wont download the entire firmware which is about 1.1 GB and there by saving my limited data plan. Is there a problem by copying the firmware before repair process?
zankdroid said:
Hi
My M2 is running on build 18.6.A.0.182 lollipop and tried to downgrade to kitkat 4.4.4 using flashtool. But it resulted in a bootloop.
After that using PC companion I repaired it back to 5.1.1 and got it back working .But now the camera is showing some white noise lines while shooting pictures on indoors where there is a bright highlighted area. This happens only in HDR mode. One time I saw it also in Superior auto mode where the auto scene selection was shown as Backlight HDR. So is this a sensor problem or a software issue?
I had a backup firmware of lollipop that I copied from C:\ProgramData\Sony Mobile.
I copied that to the location before repairing it using PC Companion so that the PC Companion wont download the entire firmware which is about 1.1 GB and there by saving my limited data plan. Is there a problem by copying the firmware before repair process?
Click to expand...
Click to collapse
Did you wipe clean the device when trying to downgrade to KK you must wipe user data and cache in flashtool when going from lollipop to KK and vice versa I'd try another software repair as it'll re-install the whole ftf from scratch. Pretty sure sony pcc will always download the latest available firmware from sonys server's before completing a software repair don't think there's anyway round it. It should fix the camera issue
Hi
Solved the problem. Yesterday I downgraded to KK using flashtool 0.9.18.6 . Previously I used 0.9.19.8, in which there was only an option to clear user data and not clear cache.
Flashtool 0.9.18.6 provided both the options and I also read on an XDA post that 0.9.18.6 is best suited for Xperia M2.
Now I am on kitkat 4.4.4 build 18.3.1.B.1.8. Now the camera issue is gone. No more white noise lines on camera pics. Focusing got faster and better. HDR video mode now equalizes bright and dark areas more efficiently as before. In Lollipop videos shot were wobbly with Steadyshot turned on. That was not a problem with KK then and now. Also I got back about 1 GB of Internal memory that was taken up by lollipop .
I love KitKat. But still I miss Lollipop for it's notification design. Can I get a full Lollipop interface on KK without rooting? . I have no idea about rooting modding and all.
zankdroid said:
Hi
Solved the problem. Yesterday I downgraded to KK using flashtool 0.9.18.6 . Previously I used 0.9.19.8, in which there was only an option to clear user data and not clear cache.
Flashtool 0.9.18.6 provided both the options and I also read on an XDA post that 0.9.18.6 is best suited for Xperia M2.
Now I am on kitkat 4.4.4 build 18.3.1.B.1.8. Now the camera issue is gone. No more white noise lines on camera pics. Focusing got faster and better. HDR video mode now equalizes bright and dark areas more efficiently as before. In Lollipop videos shot were wobbly with Steadyshot turned on. That was not a problem with KK then and now. Also I got back about 1 GB of Internal memory that was taken up by lollipop .
I love KitKat. But still I miss Lollipop for it's notification design. Can I get a full Lollipop interface on KK without rooting? . I have no idea about rooting modding and all.
Click to expand...
Click to collapse
Not that I'm aware of and the one I used on KK that was almost like lollipop needed root and superuser mod anyway. Kk sucks compared to 5.1 lollipop in every way but each to their own and all that and rooting 5.1 is also easy now with linuxcts root tool almost a one click job compared to how it was
Ok. is there any way to integrate kitkat camera firmware to lollipop 5.1.1 ?. Or any better camera firmware for M2 in lollipop? . Camera and Internal storage are the main gripe I have with lollipop.
Also I encountered another problem in lollipop recently as I was changing pattern lock. I forgot the pattern lock and it never asked for Google password for recovery. I had smart lock enabled with face detection. It didn't even asked that and I had to perform an ADM erase. Why does this happen with lollipop.
I would like to know about Deodexing. What is that? Is it like rooting? . Will it compromise security?.
In this link http://forum.xda-developers.com/xperia-m2/development/stock-xperia-m2-deodex-patch-t3243891 , it is mentioned Sony shipped the stock with corrupt odex files. Is there any issues with Sony stock firmware?
zankdroid said:
Ok. is there any way to integrate kitkat camera firmware to lollipop 5.1.1 ?. Or any better camera firmware for M2 in lollipop? . Camera and Internal storage are the main gripe I have with lollipop.
Also I encountered another problem in lollipop recently as I was changing pattern lock. I forgot the pattern lock and it never asked for Google password for recovery. I had smart lock enabled with face detection. It didn't even asked that and I had to perform an ADM erase. Why does this happen with lollipop.
I would like to know about Deodexing. What is that? Is it like rooting? . Will it compromise security?.
In this link http://forum.xda-developers.com/xperia-m2/development/stock-xperia-m2-deodex-patch-t3243891 , it is mentioned Sony shipped the stock with corrupt odex files. Is there any issues with Sony stock firmware?
Click to expand...
Click to collapse
They use different frameworks from KK to LP so it wouldn't be possibly to port over. I thought the M2 had an update that fixed your camera problems?
Deodexing is basically a method to allow for modifications to the system and user apps. Sony accidentally/purposely prevented deodexing, so an alternative method is needed. It's harmless on its own though.
zankdroid said:
Ok. is there any way to integrate kitkat camera firmware to lollipop 5.1.1 ?. Or any better camera firmware for M2 in lollipop? . Camera and Internal storage are the main gripe I have with lollipop.
Also I encountered another problem in lollipop recently as I was changing pattern lock. I forgot the pattern lock and it never asked for Google password for recovery. I had smart lock enabled with face detection. It didn't even asked that and I had to perform an ADM erase. Why does this happen with lollipop.
I would like to know about Deodexing. What is that? Is it like rooting? . Will it compromise security?.
In this link http://forum.xda-developers.com/xperia-m2/development/stock-xperia-m2-deodex-patch-t3243891 , it is mentioned Sony shipped the stock with corrupt odex files. Is there any issues with Sony stock firmware?
Click to expand...
Click to collapse
Camera on 18.6.A.0.182 is fine, if rooted with a few tweaks even better(I'm using cam2 ui with a combination of KK+L settings+z5+x framework files). The corrupted services.odex file shipped with 5.1 on M2,t2u and c3 only these three devices are affected(funnily enough the three not originally planned for 5,1) basically it means deodexing the stock 5.1 firmware is impossible and xposed won't work. To get round this @Gaurav007 and Co ported z1c + z2(the better port) deodexed system+framework this brings ultra stamina bravia engine x-reality(only on locked Bootloader) assertive display(must be edited to correct M2 screen size) and gives the m2 z2 features I've been using it since just after 5.1 was released no problem at all I highly recommend it for a good base to start with if on stock and want xposed, the only bug is just a annoying toast message when turning off Bluetooth it actually works fine as I use it for my sbh20's. There's also z5 style rom by @linuxct this also uses gauravs z1c port as it's base but is heavily de-bloated(to much if you ask me)With root and a few tweeks the m2 is a good device. I'd have a read through the threads in here you'll find all the information you need any problems post in here.
I am not able to understand these white/blue spots across the images. Please see the attached images and zoom in to look in the highlighted areas. It's not dust for sure as I have cleaned the lens and the photos were shot in auto mode (no change in ISO etc). IS there an issue with Nougat beta camera or is my sensor damaged?:crying:
What variant you have (L09 or L04) and which firmware you're running (B1..)?!
I am sorry for hijacking this forum, but I have an Honor V8 variant (the big sized version) with EMUI 5.0. beta. There is no xda forum on this model, hence I posted here. I am not sure if the s/w is the issue as I tried it with other camera apps as well producing the same issue
try a 3rd party camera to see if it is still there, if so try reflash stock rom.
If 3rd party apps don't work, then look if there's an update for your phone
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
yes it is probably a hardware issue, but you will have to flash stock to completely rule out a software issue. back up data using twrp
linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
Its a 50 50 situation, some early buyers of honor 8 had the same issue, but after an OTA it's gone.
If it's a hardware issue, return it back if you have warranty.
A friend of mine had the same issue but it was fixed after the update.
Neil6684 said:
A friend of mine had the same issue but it was fixed after the update.
Click to expand...
Click to collapse
Do you mean those spots on zooming in? I have been through 2 beta-Nougat updates, but its not yet resolved. I will factory reset over this weekend and check.
linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
Did you experience this problem when you were using the original version of android that came preinstalled on your device? If you did then it's probably a hardware problem. Which can only be fixed by the manufacturer.
Ok, before I factory reset, I just realized that RAW format is completely fine. However the same jpegs are showing these dead pixels (or bright spots). Is this something s/w related or hardware? Are the raw images processed by s/w or sensor & s/w?
linom said:
Ok, before I factory reset, I just realized that RAW format is completely fine. However the same jpegs are showing these dead pixels (or bright spots). Is this something s/w related or hardware? Are the raw images processed by s/w or sensor & s/w?
Click to expand...
Click to collapse
It's a software issue, don't worry.
If RAW images are fines, then it's just a problem of processing when taking a JPEG photo
An update should fix this
DarkGuyver said:
Did you experience this problem when you were using the original version of android that came preinstalled on your device? If you did then it's probably a hardware problem. Which can only be fixed by the manufacturer.
Click to expand...
Click to collapse
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.
linom said:
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.
Click to expand...
Click to collapse
It's better for you, and when you buy a device make sure it's officially supported in your country (like honor 8) .
All the best
linom said:
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.
Click to expand...
Click to collapse
I'd contact Honor directly and ask them about the problem. Maybe they will release a software patch for it. But I have never heard the Honor 8 had this problem.
I just did a factory reset. The issue persists. Is there a way I could downgrade to EMUI 4.1 rom? I am on Nougat beta and that could be still an issue which I need to exclude. Factory reset keeps the same version of the ROM, I need to downgrade to EMUI 4.1 (Marshmallow) and check.
Also, I suspect the raw images are not processed correctly. Is there a way to change any library associated with image processing? I am able to process raw files on my computer without any issues. I am not rooted, but willing to take that step if it solves this issue.
linom said:
Also, I suspect the raw images are not processed correctly. Is there a way to change any library associated with image processing? I am able to process raw files on my computer without any issues. I am not rooted, but willing to take that step if it solves this issue.
Click to expand...
Click to collapse
Unfortunately, we don't know the exact files (libs that are responsible for image processing)
linom said:
I just did a factory reset. The issue persists. Is there a way I could downgrade to EMUI 4.1 rom? I am on Nougat beta and that could be still an issue which I need to exclude. Factory reset keeps the same version of the ROM, I need to downgrade to EMUI 4.1 (Marshmallow) and check.
Click to expand...
Click to collapse
You would have to contact Honor directly for instructions on how to restore Marshmallow back onto your device. They will also be able to provide you with a link to the Marshmallow firmware for your device.
suddenly i bought this phone second hand. then when I tested Turning on my bluetooth it won't turn on.
Is there anyone experiencing the same problem?
I already did troubleshoot and performed this steps:
1. Wipe cache of Bluetooth Applications on System apps in settings
2. Force stop Bluetooth Applications on System apps in settings
3. Restart my phone
4. Wipe Cache on stock Recovery & restart my phone
5. Restore Factory Settings on Recovery
but suddenly bluetooth still won't open when touching it on notification panel nothing happens even directly on the settings toggling the bluetooth won't work. :crying:
my phone is untouch on rooting world.
So my questions is;
1. Will rooting and flashing rom can solve my bluetooth problem?
2. Is this a hardware problem?
3. Is there a separate chip or module for bluetooth on the motherboard of S7 edge?
to all XDA members I'm asking if you have an idea on this matter please feel free to reply to this post.
thanks you so much!
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Beanvee7 said:
Rooting and flashing a ROM shouldn't be necessary, if you're willing to lose data I would just recommend a full flash via Odin as it keeps you on stock firmware, doesn't trip knox etc. There's stock firmware files and a guide on www.updato.com
Sometimes the OTA updates can be buggy and end up with issues like these. It could be a hardware problem, but I suspect it's probably more likely to just be something wrong with the firmware or bootloader.
Click to expand...
Click to collapse
if it is a hardware problem? is there a separate module or chip on the s7 edge motherboard? or it is integrated on the processor ?
I don't know the answer to that
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
dhawal4u said:
exact problem on my s7 edge 935fd since i updated to Android "Nougat"
tried everything [just like u]
even downgrade to MM or rooting or even custom roms also
but bluetooth not turning on
more than 4 months passed i am not able to find solution to it
Click to expand...
Click to collapse
what custom rom have you tested?
i already tried Batman-Rom
lervzz said:
what custom rom have you tested?
i already tried Batman-Rom
Click to expand...
Click to collapse
batman / superman / tgp and many others
none working
dhawal4u said:
batman / superman / tgp and many others
none working
Click to expand...
Click to collapse
I tried flashing newest stock nougat firnware XTC csc.
Tried it using ODIN
But still bluetooth won't turn on.
Can you say that our problem is hardware failure? But I think if it's a hardware issue then wifi should not work too. Because wifi and bluetooth is on the same chip module. ???
Update: I've talk to numerous technician and they think its not a hardware issue since my wifi is working. They said that wifi and bluetooth is on the same micro chip module. So if it is hardware issue on the bluetooth wifi should not work too. ???????? @dhawal4u
Same Problem here. Since 2 months after trying Badman Rom my Bluetooth doenst work. Now I load Stock Rom, Bootloader, Modem but no solve for the Problem