i recently received a new nexus one because of dust under the screen. today i noticed my camera flash is not working properly.
everytime i take a picture with the flash enabled the flash fires once (for exposure metering i assume) but the second flash never comes. so the images are flashless and super dark.
i tried "factory resetting" and the roblem continues. anyone else have this problem. seems like a software issue? any ideas on how to fix this?
im on stock ere27 2.1 update-1. ALSO this problem effects aftermarket apps as well because its part of the firmware.
Update: recorded a short video to demonstrate my problem.
http://www.youtube.com/watch?v=RVKlSe0UiDY
Called HTC, they had no idea what they where talking about. Transfered me to Google support. They had no idea what was causing this problem and suggested a "swap"
... this phone is a SWAP... its 2 days old.
I'm getting sick of this.
Is there anywhere to download the full stock ROM that is flashable without root? I tried the "manual update" patch from 2.1 to 2.1 Update-1 but that didnt fix it either.
Maybe my firmware has a glitch that is causing this flash problem. Anyone know where I could find the full flashable ROM?
Recorded a short video to further explain whats happening.
http://www.youtube.com/watch?v=RVKlSe0UiDY
please let me know what you think.
dills84 said:
Is there anywhere to download the full stock ROM that is flashable without root? I tried the "manual update" patch from 2.1 to 2.1 Update-1 but that didnt fix it either.
Maybe my firmware has a glitch that is causing this flash problem. Anyone know where I could find the full flashable ROM?
Click to expand...
Click to collapse
It's definately a odd problem, I haven't seen this myself, but if you have already reset your phone to stock and have done the updates and are still experiencing problems. Sadly, your best bet is to have Google warrenty your phone. Don't root to see if its going to fix the problem, you'll be in a much deeper hole if it doesn't fix your problem.
TL;DR
Let Google replace your phone.
Is there a way to re-flash the stock firmware from a ZIP without having the bootloader unlocked?
dills84 said:
Is there a way to re-flash the stock firmware from a ZIP without having the bootloader unlocked?
Click to expand...
Click to collapse
You might want to take a look here.
It has a complete list of all the stock roms and images. (With download links.)
You need to warranty your phone. Don't waste your time trying come up with a solution. I'm sure it's a hassle, but it will be worth it in the long run.
prettyboy85712 said:
You need to warranty your phone. Don't waste your time trying come up with a solution. I'm sure it's a hassle, but it will be worth it in the long run.
Click to expand...
Click to collapse
Just trying to come up with an easy alternative since this is kind of a minor issue?
Also this phone is my second nexus one, First one had tons of dust under the screen. This one is real clean so I was hoping I could hang onto it!
why did the picture without any flash at all have a brighter resolution than the one with the flash on?
EDIT - Have you tried one of the other free camera apps from the market? It might be an error or problem with the stock Camera.apk
palosjr said:
why did the picture without any flash at all have a brighter resolution than the one with the flash on?
EDIT - Have you tried one of the other free camera apps from the market? It might be an error or problem with the stock Camera.apk
Click to expand...
Click to collapse
As stated, this is the problem. The first flash is for "exposure" the second flash is for the actual picture. So the camera is exposing thinking there is a flash coming from the camera. But there is no flash happening during the picture, only before hand.
And yes this is a firmware problem. so any app that uses the camera has the same problem with the flash. I've tried a bunch.
Does anyone know the actual hardware innards of the nexus? If this is just some kind software glitch I may just unlock my bootloarder and fire up CM. Maybe that'll fix it?
I'd hate to return another one... this ones screen is perrrfect.
Related
So I convinced my aunt to get the nexus 4 a while back. Unfortunatly its now not able to make calls correctly. Everything works on the phone without an issue just that There is no sound incoming or outgoing without having to put it on speaker mode (while in a call). This is a already know issue but there is not true way to fix it. We got around it by install the aplication called soundabout and unchecking something about the headphones. That got It to work... for a while. Now it is not working and am going to have to have to downgrade it back to 4.2.1? I read that was the only way. But I wanted to find a real solution. Or at least a reason as to why it happens to maybe figure out a solution?
Are you on 4.2.2? If so, you need your radio baseband upgraded to .48.
If that's not the case, then it could be a hardware issue.
Sent from my Nexus 4 using Tapatalk 2
cmacia06 said:
So I convinced my aunt to get the nexus 4 a while back. Unfortunatly its now not able to make calls correctly. Everything works on the phone without an issue just that There is no sound incoming or outgoing without having to put it on speaker mode (while in a call). This is a already know issue but there is not true way to fix it. We got around it by install the aplication called soundabout and unchecking something about the headphones. That got It to work... for a while. Now it is not working and am going to have to have to downgrade it back to 4.2.1? I read that was the only way. But I wanted to find a real solution. Or at least a reason as to why it happens to maybe figure out a solution?
Click to expand...
Click to collapse
there are a few ways to fix this. technically its not broken, they want you to use the newest baseband/radio, since it disables lte. easiest way is to flash the .48 radio, which was already stated. there is also a method that involves editing a certain file(found in the original dev threads).
simms22 said:
there are a few ways to fix this. technically its not broken, they want you to use the newest baseband/radio, since it disables lte. easiest way is to flash the .48 radio, which was already stated. there is also a method that involves editing a certain file(found in the original dev threads).
Click to expand...
Click to collapse
When she brings me the phone ill have a look at it. Thank you for the replies. Ill probably upgrade her baseband seeing as how she doesnt need lte. I flashed the 4.2.2 images available on the google developers website. All of them. Do those images comes with the baseband that is needed? It came with the radio, recovery, and a few other things... I forgot.
cmacia06 said:
When she brings me the phone ill have a look at it. Thank you for the replies. Ill probably upgrade her baseband seeing as how she doesnt need lte. I flashed the 4.2.2 images available on the google developers website. All of them. Do those images comes with the baseband that is needed? It came with the radio, recovery, and a few other things... I forgot.
Click to expand...
Click to collapse
Where can I get the 4.2.1 Images seeing as how it was taken down from the google website. And so the .48 boot loader image
I Found this http://www.randomphantasmagoria.com/firmware/nexus-4/occam/ but i am not sure what version to download? are they all compatible?
I followed Efrant's guide (http://forum.xda-developers.com/showthread.php?t=2010312) for flashing Android 4.4 stock image(I was previously on 4.3 rooted stock).
After the upgrade, when i tested the new stock camera app, I noticed that the Flash option is disabled(Flash symbol with strike-grayed out). I'm not able to change it to Flash or Auto-Flash mode. Then i downloaded another camera app(Focal cam), and there the Camera flash was working properly.So, I guess the problem is with Stock camera app(It seems to think that my N4 doesn't have an LED Flash).
Am I the only one facing this issue or are ppl out there with same issue ? I tried googling and searching here, but could not find this being mentioned before. Any work arounds (other than a 3rd party camera app) for this problem? If yes, then please let me know.
P.S: I'm already feeling bad about flashing 4.4 update(It is missing out most of the UI changes. I, so, envy N5 users ! Hell with you google )
Exactly the same problem and exactly the same feelings. Were you able to find a fix for this?
badhri said:
I followed Efrant's guide (http://forum.xda-developers.com/showthread.php?t=2010312) for flashing Android 4.4 stock image(I was previously on 4.3 rooted stock).
After the upgrade, when i tested the new stock camera app, I noticed that the Flash option is disabled(Flash symbol with strike-grayed out). I'm not able to change it to Flash or Auto-Flash mode. Then i downloaded another camera app(Focal cam), and there the Camera flash was working properly.So, I guess the problem is with Stock camera app(It seems to think that my N4 doesn't have an LED Flash).
Am I the only one facing this issue or are ppl out there with same issue ? I tried googling and searching here, but could not find this being mentioned before. Any work arounds (other than a 3rd party camera app) for this problem? If yes, then please let me know.
P.S: I'm already feeling bad about flashing 4.4 update(It is missing out most of the UI changes. I, so, envy N5 users ! Hell with you google )
Click to expand...
Click to collapse
Fixed! Just read about the KRT16S build that got pushed out. Re-imaged my Nexus 4 (no patience to wait for OTA) with this latest build and yes, this fixes the camera LED flash issue (it is now enabled). :good:
shikhanshu said:
Exactly the same problem and exactly the same feelings. Were you able to find a fix for this?
Click to expand...
Click to collapse
After installing Android 4.4.2 onto my Razr M (183.46.10.XT907.Verizon.en.US), whenever a sound is played after a period of silence. The
speaker makes a popping noise. This isnt too major of an issue, but I am wondering if it may be a simple setting issue or a problem with the update? Either way is there a known workaround to an issue like this?
I tried KitKat last night and had this even when my phone was on complete silent, It didn't matter if I played anything or not. I also noticed when I was texting someone if I left it open in their text when they replied it would do it also. Another thing for me was the volume lowers itself when playing music (Pandora/Google Play). I turned off the EQ, thinking it might be that, but it didn't do anything. I don't know if that is a feature of KitKat couldn't find anything on it, but I'm back on JB for now.
GPlX said:
After installing Android 4.4.2 onto my Razr M (183.46.10.XT907.Verizon.en.US), whenever a sound is played after a period of silence. The
speaker makes a popping noise. This isnt too major of an issue, but I am wondering if it may be a simple setting issue or a problem with the update? Either way is there a known workaround to an issue like this?
Click to expand...
Click to collapse
I have this issue too and would really like a fix. I don't think a factory reset would help. When i plug headphones in, the popping stops completely.
Yeah ditto. No biggie but they definitely have a bug that submits noise to the speaker.
Sent from my XT907 using XDA Free mobile app
mrkhigh said:
Yeah ditto. No biggie but they definitely have a bug that submits noise to the speaker.
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Every time there's sound, the popping happens. If I play a song, before the song starts playing it starts popping. I think it's more than just noise being submitted because of touch input.
Well after no official response for a few days here, I've contacted Motorola customer support to see if they
Possibly told the low level support about a potential fix. Unfortunately no luck.
The interesting thing is that my family all use the RAZR m and all 3 phones have one form or another of the speaker issue.
I am still in warranty and have been offered to send it in for replacement/repair.
Thoughts? I am not sure if replacing the phone(s) will do any good.
GPlX said:
Well after no official response for a few days here, I've contacted Motorola customer support to see if they
Possibly told the low level support about a potential fix. Unfortunately no luck.
The interesting thing is that my family all use the RAZR m and all 3 phones have one form or another of the speaker issue.
I am still in warranty and have been offered to send it in for replacement/repair.
Thoughts? I am not sure if replacing the phone(s) will do any good.
Click to expand...
Click to collapse
I doubt replacing it will do anything unless you can somehow get the unlocked developers' version. This seems to be an issue with the rom, not the phone itself.
shnish said:
I doubt replacing it will do anything unless you can somehow get the unlocked developers' version. This seems to be an issue with the rom, not the phone itself.
Click to expand...
Click to collapse
Funnily enough I decided to try replacing it and the phone arrived the day this message was posted. The replacement did solve the issue... mostly.
I hear a faint two click/pops on sounds but they are so faint that you can only hear them in a quiet place with your full attention.
Seriiez said:
I tried KitKat last night [...]
I don't know if that is a feature of KitKat couldn't find anything on it, but I'm back on JB for now.
Click to expand...
Click to collapse
How did you get back to JB? I made the OTA Update from Stock JB and would like to flash back to JB somehow.
I have an unlocked bootloader, and downloaded the JB (98.30.1.XT907) sbf file. I had to edit some lines out the .xml (found the instruction in another post) and used RSDlite to flash back. If you're locked I have no idea if you can go back.
Fix for unlocked bootloader only!
Boot images for XT926 and XT907 stock kitkat:
XT926: http://d-h.st/vre
XT907: http://d-h.st/KXA
Both boot images contain the recompiled stock kitkat kernel with increased sleep time after lineout PA enable, as in this commit: https://github.com/CyanogenMod/andr...mmit/1212f2e043341016cacd6b0d93435380750bd78e
To be flashed via fastboot:
Code:
fastboot flash boot bootXT926speakerfix.img
or
Code:
fastboot flash boot bootXT907speakerfix.img
Please note that I don't own xt926 nor xt907, so I can't verify that the boot images boot at all, nor that they actually fix the issue.
(xt897 haven't got an official kitkat update yet, and it's possible that it won't happen for Photon Q at all.)
Be prepared to flash the stock kitkat boot.img in case of a failure if you're going to test this. You've been warned.
Please let me know how it works for you, thanks.
EDIT: links updated to correctly re-packed boot images.
xt926 boot image already confirmed to boot fine and fix the issue (by iBolski).
XT907 boots fine and also seems to fix the issue.
kabaldan said:
Fix for unlocked bootloader only!
Boot images for XT926 and XT907 stock kitkat:
XT926: http://d-h.st/vre
XT907: http://d-h.st/KXA
Both boot images contain the recompiled stock kitkat kernel with increased sleep time after lineout PA enable, as in this commit: https://github.com/CyanogenMod/andr...mmit/1212f2e043341016cacd6b0d93435380750bd78e
To be flashed via fastboot:
Code:
fastboot flash boot bootXT926speakerfix.img
or
Code:
fastboot flash boot bootXT907speakerfix.img
Please note that I don't own xt926 nor xt907, so I can't verify that the boot images boot at all, nor that they actually fix the issue.
(xt897 haven't got an official kitkat update yet, and it's possible that it won't happen for Photon Q at all.)
Be prepared to flash the stock kitkat boot.img in case of a failure if you're going to test this. You've been warned.
Please let me know how it works for you, thanks.
EDIT: links updated to correctly re-packed boot images.
xt926 boot image already confirmed to boot fine and fix the issue (by iBolski).
Click to expand...
Click to collapse
this may be a stupid question...but could i flash this with the flashify app? would it work on a phone with custon rom?
crazy4android said:
this may be a stupid question...but could i flash this with the flashify app? would it work on a phone with custon rom?
Click to expand...
Click to collapse
Sorry, I have no idea what flashify app is and does. I'm used to do the flashing from command line.
The boot images linked here are only for the stock 4.4 ROM.
The issue will be fixed directly in the CM11/razrqcom motorola msm8960dt-common kernel in the future.
See my post about it here: http://forum.xda-developers.com/showthread.php?p=53614821
Odd thing, is my black RAZR M whose manufacture date was sometime in 2012 didn't have this problem at all. No popping whatsoever. However, my white one with manufacture date sometime around 5/2013 did have this problem. Makes me wonder if the hardware was updated in some minor way.
kabaldan, thank you so much this really seems to work. Great work. that popping sound was getting on my last nerve I even un installed solitary because every time I taped a card the phone made a popping sound very annoying. You fixed my phone thanks bro.
crazy4android said:
this may be a stupid question...but could i flash this with the flashify app? would it work on a phone with custon rom?
Click to expand...
Click to collapse
I made a backup just in case. then used flashify to flash this boot.img once done I rebooted the phone and profit
Quick question kabaldan, ppl are making claims to battery life and wifi etc, in this thread http://forum.xda-developers.com/showthread.php?p=53614821#post53614821. That bit in the commit you posted, that's the only thing you changed right?
@kabaldan Hi, i had this same problem with my razr i XT890, could you make a fix for he too?
Thx
Hello and thank you for taking the time.
I recently gotten this message popping up everytime I try to use the camera on my S4.
"Can't connect to camera". I'm not sure why this is happening, so I thought maybe perhaps it had to do with the camera itself
so I went ahead and got the camera part replaced and got a new camera and it still shows this :'( I spent a lot of money getting this new camera part and I still get this message.
Can some one please help me? I sincerely ask because I am losing hope.
I am currently running a PAC-MAN ROM
Thank you again!
Mkami said:
Hello and thank you for taking the time.
I recently gotten this message popping up everytime I try to use the camera on my S4.
"Can't connect to camera". I'm not sure why this is happening, so I thought maybe perhaps it had to do with the camera itself
so I went ahead and got the camera part replaced and got a new camera and it still shows this :'( I spent a lot of money getting this new camera part and I still get this message.
Can some one please help me? I sincerely ask because I am losing hope.
I am currently running a PAC-MAN ROM
Thank you again!
Click to expand...
Click to collapse
I'd recommend Odin back to stock. If the camera works then you know it was a software issue with your ROM. If not, then you most likely have a hardware issue.
Or if you you think that is too extreme, just try reinstalling your ROM first.
guut13 said:
I'd recommend Odin back to stock. If the camera works then you know it was a software issue with your ROM. If not, then you most likely have a hardware issue.
Or if you you think that is too extreme, just try reinstalling your ROM first.
Click to expand...
Click to collapse
Thank you so much for replying. I am sincerely grateful.
The front camera works just fine. Its the rear camera.
I have wiped and installed my ROM into the phone hoping that'll work but nothing. I also tried another ROM still nothing.
What you have suggest though about using ODIN to go back to stock ROM I shall try
Is there anything specific I need to do to go back to stock ROM for the s4? I have i337m and don't have the original ROM.
It's been 4months since I last did all this so I'm a bit in need of refreshing.
Thank you again friend
Mkami said:
Thank you so much for replying. I am sincerely grateful.
The front camera works just fine. Its the rear camera.
I have wiped and installed my ROM into the phone hoping that'll work but nothing. I also tried another ROM still nothing.
What you have suggest though about using ODIN to go back to stock ROM I shall try
Is there anything specific I need to do to go back to stock ROM for the s4? I have i337m and don't have the original ROM.
It's been 4months since I last did all this so I'm a bit in need of refreshing.
Thank you again friend
Click to expand...
Click to collapse
You'll need the odin tar file specific to your i337m phone. Unfortunately, I'm on i337 so I'm not sure which one you need.
I guess start with determining what base you are on. Should help you find it easier. This link will help with that..
http://forum.xda-developers.com/showpost.php?p=51067793&postcount=4
guut13 said:
You'll need the odin tar file specific to your i337m phone. Unfortunately, I'm on i337 so I'm not sure which one you need.
I guess start with determining what base you are on. Should help you find it easier. This link will help with that..
http://forum.xda-developers.com/showpost.php?p=51067793&postcount=4
Click to expand...
Click to collapse
So I have done everything and found out it is a hardware issue :/ Does this mean it is not fixable?
Mkami said:
So I have done everything and found out it is a hardware issue :/ Does this mean it is not fixable?
Click to expand...
Click to collapse
Sounds like a hardware issue then. (Had it been a driver issue, the stock samsung firmware that you installed on it would have solved that issue)
You mentioned you just got a new camera. Did the camera work after it was installed? If you took it to a store, maybe it's still under warranty and you can take it back. If you replaced it yourself, maybe the something came loose. Try taking it apart and making sure it's still connected. If it was an after market camera, maybe you need different drivers?
guut13 said:
Sounds like a hardware issue then. (Had it been a driver issue, the stock samsung firmware that you installed on it would have solved that issue)
You mentioned you just got a new camera. Did the camera work after it was installed? If you took it to a store, maybe it's still under warranty and you can take it back. If you replaced it yourself, maybe the something came loose. Try taking it apart and making sure it's still connected. If it was an after market camera, maybe you need different drivers?
Click to expand...
Click to collapse
Do you know where I can get the drivers for the camera on the s4 i337? I double checked everything after taking it apart and yet nothing. If it's an actual hardware issue I guess I can't do anything about it :'(. Actually my warranty is voided due to rooting. Thank you very very much for trying though
Mkami said:
Do you know where I can get the drivers for the camera on the s4 i337? I double checked everything after taking it apart and yet nothing. If it's an actual hardware issue I guess I can't do anything about it :'(. Actually my warranty is voided due to rooting. Thank you very very much for trying though
Click to expand...
Click to collapse
The Samsung camera drivers would be built in to the stock image. I just threw in the driver suggestion in case you replaced the camera with another brand.
I wouldn't worry too much about your warranty being void due to rooting. It's one thing if you bricked your phone because you were trying to flash something you shouldn't have and then try to get it replaced under warranty... That's wrong.
By Odin back to stock you put the phone back into the state it was when you first received it. If the camera is still not working, I would try to get it fixed under warranty. (unless of course it broke from a fall or a swim... then you'd be out of luck)
Hi guys,
Just rooted my S8 and installed TWRP, using STOCK Samsung ROM, AQH3. I noticed in the Camera that "Selective Focus" is not working anymore. I didn't change anything else, just rooted the device and installed Notorious Kernel, before doing this the Selective Focus was working OK. So does anyone know what happened? Any help would be highly appreciated, I really like this shooting mode. Thank you!
EDIT: To clarify: before this I got sometimes the error, but mostly of the time it worked well. Now after rooting the phone and installing TWRP it doesn't work at all in any conditions, even with different subjects.. I've heard someone reporting this issue in another thread, but I can't remember at all
Root these days is nothing but problems.
Well ok.. But I really can't figure out how root could broke a single, specific, functionality of the Camera
blak24 said:
Well ok.. But I really can't figure out how root could broke a single, specific, functionality of the Camera
Click to expand...
Click to collapse
Flash stock firmware through Odin and then check again if this solve the issue.
Also which method of root? Magisk or SuperSu?
I used Magisk. Anyway if I'll flash stock firmware through Odin I'll lose TWRP and root and everything else right?
blak24 said:
Well ok.. But I really can't figure out how root could broke a single, specific, functionality of the Camera
Click to expand...
Click to collapse
Seems like kernel related issue
Mmmh so you suggest to try changing kernel and/or flashing the stock one to see if the issue persists?