Related
I'm so mad right now.
My camera app crashed even after several reboots forcing a Hard reset.
I lost all my data and the camera app still crashes.
I can't describe how mad I am.
I press the camera button and it shows for a sec. It then immediately returns to the home screen.
I'm gonna contact Microsoft first thing in the morning.
I might lose a job because of this.
The hard reset didn't fix anything. It still crashes .
Can someone link me the he fastest way to get to Microsoft to help me fix this stuff.
I'm seriously going insane. All me stuff is gone and since its impossible to take a backup I'll never get it back.
Die, Microsoft. Die.
You just made me lose heaps of things because of a camera flaw.
Thanks for letting us know:
1. What you were doing when it crashed.
2. What type of phone you have.
3. Whether or not you're using a 3rd party MicroSD card in the slot.
4. What actually happens when it crashes (phone freezes, app just closes, middle finger graphic comes up on the screen, what does it do?)
5. Were you on WiFI, EDGE, 3G, GPRS?
6. Are you sure the device isn't defective (And/or prematurely failing on you? In this case, the OS has nothing to do with it - can happen on any phone running any Smartphone OS)
7. Other trivial information that can cause us to come to better conclusions.
Instead, you plummel us with bad grammar, vulgarities, and a rant that will certainly accomplish nothing due to #s 1-5.
BTW, you should back up all important information on any device. Laptop, Tablet PC, Desktop PC, Smartphone, Thumb Drive, etc. It's not Microsoft's fault if you lose you fault due to data loss. Important information should be backed up and IIRC Windows Phone 7 is capable of keeping the Camera Roll Sync'd up with SkyDrive.
I give you 3/10, though.
Ciao!
You might try Windows Phone Support on twitter. They usually reply pretty fast during business hours.
http://twitter.com/#!/WinPhoneSupport
A side note, if you've got a job that depends on your ability to take pictures, you might not want to depend on a phone's camera and use a dedicated camera.
@Side Note: Still shouldn't matter. Anyone that takes (EDIT) photos for business use with their phone camera should have the SkyDrive Camera Roll Backup/Sync enabled and you can set your Photo Gallery to Private.
The OP's situation is completely avoidable.
badboy70 said:
I might lose a job because of this.
Click to expand...
Click to collapse
This is either a very bad troll or you're a complete moron. I can't decide.
Sent from my GT-I9000M
damn my camera app crashed too yesterday after i was changing some settings.
i turned off light and changed the measurement adjustment.
it crashed when i tried to focus the object. black screen, crash.
so happy a restart fixxed it, i better dont mess with the settings for some time...
Yeah, besides, Microsoft did not MAKE you do a hard reset of your device.
If you read the manual and understood what you were doing before you did it you would have known that a Hard Reset puts the phone back to its initial state.
You must have also disabled image syncing onto Zune which would have backed up your photos everytime you plugged it in or Wifi synched it. Could have also auto-uploaded the pics to Skydrive and had a lower resolution copy on there.
Can't blame Microsoft for this. Yes, the camera should not be broken, but most times a soft reset will fix any software issues.
Bah, sorry.
I was kinda drunk when I posted this.
I was at a party.
But to answer the questions:
1. What you were doing when it crashed.
Nothing. I tried to take a picture by holding the camera button whilit was still locked.
2. What type of phone you have.
HTC HD7
3. Whether or not you're using a 3rd party MicroSD card in the slot.
No, I did not modify my phone
4. What actually happens when it crashes (phone freezes, app just closes, middle finger graphic comes up on the screen, what does it do?)
It shows the zoom bar on the right, then immediately closes and shows the start screen.
5. Were you on WiFI, EDGE, 3G, GPRS?
Edge
6. Are you sure the device isn't defective (And/or prematurely failing on you? In this case, the OS has nothing to do with it - can happen on any phone running any Smartphone OS)
Nope, there's nothing wrong with it other than that.
7. Other trivial information that can cause us to come to better conclusions.
Not really, I never did anything special to it.
All I did that evening was texting, calling and updating my status on Facebook because the power blacked out, three times.
Ok, so after the third hard reset the camera works again.
But now all the pictures I take are rotated 90 degrees
I think there's definately something wrong with the camera app.
badboy70 said:
Ok, so after the third hard reset the camera works again.
But now all the pictures I take are rotated 90 degrees
I think there's definately something wrong with the camera app.
Click to expand...
Click to collapse
Sounds more like a HW problem to me (wouldn't be the first for a HD7) as it doesn't happen to everyone else.
Yeah, sounds like a bad HD7 to me too. My first HD7 was an awesome phone, if by awesome, the standard you use is how often it simulated Windows XP by crashing on me.
Returned it and got a new one and it's been smooth sailing so far.
Send that POS back and replace, blame HTC not MS and don't do your business while drunk otherwise it won't be the phone's fault you lost your job.
i don't know which is worse, being unable to identify the cause or blaming something else other than the cause
badboy70 said:
I'm so mad right now.
My camera app crashed even after several reboots forcing a Hard reset.
I lost all my data and the camera app still crashes.
I can't describe how mad I am.
I press the camera button and it shows for a sec. It then immediately returns to the home screen.
I'm gonna contact Microsoft first thing in the morning.
I might lose a job because of this.
The hard reset didn't fix anything. It still crashes .
Can someone link me the he fastest way to get to Microsoft to help me fix this stuff.
I'm seriously going insane. All me stuff is gone and since its impossible to take a backup I'll never get it back.
Die, Microsoft. Die.
You just made me lose heaps of things because of a camera flaw.
Click to expand...
Click to collapse
Honestly, I'm actually surprised somebody hasn't posted Die, Badboy70. Die. because of this post, XDA is maturing. Anyway, your Zune auto syncs your photos by default, I'm assuming if you do this for a living, you'd know not to turn this off. So, I'm going to go out on a limb here and say that you're FOS for saying you're losing a job because of this. I'm betting more on you being a 14 year old who's phone is malfunctioning due to a hardware problem and had to come rant about it instead of asking for help.
Jonno2343 said:
Yeah, besides, Microsoft did not MAKE you do a hard reset of your device.
If you read the manual and understood what you were doing before you did it you would have known that a Hard Reset puts the phone back to its initial state.
You must have also disabled image syncing onto Zune which would have backed up your photos everytime you plugged it in or Wifi synched it. Could have also auto-uploaded the pics to Skydrive and had a lower resolution copy on there.
Can't blame Microsoft for this. Yes, the camera should not be broken, but most times a soft reset will fix any software issues.
Click to expand...
Click to collapse
Just wanted to echo this.
badboy70 said:
Bah, sorry.
I was kinda drunk when I posted this.
I was at a party.
But to answer the questions:
1. What you were doing when it crashed.
Nothing. I tried to take a picture by holding the camera button whilit was still locked.
2. What type of phone you have.
HTC HD7
3. Whether or not you're using a 3rd party MicroSD card in the slot.
No, I did not modify my phone
4. What actually happens when it crashes (phone freezes, app just closes, middle finger graphic comes up on the screen, what does it do?)
It shows the zoom bar on the right, then immediately closes and shows the start screen.
5. Were you on WiFI, EDGE, 3G, GPRS?
Edge
6. Are you sure the device isn't defective (And/or prematurely failing on you? In this case, the OS has nothing to do with it - can happen on any phone running any Smartphone OS)
Nope, there's nothing wrong with it other than that.
7. Other trivial information that can cause us to come to better conclusions.
Not really, I never did anything special to it.
All I did that evening was texting, calling and updating my status on Facebook because the power blacked out, three times.
Click to expand...
Click to collapse
Your excuse of being drunk just validates the first part of my phone. You won't know your device is defective without a professional looking at the camera hardware. Just becase nothing else is messing up doesn't mean the camera isn't defective. Considering it worked, and then didn't, especially on factory settings leads me to believe this is hardware related, if it even exists at all. I would try to replace the device.
It's more likely to be a defective HD7 ...
Doesn't a hard reset delete all the data off your phone? So instead syncing it to your PC and extracting the photos you decided to delete. It may be MS fault that your Camera app crashed, but its your fault the data is missing. Why didn't you back your photos up on your computer or even to skydrive? Couldn't had been to important if your didn't.
So you know how when you write out something really long and detailed and triple check it for spelling, grammar and readability and realize that you've been on the page long enough that you have been logged out so you copy everything you've just spent over an hour writing to make sure you don't lose it when you log back in and then you've forgotten your password because you made it in the middle of the night and you were tired so you do a reset and they send you a new password full of random letters so you....copy and paste that into the log in.............yeah..... bye bye 300+ words.......
So I'll try again but forgive me if its short or missing a few details. Please let me know any additional information you think might be useful.
First a short thanks to the community for all of their advice to others. I have learned a great deal from these forums.
Now on to the issue. Essentially what has happened is I received an update to an app called Widgetsoid which was supposedly a complete rewrite and thus I had to recreate my toggles. At one point while using the "Screen always on/off" toggle (in the on position) my phone became unresponsive. After a battery pull and reset I was still experiencing issues. Mainly that the camera app wouldnt open and I couldnt toggle the flash on. I was already planning on doing a factory reset so i pushed up the schedule, backed up my data and went ahead with that. However, after the reset my camera app still won't load. I figured a factory reset would return the OS and the stock apps to their default state but apparently not. Unless of course the error is somehow in the hardware now which would suck.
Anyways my question is this: Where do I go from here? What do you think the problem is? Anyone see any red flags waving violently in the wind?
Thanks in advance for any light you may be able to shed on this issue.
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
patrioticparadox said:
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
Click to expand...
Click to collapse
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware. Make sure you wipe data and dalvik a couple times and go to mounts and storage and wipe system too. Do those a couple times, I always do just to be sure it works. Then after that try to flash another ROM stock or custom doesnt matter. This will help a lot.
Just a recommendation, I use and LOVE Codename Android Rom. Very very fast and stable with a lot of features.
Anyways, post back when you wipe everything out and flash a new ROM on there and let me know the outcome.
nothing yet...
myboyblake said:
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware.
Click to expand...
Click to collapse
Just finished flashing the 4.1.1 back and still the same issue (did all of the data wiping). I'll try a custom ROM now though I doubt its going to make any difference.
What in the world has got a hold of my camera?
No dice
"Unfortunately Talk has stopped responding" on the first screen. "Gallery has stopped responding" when trying to open Camera app.
So despite several wipes and two distinct ROM flashes (used PARANOIDANDROID the second time) my device is still acting up.
Please help me out people. What is causing this error that is lasting across ROM flashes? What can I try to resolve this issue?
Rewiped everything and reflashed PARANOIDANDROID (2.23) just to be sure and still the camera doesn't work
seems like perhaps the registers ended up in an odd state.. know this is for a different phone, but you might give it a shot..
http://www.droidforums.net/forum/dr...amera-app-stoped-working-wont-initialize.html
---------- Post added at 05:03 PM ---------- Previous post was at 04:46 PM ----------
Looks like OMAPFlash can do a full reset on all the camera registers from looking at:
./Targets/Definitions/definitions_omap4.txt
in the OMAPFlash zipfile..
It might be worth a shot..
Slide opultl
No dice... I assume you were referring to clearing the cache and data. I had tried this before but gave it another shot anyways. In case you meant the screenshot part, I did that too and the screenshot captures fine but still the camera does not function. Also holding down the volume down and power keys never shuts the phone off I assume that is device specific (though several seconds after the screenshot captured the screen did flash off then on very quickly). I have tried disabling Gallery and rebooting in the hopes that would free up the hardware. Failed.
I am uber stuck on this.
Why is this persisting across flashes and what can I try to resolve it?
edit: just noticed that the bottom of your post was more info and not a signature. I'll look into that. Ran out of "thanks" for today but I'll get you yours
Since it won't delete....
As an update: I have tried contacting both Verizon and Samsung about the issue. Both recommend returning the device under warranty (as was expected). This would be fine except that I LEARN NOTHING! If the Samsung techies have a protocol/enumeration/anything to discover and resolve the issue then so can I (potentially), which means the general public should have this knowledge too, right? WHAT IS MY NEXT STEP?
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Here's a link, sorry I didn't post soon - I don't check back here often..
patrioticparadox said:
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
Click to expand...
Click to collapse
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
I don't think it going to do a reg reset for the camera by default..
This is from: Targets/Definitions/definitions_omap4.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET 0x4A1000C0
It is pulled in and used by:
Targets/Configurations/configuration_omap4460_tuna_8g.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET needs to set for the correct location -- I have not done any digging, so I don't know what the location is..
Just Found this -- https://github.com/omapconf/omapconf/wiki
omapconf can be used to read/write/modify any register from within Android..
Mach3.2 said:
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
Click to expand...
Click to collapse
Insurance fraud? Um get a life! That's not why their premiums are high you ass! They do it to make more money you jack knob. My company charges $65/yr with a $25 deductible with up to 5 claims a year! That's so much better than asurion. And they give you a piece of **** replacement. Is all about money not the customer...now please me nice. Great ideas come from working together not from being an asshat!
This is a last-ditch effort to get some input before I go blow some money on a new phone. Hoping someone can help! It's possible that I haven't found an answer yet because what I'm doing is futile but I'll go through the story just in case...
Looks like quite a few internet people are having trouble with their HTC Incredible 2 cameras, and over Christmas I joined the fray. Upon launching camera or camcorder, I only see a black screen. The only thing I can think that could have prompted a camera failure was a short (<2ft) drop, but there’s no damage otherwise.
At first I tried but had no success with:
Restarting the phone
Clearing cache, clearing data, and/or force stop in Applications/Manage Applications/All/Camera/ (it’s running v3.00.000.120826.605 if that matters at all)
Restarting the phone in safe mode
Performing a factory reset
Unmounting SD card
Using diagnostic apps (some combination of doms diagnostic tools, androsensor, and msherlock) I’ve confirmed that although both front and rear cameras are recognized by the phone, accessing them for diagnosis freezes the diagnostic app. Strangely, the flash diagnostic tool freezes also, although the flashlight app works fine. Since I don’t think my drop could have busted both cameras and the flash at once, I guess there are two options: it DID wiggle loose a wire that does all the camera-related stuff, or it’s a software problem.
Since my warranty is a few months expired I figured I’d root the phone today, just to be double-dog sure it’s not something easily fixable. I followed http://forum.xda-developers.com/showthread.php?t=1931096, http://forum.xda-developers.com/showthread.php?t=1687590, used Android Commander to look at system files. On recommendation from http://androidforums.com/incredible-2-all-things-root/433350-camera-problem.html#post3361181, I tried to delete the current system/apps/HTCCamera.apk and replace with a different one; both one from http://www.teambamf.net/topic/1737-romgb-skyraider-zeus-13-inc2-update-11222011/ and also a standalone MiuiCamera.apk download were tried, but to no success.
I (attempt to) work with fortran77 during my day job so I can’t say I’m super happy to have blown a Saturday on yet more programming work. Unfortunately I’m a complete noob at this, and am not really sure how to further mess around with anything camera-related. It seems like the only thing I haven’t tried is to install a different ROM, but would it even be useful to do so? Have I missed anything? The Verizon agent I spoke to told me just to replace my phone, but since everything else works okay I wanted to be completely sure there wasn’t anything else I could do to fix the camera function. Does seem like I’m toast, though…
Thanks so much!
Excellent first post.
I have no idea how to help you. I would, However flash a ROM just to be sure. Tsm sense or andybonestock come to mind. It wouldn't hurt, you know?
Sent from my Incredible 2 using xda app-developers app
If that doesn't work try a aosp ROM like dkstunnas cm9 for a last ditch effort. I believe it interacts a Lil different with the camera then sense roms. Maybe
The camera is a replaceable part, so if you cant get it working a new one is less than $20.
Thanks for your suggestions!
I've learned a lot this week (like SMS Backup + should have been installed before the Verizon guy factory reset my phone...whoops, bye texts) and also tried to download "an app that uses the camera but not as a camera" as per http://forum.xda-developers.com/showpost.php?p=36239149&postcount=2 but that didn't work.
Looking at videos that take apart Dinc2's (http://www.youtube.com/watch?v=Qk91u3aqGAQ) I think replacing the camera would be quite outside my comfort zone...also, since both cameras and the flash refuse to work, that seems like a bigger job than I could handle. Unless they're like xmas lights where one goes out and they all go out, but still. I've only soldered maybe once in my life...
On to ROM switching, then. I used this tutorial to guide me through: http://www.incredibleforum.com/forum/htc-incredible-hacks/5514-flashing-roms-tutorial.html#post49612.
I've seen some threads about asop camera weirdness so I figured I'd try the strange one (http://forum.xda-developers.com/showthread.php?t=1932573) first. But, after a few different tries, I couldn’t get it to work…just got stuck on the white htc screen. After 25 minutes of waiting, I pulled out the battery and did the power-voldown thing to get to a menu. Then did a clockworkmod restore and tried andybonestock (http://forum.xda-developers.com/showthread.php?t=1392516) instead, which was successful in booting but not successful in starting my camera (BOO, but who is surprised). Went back to the asop a few more times (aeroevan kernel v14 and v15) as I’m thinking it has the best shot at a camera back door, but I just couldn’t get it to flash. White screen every time. I thought about doing ViperINC (http://forum.xda-developers.com/showthread.php?t=1953899) just for some variety but it uses more things I’m not familiar with (twrp? aroma? boot.img?) and I’m feeling done with this for the day. In any case it was a long shot, and if one ROM flash and a bunch of data clearing didn’t help, probably nothing will.
Looking like I may use this phone as a backup VOIP in the apartment (http://forum.xda-developers.com/showpost.php?p=34335798&postcount=20). Off to probably get an Incredible 4G LTE. Maybe all of the steps outlined in this thread will help someone with a less-severe camera issue…
Can you tell me if bluetooth is ON or OFF by default at startup after a factory reset? I swear that it was off the first time I booted up but now it is on. Makes me wonder if it was infected or changed. Anyone know if the default was changed? Thanks
Eutility said:
Can you tell me if bluetooth is ON or OFF by default at startup after a factory reset? I swear that it was off the first time I booted up but now it is on. Makes me wonder if it was infected or changed. Anyone know if the default was changed? Thanks
Click to expand...
Click to collapse
Bluetooth may or may not be "on" but it should not be "connected" or "remember" any devices if you did a factory reset.
However, without wiping internal SD and data, you are subject to "potential weird things" that can happen.
It's why I never report a bug unless I made absolutely sure to wipe data and internal SD before trying to reproduce an issue.
Bluetooth has been turned on by default for all the software versions I've used.
Upon a factory flash or reset, Bluetooth will be enabled but no devices will connect/be remembered.
On a side note, No application can "infect" an android. Most of these antivirus applications are complete bullcrap. Dont get me wrong, there are some dangerous apps out there, but you would still have to give the app permissions and accessibility access For it to do any damage. even then, simply uninstalling them Will remove everything.
Thanks for your responses. I do appreciate it. Well, unfortunately I have had multiple phones infected by ex-neighbors. I literally would lose control over the phone and during calls they would make beeping sounds like I had hit a key. Once I flashed my phone outside of town and they kept messing with it. I had always thought they had a tool which enables persistence even through flashing, but it may be that they are using Signaling System 7 (SS7) and are just reinfecting them remotely. (you can watch a 60 minute special on SS7 if u like, available online) They were using an IMSI catcher when I lived next door to them. With the Pixel XL I was having ALOT of data use and reset the phone after some weird stuff happened that I had come to recognize as likely signs of being compromised, and I think put in a new SIM with a new phone #. It was much better after that. It was a nightmare with them and one of them even followed me home after work a month after I moved away. Not to mention steal things like laundry soap and put them on their side of the street in front of my house. Creeps. At this point it is just pathetic and weird. Just trying to take reasonable precautions now and live my life. If they want to waste their time that is sad.
Really glad to hear the bluetooth being there is not a deviance from default. Thanks