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.
Ive sort of tried to search this one (How do I search JUST the Epic 4g section of XDA??) and found no one describing this problem the way I do...
This is my second time having this issue, and the fix for it last time was a pain in the ass, so id like a new fix-
Every app, every aspect of my phone, continuously resets/reloads. This is most noticeable with Hancent SMS, as it saves a message as a draft when you close out of the app... Well, right now, ill be typing and "message saved as draft" will constantly pop up at the bottom of the screen (about once every 2 seconds), and the phone will lag and it will erase 1 or two characters(making me look like I cant type :silly: ).
If this was the only problem, maybe I could live with it, but it affects everything. Launcher Pro randomly/continuously resets. The notification bar often resets while trying to pull it down. The phone app will close or freeze as soon as I start receiving a call. Sometimes it'll play my ringtone without a way for me to answer, other times I never knew I missed a call unless they leave a voice mail... And sometimes its worse than others, sometimes its fine for an hour, then something goes stupid and even a reboot doesn't help. For instance, right now, it was happy. I launched aLogcat to check it out and now the screen orientation REFUSES to stay one way. Even setting the phone down, it switches directions every few seconds, which makes aLogcat reload and therefor its unusable.
I haven't mentioned what im running because Ive had this exact same issue on a totally different rom, almost a year ago, but im running-
build - SleeperROM_3.0.0_FC09
kernal - 2.6.35.7-Shadow-FC09_v1.0
baseband - S700.0.5s.FC09
firmware - 2.3.6
Ive had this happen on EB13 on the EpicExperience ROM too.
SOO, if anyone has advice on how to fix this, id be extremely interested.
On the other hand, last time I had this issue I was convinced it was a corrupt piece of memory somewhere early in the OS, something I corrupt during install, and I went ahead and reflashed and wiped and reflashed and wiped and returned to stock and etc. etc. etc... and that seemed to work... actually, I dont know exactly what part of the process fixed it, thats why I do not want to repeat it unless I have to... BUT, if someone would like to explain/point me in the right direction. I'd like to know how to DELETE AS MUCH AS POSSIBLE and FLASH as CLEAN as possible. (that is, if no one else knows of a fix for my problem)
thanks all!
Err, well only thing I can think of is a truly clean install using Odin. This means do not restore any data from backups. Then slowly begin installing applications 1-by-1 through the play store website (for speed sake) to see if your issue creeps up again.
It also couldn't hurt to format your SD card too. Corrupt data on the SD card can cause some wonky things at times.
get another device...i hope u have the equipment protection plan
Thanks for the advice guys OFF TO THE ODIN MACHINE! haha.
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!
Hey so my speaker phone is always on whenever I make or receive a call. I've gone through every single setting, made sure no apps are installed making it default to be on (voice recorders, GPS apps, ect) yet it is always on?
Anyone know how to fix this? Is there some app that I can install that can force it stay off unless I turn it on?
Some people say its the phone thinking its in dock mode. Is there any way to disable that?
This is driving me nuts. I've tried pulling the battery, rebooting and nothing is working.
Thanks for the help!
Is there some app that I can install that can force it stay off unless I turn it on?
Click to expand...
Click to collapse
You shouldn't need an app to do what the phone already natively "normally" does. More than likely, some app you installed is causing your problem. Even if you disable apps to not have speaker on by default, perhaps the app cache settings are still affecting your phone.
If you're still agonizing over this problem by the time you read this... I would clear all the app cache, clear data on each installed app, disable all installed apps (force stop), and if that doesn't work, back up your data and factory reset. More than likely a factory reset will get your phone working correctly again. A pain, I know, but... better than going nuts! Good luck!
Yeah I've gone through every conceivable app that would have anything to do with my speakerphone and it hasn't helped. I'm afraid to do a factory reset because I honestly don't think it is going to fix it. I'm starting to think more and more that it is a hardware issue with the USB port and not a software issue. I may have to go to a Verizon store and see what they say. I'm sure once the guy can't figure it out he will tell me that I have to factory reset it at which point I want to make say if it doesn't fix it, I'll need a new phone.
So annoyed it's not even funny.....
UPDATE:
Ok so I still can't figure out what it is, I've cleared all data and cache on all apps (including the phone app) but nothing seems to help.
For ****s and grins I wanted to see if I plugged in my headphones what it would do. When I plugged them in and tried to make a call, this time the speakerphone button is NOT illuminated BUT.........IT STILL PLAYS THROUGH THE SPEAKER PHONE AND NOT THE HEADPHONES????
I know, mind...blown.
Now if I push the speakerphone button, it turns green (on) and the sound still comes through the speaker phone but if I push it again, it turns off and now the sound plays through the headsets.
What on earth is possibly going on??? Can the phone dialer app be corrupted? What else can I try other than a hard reset? Is there a way I can reinstall the phone dialer app?
I know you stated you looked at all the apps you could, but did you look into the S Voice settings to see if Auto start Speakerphone is enabled? Supposedly it'll be used only when S Voice is used, but who knows when something might be corrupted.
Already tried that, didn't fix it. Even tried disabling Svoice.
I also booted up in safe mode and it still was doing it so I know it isn't any installed app that I have that is doing it.
At this point I think have no choice but to do a hard reset unfortunately. SO incredibly annoying.
Well, I hope you solve the problem. At least with the hard reset you'll get a clean start. Nah... nothing good about a hard reset! Damn annoying! Let us know how you solved it once you get it going.
Some background info.
I bought my pixel XL from the Google store and I believe it came with the 63L build out of the box. I have since made it a point to completely wipe and fastboot flash the latest image Everytime an update is release, right now I am on the 26U build. The only thing I have done to my phone (and these bugs happen before and after) is bootloader unlock and root.
The bugs.
Every once in a while, my volume controls will quit working. I notice it happen more if I cast to my Chromecast and play a song or video (seperate) on my device. I'll hit the volume button and literally nothing will happen. To fix this I usually have to turn the display off, wait a few seconds, wake it back up, then the controls work fine again. I do not believe it is a hardware issue because i can fix it Everytime it happens.
The second bug, probably the most annoying, is that my nav bar will become completely unresponsive occasionally while in landscape orientation. Say I'm watching a video on YouTube in full screen, if I swipe to pull out my nav bar and hit the home/recent/back button, nothing will happen. I will see the animation however no vibration (feedback) or a action occurs.
This happens in games, YouTube, web browsers, doesn't matter as long as my phone is in landscape mode. Also note that when this happens, my device refuses to rotate back to portrait. This leaves my only solution (same as the volume bug) to turn off the display, wait a few seconds, and then I back on. Sometimes, however, this don't even work, and I'll have to jump straight to settings from my lockscreen to force the phone to portrait where the functionality of the nav bar returns.
I've contacted google, they run me through the typical steps "delete cache, have you tried a reset, update to the latest software", but nothing fixes it. They have told me repetitively it's not a common problem and it's not a problem that's worth rma'ing over.
I've been discovering my pixel has many small issues that no one else has. Such as the horrible transfer speed explain in my earlier thread, these bugs above, refusing to charge when the device is off, etc.
Has anyone had similar problems?
@noidea24,
I've had none of those issues. In fact, my Pixel XL has been flawless.
Not good. I guess I'm going to try and force a RMA.
noidea24 said:
I've contacted google, they run me through the typical steps "delete cache, have you tried a reset, update to the latest software", but nothing fixes it. They have told me repetitively it's not a common problem and it's not a problem that's worth rma'ing over.
Click to expand...
Click to collapse
Sorry to nit, but when I read the statement above I can't help but wonder if you actually did a factory reset. Reason I say that is you stated "have you tried a reset" and you didn't explicitly state that you did.
I kind of doubt the responsiveness stuff you're referring to is hardware related, it's probably software.
Whether or not a rogue app is affecting your device or a root app is impossible to determine without doing a factory reset and carefully adding one app/change at a time until the problem comes back. It's a PITA but that's what I'd do first to rule out hardware, and I'd simply run email and messaging apps unrooted for at least 24 hours to rule out hardware issues before I start loading up my favorite apps.
muzzy996 said:
Sorry to nit, but when I read the statement above I can't help but wonder if you actually did a factory reset. Reason I say that is you stated "have you tried a reset" and you didn't explicitly state that you did.
I kind of doubt the responsiveness stuff you're referring to is hardware related, it's probably software.
Whether or not a rogue app is affecting your device or a root app is impossible to determine without doing a factory reset and carefully adding one app/change at a time until the problem comes back. It's a PITA but that's what I'd do first to rule out hardware, and I'd simply run email and messaging apps unrooted for at least 24 hours to rule out hardware issues before I start loading up my favorite apps.
Click to expand...
Click to collapse
A factory reset is far from a pain in the ass, and yes, i have done it many times. the only things that makes it suck is when i have to transfer files back to my device because (as mentioned) i have terrible transfer speed from pc to device.
i have literally done everything i can to make this devices worth the price, and things are only getting worse. Since the post (later that night) i factory flashed once again, and re locked the bootloader. No root, No extra apps, hell, the only apps i had on my phone to begin with were facebook messenger, and that pixel car racer, i dont use anything else. ive had an even worse bug come in where my phone completely freezes when opening google camera and swiping to the video section. ill have to hold power until it force resets.
ive been with xda since my Motorola droid, Ive built roms for the community for my lg g2 and my nexus 6. hell, i even built kernels for my 5x (not public), so im a little past your average user complaining about some things that dont work due to user error. these are legitimate device flaws and malfunctions, and i was simply asking if anyone else has experienced them. and since it seems no one has, i have deemed my device faulty. now i have to come up with $600 for a service hold to get it replaced.
My experience with Googles first official flag ship has been pathetic, and im hoping that this replacement device i get (eventually) will persuade me not to go back to my 6p.
Well if that's the case then yeah I hope a replacement device will solve your issues. Sounds like it will.
Didn't mean to rile you up, just looking for clarity.
Good luck!