Related
Anyone else have the camera load to a blank black screen with no buttons in any and all apps that utilize the camera? Camera, Barcode Scanner, Sniper Shot, and all other programs that use the camera fail to load since the update. Anyone have any idea as to why?
DanielWGK said:
Anyone else have the camera load to a blank black screen with no buttons in any and all apps that utilize the camera? Camera, Barcode Scanner, Sniper Shot, and all other programs that use the camera fail to load since the update. Anyone have any idea as to why?
Click to expand...
Click to collapse
Did you try a restart, I have heard of camera problems like this before (i think first FroYo update) and all it needed was a simple reboot.
Reboot didn't work. I reflashed the rom and BAM, it worked again. Crisis averted.
I have the same problem.
I'm running the following:
Azreal 3.0
circular battery widget update
removed HTC lock screen
superior battery charging kernel
wifi hotspot patch
I'm currently trying things to figure out what will fix it.
Here are the current things I have tried that did NOT fix the problem:
Reboot
Wipe cache/davlik cache
fix UID mismatches
I then reflashed azreal 3.0
At this point the camera worked again but everything was wiped. I then reapplied the following patches:
Circular battery
remove HTC lock screen
wifi/hotspot patch
after this everything continued to work
I then applied:
superior battery charging kernel and it broke again
I think the problem is the superior battery charging kernel
i am having the same problem and have not been successful yet fixing it. switched from cm7 back to stock to update my prl and tryed to use the camera while stock when the black blank screen happened. flashed to evdo(sense) and same result. flashed back to cm7 and the 1st time i opened camera it opened the ffc. when i tried to switch and everytime i have tried to open it since i get "camera error cannot connect to camera" help plz!
If you have HW 0004 phone or HW003 with the new camera, you have to make sure your rom has a kernel with the NEW drivers. The kernel in my signature has the new drivers for ASOP roms (like cm 7).
just flashed Savaged-Zen-V002-CFS-HAVS-SBC-WiMAX - GB.zip
with the same result running cm7. seems like ive tried 20 different things with no success. everything i have flashed has been off my sd meaning i have had all of it running before at one time or another with no problem. i really cant think of what ive done new to have caused this
Same here
Happened to me right after I flashed calkulins_format_all.zip and then the MikFroyo4.4.zip yesterday. I thought it was a problem with mikfroyo so I flashed Azraelz 3.1 and still the same issue (i was using azrael 3.0 with no prob prior to mikfroyo).
I'll post if I find anything that works, please also give any suggestions i'm willing to try anything b4 i take her to sprint.
I also flashed calkulins evio rom. When I flash back to stock it will start running again sometimes. Not even right away though. It will be black for a while then if I just let the phone sleep for a bit and come back to it bam. Camera again. For a little while. Then back to the same thing an hour later without doing anything! This is very frustrating! Someone plz help!
Sent from my PC36100 using XDA App
UPDATE
I turned my phone off and switched SD cards to one that has an old backup (3.29, kernel#11), when I booted into recovery, I could hear clicking noices coming from the lens, at a super fast rate (say 2-3 clicks a second).
Not wanting to do any more damage I turned off the phone.
I did just take my phone to sprint to fix my kick stand, maybe they did something to mess with me (thats just my paranoid side speaking)...
But what gives? What would make the camera shutter do that while im in recovery (btw using latest amon ra recovery)?
Hey,
I know there are a few threads on this but I haven't found one that followed through to a reported solution.
G2 rooted with CyanogenMod 6.1.1 since January of this year. Tried google goggles and the app locked up. I finally realized that was because the camera has stopped responding. When I pressed on the camera help, nothing changes for a few seconds, then it goes to a black screen. Eventually, (pressing on the back key helps) I'll get a force close/wait screen. Camera had been working fine the previous day.
I've tried clearing caches, using a different SD card with no changes. Used the opportunity to finally upgrade to CyanogenMod 7.0.3 and cleared all the caches as part of the flash. Tried the camera the first chance I could get the phone to that point. Same response from the camera (hesitate, black screen, force close).
So, is there anything else to try or is this a hardware camera failure?
Thanks for any help.
Try flashing some other rom. If that fails, then try flashing another radio.
I'd suggest taking a rooted stock rom and a stock radio just to be sure.
Thanks, but I'm trying to understand what any of that would do to fix the camera over what I've already tried.
I guess I'm looking for anyone that actually had a similar problem and either fixed it or failed to fix it.
Thanks.
Well for once the stock rom uses HTCcamera.apk to open the cam. Since you are using CM7 its a completely different apk.
Radio is somethign that is responsible for almost every device on your phone. Then the drivers that are in the Kernel, and then the ROM which has the apk, that uses the driver from the kernel to start the camera that is defined in the radio.
Well, nothing worked. Unrooted and back to stock (camera still doesn't work). Replacement phone is on it's way.
Since I upgraded to gingerbread (stock rooted 4.24.651.1), my phone randomly crashes when taking pictures. At least 95% of the time, it works fine. Sometimes I take a picture and it doesn't return to the camera after displaying the captured image. Instead, it hangs on the preview for a few seconds, then the screen turns black and it won't respond to any buttons. If I wait long enough (20 seconds? I'm not sure), eventually the phone will reboot. Usually I'm impatient and pull the battery. Sometimes the picture is saved and sometimes it isn't, but I think this is related to whether I pull the battery. For a long time I thought that it only occurred when the flash was OFF, but it crashed again today when the flash was set to auto and it flashed when I took the picture.
Is there anything I can do to determine the cause and/or prevent it?
velociraptors said:
Since I upgraded to gingerbread (stock rooted 4.24.651.1), my phone randomly crashes when taking pictures. At least 95% of the time, it works fine. Sometimes I take a picture and it doesn't return to the camera after displaying the captured image. Instead, it hangs on the preview for a few seconds, then the screen turns black and it won't respond to any buttons. If I wait long enough (20 seconds? I'm not sure), eventually the phone will reboot. Usually I'm impatient and pull the battery. Sometimes the picture is saved and sometimes it isn't, but I think this is related to whether I pull the battery. For a long time I thought that it only occurred when the flash was OFF, but it crashed again today when the flash was set to auto and it flashed when I took the picture.
Is there anything I can do to determine the cause and/or prevent it?
Click to expand...
Click to collapse
It could be an issue with the apk, it could be a hardware issue as well.
You could either try installing the camera or re-flashing the ROM/kernel or returning to stock.
If it continues after all of that it's likely a hardware issue.
mattykinsx said:
It could be an issue with the apk, it could be a hardware issue as well.
You could either try installing the camera or re-flashing the ROM/kernel or returning to stock.
If it continues after all of that it's likely a hardware issue.
Click to expand...
Click to collapse
That's the thing, it is the stock rom. I have flashed a few different roms, but I've returned to stock after a day or two without using the camera much so I don't know if the problem is specific to the stock rom. I've been meaning to flash the rooted 4.53.651.1 update anyway. If that doesn't fix it, I'll try to reproduce the crash in other roms.
velociraptors said:
That's the thing, it is the stock rom. I have flashed a few different roms, but I've returned to stock after a day or two without using the camera much so I don't know if the problem is specific to the stock rom. I've been meaning to flash the rooted 4.53.651.1 update anyway. If that doesn't fix it, I'll try to reproduce the crash in other roms.
Click to expand...
Click to collapse
I mean stock as in fully stock, unrooted.
It's possible that when you flashed the rooted version it was a bad download/flash.
Like I said, if the issue continues across multiple ROMs/Kernels then it's probable that their is a hardware issue.
velociraptors said:
Since I upgraded to gingerbread (stock rooted 4.24.651.1), my phone randomly crashes when taking pictures. At least 95% of the time, it works fine. Sometimes I take a picture and it doesn't return to the camera after displaying the captured image. Instead, it hangs on the preview for a few seconds, then the screen turns black and it won't respond to any buttons. If I wait long enough (20 seconds? I'm not sure), eventually the phone will reboot.
Click to expand...
Click to collapse
I'm having this issue on two different EVO 4G phones:
Updated to 4.24.651.1 OTA, S-OFF and custom recovery with the Revolutionary method, followed by Superuser root. Then all I did was move Sprint bloatware from /system/apps (all Google and HTC software bits were untouched). The phone was used for a week and the phone/reboot problem was noticed. Then I restored stock recovery, updated the phone to 4.53.651.1, re-ran the Revolutionary tool, and got root again. Then once more I moved Sprint bloatware from /system/apps. The update didn't fix the phone/reboot issue.
On a second phone it had 4.53.651.1 to start off with. I ran the Revolutionary tool for S-OFF and custom recovery, installed Superuser for root, and then moved the Sprint bloatware from /system/apps. With this phone also, the phone/reboot issue can be reproduced.
I have no idea what can be causing this, but at least I know I'm not alone in having this problem now.
I hope someone can identify and fix this.
What bloatware did you remove? I removed some as well, which might be the common issue.
So you have a way to reliably reproduce it? If so, I'll do some tests.
velociraptors said:
What bloatware did you remove? I removed some as well, which might be the common issue.
So you have a way to reliably reproduce it? If so, I'll do some tests.
Click to expand...
Click to collapse
These are the apps that I moved:
amazonmp3.apk
Blockbuster_htc.apk
HTC_Evo_Sprint_NOVA_HEP_ML320.apk
Kindle-1.0.2.80600055-OEM-SingleSign.apk
nascar09-prod-release.apk
qik.apk
Quickoffice.apk
sfl-prod-release.apk
Sprint_Navigator.apk
SprintTV_v1_0_4_46_124166.apk
SprintTVWidget.apk
SprintZoneNC_2511.apk
Stock.apk
Stock.odex
teeter.apk
teeter.odex
WifiRouter.apk
WifiRouter.odex
To reproduce the issue (and it is random), take a picture with the camera app and then try to access the Gallery from the button on the lower-right corner of the app screen.
I have a problem with MIUI rom. Some days ago, my phone suddenly had FC, now, my phone run really slow and laggy... If I turn off the screen, my phone won't wake up, only four button in the bottom light up.
I wiped everything in CMW (system,data, and cache, also sd-card) but it doesn't work.
The fresh install had the same issues
I have this problem only with MIUI rom
any help
You probably need to provide more info on the issue. What version of MIUI are you running? Have you tried a fresh download of the ROM?
zandroid said:
You probably need to provide more info on the issue. What version of MIUI are you running? Have you tried a fresh download of the ROM?
Click to expand...
Click to collapse
i have tried from 1.8.5 to 1.9.2.
it's very weird
this guy has the same problem with me, maybe he can explain better than me
http://forums.miui.us/showthread.php?3740-Display-won-t-wake-from-sleep
Hey guys, I flashed 1.819 yesterday and everything was going great. The ROM ran smoothly and I was having no issues at all. When I woke up the next morning my display would not turn back on. Every time I tried to turn on the display the soft lights would light up but the display remained unresponsive. The phone still seemed functional as I could hear e-mail and sms notifications coming through.
When I rebooted my phone it was abnormally slow.. mounting the sd card and syncing seemed like it was taking forever and the launcher was very jittery.. if I let my display time out it would not come back on and I'd be forced to pull the battery and try again.
I performed a full wipe through clockwork recovery (everything, including wiping system,data, and cache in 'mounts and usb') and reinstalled 1.819. The fresh install had the same issues.. if I let my display time out I wouldn't be able to turn it back on. I thought I was having some wonky hardware issue but after flashing my previous sense rom and everything is working perfectly.. so I'm pretty much scratching my head here. My phone was kickass for one day and became allergic to MIUI overnight!
Click to expand...
Click to collapse
Have you tried using a different kernal such as Tiamat or JD's Kernal?
May want to try that. I had good luck with Miui and Tiamat (ran it for a week)
PacerguyDon said:
Have you tried using a different kernal such as Tiamat or JD's Kernal?
May want to try that. I had good luck with Miui and Tiamat (ran it for a week)
Click to expand...
Click to collapse
i have tried both
Does this happen immediately after you flash? Or are you installing applications to get back to your preferred setup and then seeing the performance problems?
If it's the latter, I'd run the rom alone and see if it runs normally. Then install your applications individually until you encounter issues.
ttupa said:
Does this happen immediately after you flash? Or are you installing applications to get back to your preferred setup and then seeing the performance problems?
If it's the latter, I'd run the rom alone and see if it runs normally. Then install your applications individually until you encounter issues.
Click to expand...
Click to collapse
immediately after the flash. I don't install any other apps
since we are talking about MIUI issues. I am running the latest version of MIUI with the JDKernal.
The camera has color distortion lines when I take a picture. The picture comes out fine but when taking it the image shows the distortion. It did not do that before so I can only assume its something with the camera in the ROM.
Anyone else see this?
spiderj said:
since we are talking about MIUI issues. I am running the latest version of MIUI with the JDKernal.
The camera has color distortion lines when I take a picture. The picture comes out fine but when taking it the image shows the distortion. It did not do that before so I can only assume its something with the camera in the ROM.
Anyone else see this?
Click to expand...
Click to collapse
Try different kernel
Sent from my Incredible 2 3D using XDA App
tenchu_712 said:
immediately after the flash. I don't install any other apps
Click to expand...
Click to collapse
tenchu, your signature says you are not English or American. Are you running the MIUI.us ROM on your incredible 2 in English - and not another language?
.....just a thought.
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.
Are you sure it's the phone and not an app?
chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.
I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!
well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).