Develop Bugs

Camera stopped working

The camera has stopped working randomly. The only thing I could think of that might of caused it would be the phone some how shut down when it was in my pocket. When I start up the camera app it immediately closes. When I attempt to use Google goggles, it says cannot connect to camera. What can I do?

First off you can give us some more details as to what software you are running. Are you on a stock Sprint ROM? A custom ROM? Did you install any software and then notice this change? Does this happen 100% of the time?

I'm running the stock 2.2 rooted odexed rom. Stock kernel. And haven't installed any new software to cause this...

I've cleared cache, dalvik cache, camera app's cache and it still doesn't work...

No one has any idea? Has this ever happened to anyone else?

It happens to me on both ava stock 2.2 and now netarchys 2.2... I have to wipe everything to get it back for a few hours... it just did it to me again do you have netarchys fps fix?
Sent from my PC36100 using XDA App

This is the craziest thing ever. The camera has returned to working after 10 hours of not working. I didn't do anything to get it to return. I will be continuing to monitor the camera to see if it happens again... This is the first time it has ever happen and the first time I've been on a 2.2 Rom for a significant amount of time.

This just barely happened to my phone too! Grrrr!!!
I'm running Fresh.02 + I tried flashing several kernels to see if it would fix it but none of them helped.
kernels I tried, latest versions of: kingX, snap, netarchy
Will try to do a full wipe and flash the stock 2.2 rooted w/o any fancy mods. <--- ok this fixed it!

Does installing the 3D Gallery app cause the Sense camera app to randomly stop working?
I'm getting the same problem again on a different ROM.
UPDATE: I've uninstalled 3D Gallery & cleared data on the Camera app and it still doesn't work.

i am having this same problem. have flashed several roms with no fix. cannot pin point when this happened either. really frustrating. ive done reboots, wipe, you name it.

happened to me
blix1337 said:
No one has any idea? Has this ever happened to anyone else?
Click to expand...
Click to collapse
Yes it happened to me, but i have HTC EVO 3D i used leedriod rom and it happend exactly i changed rom to ics and still didnt work know i will call htc and ask them how to get the official ics rom after that if camera wont work i will tell them that the camera was working before i made this update and they must fix it for free

Hi guys
Any luck with this problem? I'm using a rooted xperia neo running [email protected] #2 with an unlocked boot loader - I've used Google goggles many times before and then today its coming up with "Cannot connect to camera. You may need to restart your device" and yet the camera is working because behind this pop up I can see the image that the camera is seeing. I've tried to take a screen shot of this but the screen shot uses the camera and therefore I blanks out the image through the back lens.
I've also uninstalled the app and reinstalled it - cleared all Dalvik cache - as well as moved it to SD and made it a system app - none of these trials have made any difference.

hilfordjames said:
Hi guys
Any luck with this problem? I'm using a rooted xperia neo running [email protected] #2 with an unlocked boot loader - I've used Google goggles many times before and then today its coming up with "Cannot connect to camera. You may need to restart your device" and yet the camera is working because behind this pop up I can see the image that the camera is seeing. I've tried to take a screen shot of this but the screen shot uses the camera and therefore I blanks out the image through the back lens.
I've also uninstalled the app and reinstalled it - cleared all Dalvik cache - as well as moved it to SD and made it a system app - none of these trials have made any difference.
Click to expand...
Click to collapse
Are you sure there are no problems or known bugs with the rom you are using? Have you tried reflashing your rom? (it might be a pain to do, but something in the rom might have broke and it can help to start fresh).

I never post here but I have had a problem with my phone's camera that I fix by some random thread I found a while ago so I thought I would share what helped me. The thread stated it is something to do with the camera's connection to the phone and sometimes with drops or bumps of the phone it becomes loose. All I had to do was turn the phone face down, put my thumb over the camera and press down with some force. Not enough to break it but just to reseat the connection. After that, restart the phone. I have done this a few times and it has been successful ever time. I hope you guys have the same success.
Sent from my GT-P3110 using Tapatalk 2

hippy70 said:
I never post here but I have had a problem with my phone's camera that I fix by some random thread I found a while ago so I thought I would share what helped me. The thread stated it is something to do with the camera's connection to the phone and sometimes with drops or bumps of the phone it becomes loose. All I had to do was turn the phone face down, put my thumb over the camera and press down with some force. Not enough to break it but just to reseat the connection. After that, restart the phone. I have done this a few times and it has been successful ever time. I hope you guys have the same success.
Sent from my GT-P3110 using Tapatalk 2
Click to expand...
Click to collapse
That is correct, in some cases i have found the camera has come unseated. but it could also be the board.

Camera, Gallery and Talk doesn't work

So I got the Galaxy Nexus GSM today and it's one hell of a sexy device.
It obviously came with Ice Cream Sandwich out of the box. And errors out of the box. Right when I start the phone, Talk FCs. When I try to start the Camera, it FCs.
I though "What the heck, Jellybean probably fixes that", so I unlocked it and flashed Paranoid Android. Everything is a lot faster now, but I still have the same problems, except now Gallery just crashes, which renders the Camera unusable, because they're apparently linked together in Jellybean.
I tried 3rd party apps (Zoom Camera, Paper Camera and a few others) and none of them work.
So it seems that everything that has something to do with the Camera doesn't work.
I tried everything that I could think of;
Reflashing
returning to stock
force stop Camera
Disable and enable all network related functions in G+ and Gallery
Clearing cache - both for individual apps and the option from the recovery
Trying 3rd party apps
Googling everything I could think of
Installing G+ (that made me able to open Gallery, but Gallery still force closes when I open Camera)
Changing battery
Of course I can't see it being anything but a hardware issue, but some people who have compiled CM10 by themselves have the same errors. I don't know if that helps me.
So before I return it some time this week, does any one have any suggestions to what I could try?
I'll give this thread two days before I return it.
Thanks in advance.

You rooted? If not and you know how to root, root it, replace the app (gallery, camera, whatever is not working) with stock JB version. Hopefully it's just corrupted apps... That's easy to fix

Thanks for the reply. I've already tried the Jellybean version of Paranoid Android and it made no difference.
I though "What the heck, Jellybean probably fixes that", so I unlocked it and flashed Paranoid Android. Everything is a lot faster now, but I still have the same problems, except now Gallery just crashes, which renders the Camera unusable, because they're apparently linked together in Jellybean.
Click to expand...
Click to collapse

mrhaxx1 said:
Thanks for the reply. I've already tried the Jellybean version of Paranoid Android and it made no difference.
Click to expand...
Click to collapse
Might be a long shot, but have you tried fixing permissions in recovery?
Sent from my Galaxy Nexus using xda premium

I have, but I just tried again and it made no difference.
Also, I forgot to mention that it's not a storage issue, as I can save screenshots just fine.

mrhaxx1 said:
I have, but I just tried again and it made no difference.
Also, I forgot to mention that it's not a storage issue, as I can save screenshots just fine.
Click to expand...
Click to collapse
Any solutions for this yet? having the same problem.

Nope, nothing yet.
And to make the bad things worse, I've lost the receipt. So I can't even return it.

Bumpity bump!

mrhaxx1 said:
Bumpity bump!
Click to expand...
Click to collapse
I just went ahead and called verizon.. and they're shipping me a new phone today. I see a lot of posts about this, with no solution. It'll be quicker to do it this way. Except you call whatever your carrier is. Or samsung, if nothing else.

Well, you see, I bought the phone refurbished. There was a guarantee on it, but I lost the receipt, so I can't return it or get a new phone.
I ordered a rear- and front-facing replacement camera. It should arrive in 7-15 days because I'm ordering from the USA.
I looked into it, and disassambling and assembling it should be fairly simple. Nearly the same process as the Nexus S, which I've disassembled before.
If it doesn't work, I've only lost $22 and it's not like I have a valid guarantee on it anyway.

Oh well, replacing the cameras didn't work.
And I even managed to break the volume buttons.
Even if I got hold of the receipt, there would be no way they would repair it now.
I can as well just go buy a new phone. Next month. Maybe. At least everything else still works.

When you flash ROM, do you ensure you completely wipe previous ROM and data? Also, if you use something like Titanium Backup to restore your apps after flashing a new ROM, make sure you don't restore system apps or data. That will definitely screw things up in every ROM as incompatible files are mixed.

Try doing a full wipe of your device it could help
Sent from my Galaxy Nexus using xda app-developers app

It was like that on the stock rom.
And yes, I always ensure to wipe everything. As said in the OP, I even tried returning back to stock.

I got the same problem, I GOT IT FIXED NO HARDWARE FAILLURE!!
Hi,
this is what i did, got it fresh from the box, didn't even bother to set-up, I instantly updated to Jelly Bean..
everything worked perfectly, besides the camera, it crashed instantly.. (gallery did not respond)..
i rebooted it 2 times, then pressed the Power button + volume down.. it went to an system boot thingy.. the i connected it to my pc with an usb (usb debugging enabled).
my win7 pc said the drivers were installed, then i pressed the power button. after loading. the camera worked perfect.. thats REALY everything i DID.. i'll keep you posted if it fails again.
it also worked after unplugging the usb.. Hope I helped you a bit.

I can second this fix!
IvanGrozni87 said:
Hi,
this is what i did, got it fresh from the box, didn't even bother to set-up, I instantly updated to Jelly Bean..
everything worked perfectly, besides the camera, it crashed instantly.. (gallery did not respond)..
i rebooted it 2 times, then pressed the Power button + volume down.. it went to an system boot thingy.. the i connected it to my pc with an usb (usb debugging enabled).
my win7 pc said the drivers were installed, then i pressed the power button. after loading. the camera worked perfect.. thats REALY everything i DID.. i'll keep you posted if it fails again.
it also worked after unplugging the usb.. Hope I helped you a bit.
Click to expand...
Click to collapse
So, I was having this exact same issue and was ready to call Verizon for a replacement, when I tried this as a last resort and VOILA!! IT WORKED! I am still unsure of how this all came about, but for the purpose of hopefully helping someone with the same issue, I will second this quick fix as IT DID WORK FOR ME.

I had this same problem (camera/talk fc'ed on start, whenever opening either app), tried all the fixes I could and nothing worked. I eventually disassembled the phone and used a toothbrush and isopropyl alcohol to clean the main board and the connections for each of the camera modules. After a couple rounds of cleaning, everything started working again.

navjas73 said:
I had this same problem (camera/talk fc'ed on start, whenever opening either app), tried all the fixes I could and nothing worked. I eventually disassembled the phone and used a toothbrush and isopropyl alcohol to clean the main board and the connections for each of the camera modules. After a couple rounds of cleaning, everything started working again.
Click to expand...
Click to collapse
Thanks for this information, I'll try to do it with mine too. Any results I will post here.

[Q] "Phantom Touch Input"

PLEASE SEE BOTTOM OF OP FOR UPDATES
-----
Greetings all,
[Backstory]
I've been flashing ROMs for about a year now. I started off with Virtuous Team Gingerbread and the Sense 3.x ROMS. I had no issues.
Then I moved to CM7, and MIUI, also on Gingerbread. No problems.
I've been using the CM9/CM10 ROMs since they appeared for the Incredible 2, from AOKP and Aeroevan, respectively.
Here is where the problems start.
[Problem]
On ICS and JB ROMs, I get what I have dubbed (there is probably a better name for it) "Phantom Touch Input".
At first I thought this was caused by normal bugs and glitches in the ROM. I did my best to deal with it. Usually a simple lock/unlock would solve the issue, temporarily.
So what would happen? Without touching the screen, I would get the long press menu to show up, and then the screen and capacitive buttons would freeze. Or the screen would start to slowly half scroll to the side, and again, freeze.
The most annoying part is when I am typing on the phone. I have tried other keyboards, be it from the MIUIv4, or the default keyboards of 4.0.x, 4.1, or 4.2. All the sudden random keys are pressed, and continue to be pressed, even when my fingers are nowhere near the screen.
However, no one else seems to have this issue, so it looks like I am the lone wolf here with this problem.
Can anyone provide insight? A possible fix? Or am I forced to deal with this on all 4.x ROMs?
---
UPDATE 1: Issues also occurred on CM7.2, so I may be facing a hardware issue.
UPDATE 2: Issues occurred in 4ext Touch. Looking around on YouTube, others (Incredible S users) have similar issues.
Nearly confirmed as a hardware issue.
Check Page 2 for video links.

[::AP::] said:
Greetings all,
[Backstory]
I've been flashing ROMs for about a year now. I started off with Virtuous Team Gingerbread and the Sense 3.x ROMS. I had no issues.
Then I moved to CM7, and MIUI, also on Gingerbread. No problems.
I've been using the CM9/CM10 ROMs since they appeared for the Incredible 2, from AOKP and Aeroevan, respectively.
Here is where the problems start.
[Problem]
On ICS and JB ROMs, I get what I have dubbed (there is probably a better name for it) "Phantom Touch Input".
At first I thought this was caused by normal bugs and glitches in the ROM. I did my best to deal with it. Usually a simple lock/unlock would solve the issue, temporarily.
So what would happen? Without touching the screen, I would get the long press menu to show up, and then the screen and capacitive buttons would freeze. Or the screen would start to slowly half scroll to the side, and again, freeze.
The most annoying part is when I am typing on the phone. I have tried other keyboards, be it from the MIUIv4, or the default keyboards of 4.0.x, 4.1, or 4.2. All the sudden random keys are pressed, and continue to be pressed, even when my fingers are nowhere near the screen.
However, no one else seems to have this issue, so it looks like I am the lone wolf here with this problem.
Can anyone provide insight? A possible fix? Or am I forced to deal with this on all 4.x ROMs?
Click to expand...
Click to collapse
Not exactly sure, I would say its hardware if it happens on all the roms. Have you went back to CM7 or MIUI since this problem started? I would revert back to one of them and test for a couple of days to see if the problem continues. If the problem is only active in ICS or JB then someone else will have to give you a hand on a resolution.

ThePhantom97 said:
Not exactly sure, I would say its hardware if it happens on all the roms. Have you went back to CM7 or MIUI since this problem started? I would revert back to one of them and test for a couple of days to see if the problem continues. If the problem is only active in ICS or JB then someone else will have to give you a hand on a resolution.
Click to expand...
Click to collapse
Ok will do when I have the chance.
Thanks for the speedy reply.
But let's say it is a hardware issue...
Do I unroot/restore/whatever and bring it back to Verizon?
Thanks.

[::AP::] said:
Ok will do when I have the chance.
Thanks for the speedy reply.
But let's say it is a hardware issue...
Do I unroot/restore/whatever and bring it back to Verizon?
Thanks.
Click to expand...
Click to collapse
Yes if the phone is still under warranty
I'm so fresh you can suck my nits...

Flashed CM 7.2
My home button didn't work, but that doesn't really matter.
I still experienced the same issues.
On a side note, wow CM7.2/Gingerbread is smooth....damn kernel. But stock 2.3.x is so ugly
Anyways, it seems like I should just "start clean".
I'm not sure what that entails - not just a full wipe...something more...tips?

[::AP::] said:
Flashed CM 7.2
My home button didn't work, but that doesn't really matter.
I still experienced the same issues.
On a side note, wow CM7.2/Gingerbread is smooth....damn kernel. But stock 2.3.x is so ugly
Anyways, it seems like I should just "start clean".
I'm not sure what that entails - not just a full wipe...something more...tips?
Click to expand...
Click to collapse
I use 4ext recovery myself, and I do a "full wipe" by format all partitions/factory data reset, then I see a lot of people also say wipe cache and dalvik so I throw that in as well, it don't take long but just in case a factory reset don't get them I just do it...lol. Hope that helps, and that may clear up some bugs with ICS and JB roms if you weren't doing that before. Just make sure you do a backup before wiping everything. Wouldn't want you to be without a phone if some process hiccups.

Thanks for the info.
Should I do anything with my SD card? It shouldn't affect ROM performance, but a wipe wouldn't be a bad idea, yes?

[::AP::] said:
Thanks for the info.
Should I do anything with my SD card? It shouldn't affect ROM performance, but a wipe wouldn't be a bad idea, yes?
Click to expand...
Click to collapse
I doubt that the SD card would affect the performance, but as long as you have backups of everything you can do as you please, backup backup backup. You don't want to lose everything, trust me I have seen bad things happen to guys that don't backup, and I have learned from experience as well.

Right right I know.
I'll try 4ext on a fresh ROM and see how things go.

Not a good idea to flash the touch version of 4ext in light of my issues.
Did a Nandroid, hit back, then screen input froze. The on-screen time is updating, but are the capacitive buttons are lit up but do not respond/give haptic feedback, let alone the touch screen itself. Power button just moves to the power menu, where I again cannot select anything.
Pulling battery :/
This is why I will never (want to) purchase a phone without a removable battery.
So looks like my issue isn't software related. (This issue can in no way be software related [or even caused by], right?)
I've had the phone for over a year...but I guess I'll try with Verizon.
*sigh*
What a pain.

Looks like I am certainly not alone.
(Better video) http://www.youtube.com/watch?v=25CaiveQoQg
(Similar) http://www.youtube.com/watch?v=kANVkc-Sk74&feature=related
I'm just really pissed off. And there isn't a phone in the market that I want.

That looks like possibly a bad digitizer, you can replace that fairly cheaply if you are out of warranty. That would be my best guess, and keep in mind I am no expert. Here is a link so you can see the process:
http://www.youtube.com/watch?v=LQL9gakQyuI

ThePhantom97 said:
That looks like possibly a bad digitizer, you can replace that fairly cheaply if you are out of warranty. That would be my best guess, and keep in mind I am no expert. Here is a link so you can see the process:
http://www.youtube.com/watch?v=LQL9gakQyuI
Click to expand...
Click to collapse
That is what I was thinking.
I'll also see if I can milk anything out of Verizon. I'm already an unhappy customer, given the lack of ICS, especially when promised.

Yep, digitizer.
http://forum.xda-developers.com/showthread.php?t=1399085

Good luck with Big Red, and let us know if you get it resolved.

ThePhantom97 said:
Good luck with Big Red, and let us know if you get it resolved.
Click to expand...
Click to collapse
Thanks, I'll keep everyone updated.
I'm sure I'm not the only one who has had issues. Hopefully word spreads, especially to those still under warranty who are suffering from a faulty digitizer.

I747m screen problem...please help!

Ive searched everywhere and can't seem to find anyone with a solution. Ive found a post with the same problem but no solution.
So yesterday my s3 started having problems waking up. Meaning when I lock it usually you bring up the lock screen by pressing the power button or home button. Problem is when I press either one, screen doesnt come on. The buttons do. If I tap the screen I can hear the ripple effect but the screen doesnt light up. I have to keep locking and unlocking till it finally works. Averege of about 6 tries. When I get a call most of the time the screen doesnt come on either. I can still answer since I know where the slider is. When I do turn it on everything works perfect. No flickering or any other issues. When it boots it works perfect...never fails. Just when I lock it.
I tried restoring already, thinking its a software issue...still does it. What piece of hardware could cause this? I'm stumped. Please any advice would be great.
I'm not rooted and running 4.1.1 oem rogers software.
Sent from my SGH-I747M using xda app-developers app

felcom said:
Ive searched everywhere and can't seem to find anyone with a solution. Ive found a post with the same problem but no solution.
So yesterday my s3 started having problems waking up. Meaning when I lock it usually you bring up the lock screen by pressing the power button or home button. Problem is when I press either one, screen doesnt come on. The buttons do. If I tap the screen I can hear the ripple effect but the screen doesnt light up. I have to keep locking and unlocking till it finally works. Averege of about 6 tries. When I get a call most of the time the screen doesnt come on either. I can still answer since I know where the slider is. When I do turn it on everything works perfect. No flickering or any other issues. When it boots it works perfect...never fails. Just when I lock it.
I tried restoring already, thinking its a software issue...still does it. What piece of hardware could cause this? I'm stumped. Please any advice would be great.
I'm not rooted and running 4.1.1 oem rogers software.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
My guess is that you have something draining all your RAM or being hard on your CPU. When you restored, did you factory reset?
You might have to backup your stuff, factory reset. Test it, if it still does it, bring it up with Rogers for a replacement. If it doesn't, reinstall your stuff until you find the culprit.
You could troubleshoot it also by uninstalling the latest apps you installed.

BWolf56 said:
My guess is that you have something draining all your RAM or being hard on your CPU. When you restored, did you factory reset?
You might have to backup your stuff, factory reset. Test it, if it still does it, bring it up with Rogers for a replacement. If it doesn't, reinstall your stuff until you find the culprit.
You could troubleshoot it also by uninstalling the latest apps you installed.
Click to expand...
Click to collapse
Like I said...Already did a factory reset. Meaning All apps were gone. Started fresh. Even without going through the first setup (setting up google account etc etc) if I lock the phone its hard to wakeup.
Phone is out of warranty so no go there....
I'm just not understanding what is causing it. I know the screen is fine...buttons are fine...everything points at a software problem. I found a post from a while back where someone was having the same problem....no solution was posted though. I even took the phone apart last night thinking a bad connection or something...disconnected the screen and reconnected it...didn't do anything.
If the screen was going bad wouldn't I have issues all the time? Once I wakeup the phone it works perfect...no flickering or anything. When it boots (which I've done like 30 times between today and yesterday) the screen has come on every single time perfectly fine. Everything tells me it's software related...but after doing a factory reset and running original firmware it seems as though it must be a hardware issue...but which component.
I know the phone wakes up when I press the buttons...I can see the menu and back buttons light up...and if I tap the screen the ripple sound is there...just the screen doesn't wake up....till I try a few more times....very frustrating.
Thanks Again for trying...if anyone has any ideas....greatly appreciated. I'll try and find original Rogers firmware and install with odin...see if that works....

felcom said:
Like I said...Already did a factory reset. Meaning All apps were gone. Started fresh. Even without going through the first setup (setting up google account etc etc) if I lock the phone its hard to wakeup.
Phone is out of warranty so no go there....
I'm just not understanding what is causing it. I know the screen is fine...buttons are fine...everything points at a software problem. I found a post from a while back where someone was having the same problem....no solution was posted though. I even took the phone apart last night thinking a bad connection or something...disconnected the screen and reconnected it...didn't do anything.
If the screen was going bad wouldn't I have issues all the time? Once I wakeup the phone it works perfect...no flickering or anything. When it boots (which I've done like 30 times between today and yesterday) the screen has come on every single time perfectly fine. Everything tells me it's software related...but after doing a factory reset and running original firmware it seems as though it must be a hardware issue...but which component.
I know the phone wakes up when I press the buttons...I can see the menu and back buttons light up...and if I tap the screen the ripple sound is there...just the screen doesn't wake up....till I try a few more times....very frustrating.
Thanks Again for trying...if anyone has any ideas....greatly appreciated. I'll try and find original Rogers firmware and install with odin...see if that works....
Click to expand...
Click to collapse
Sounds indeed like software issue. I'm not so sure what would cause it on stock rogers though.
Either way, you can find the stock ROM on sammobile.com or on this thread: http://forum.xda-developers.com/showthread.php?t=1822308
You'll need Odin to flash it. (It doesn't trigger the flash counter)

felcom said:
Phone is out of warranty so no go there....
Click to expand...
Click to collapse
Did you buy your phone with a credit card? Some cc's have warranty built in. Mine doubles what the manufacturer offers.

Thanks for the link. I will try it tonight and post the results. Really hoping it works.
Sent from my SGH-I747M using xda app-developers app

I downloaded the newest firmware. 4.1.2 official rogers. Problem persists. Must be a hardware issue. Thing is what could cause this? Is it the screen...is it the gpu? I imagine if its gpu the phone is only good for parts as I imagine its part of the motherboard. Oh well...might be getting the s4 sooner then planned.
Sent from my SGH-I747M using xda app-developers app

felcom said:
I downloaded the newest firmware. 4.1.2 official rogers. Problem persists. Must be a hardware issue. Thing is what could cause this? Is it the screen...is it the gpu? I imagine if its gpu the phone is only good for parts as I imagine its part of the motherboard. Oh well...might be getting the s4 sooner then planned.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
If you're down for a little test, you could try with a custom ROM.
Use the link I gave you and flash pre-rooted Rogers' ROM. From there, install TWRP (or cwm) using goomanager (from the Play Store) and flash a custom ROM as per their instructions (Don't forget the Gapps).
Before anything though, make a backup
Never know, might save you some time on that S4.

BWolf56 said:
If you're down for a little test, you could try with a custom ROM.
Use the link I gave you and flash pre-rooted Rogers' ROM. From there, install TWRP (or cwm) using goomanager (from the Play Store) and flash a custom ROM as per their instructions (Don't forget the Gapps).
Before anything though, make a backup
Never know, might save you some time on that S4.
Click to expand...
Click to collapse
Thanks. I might try it. Dont think I have too much to lose at this point. I always try and keep my phones nice so that when I get a new one I can sell the old one for good money to help offset the cost. This really messes with that system as the phone isn't worth much now...just bought an extended battery too...was planning to keep it for at least another 6 months.
Sent from my SGH-I747M using xda app-developers app

So just a quick update. For no apparent reason the phone started working fine again. It now turns on and off just fine. I'm not going to mess around with it anymore. That's really bizzare. I'll give it a couple days and will report back if it continuous to work fine or if the problem comes back. Thanks for the input.
Sent from my SGH-I747M using xda app-developers app

problem with keyboard htc one m8

after i update phone to 5.0.1 sometimes i have a problem with keyboard ,randomly they stopped work ,
when i tapping the place and keyboard should appear nothing happens.
after one or two minut going back :/
any experience with this,,
thank guys

i noticed the same thing...i had to reboot the phone few times...

Same issue here!
You can wait till christmas, but nothing works to get your keyboard back..except booting..

Yes same issue here. I've mentioned it not long after the Developer Edition received the OTA.
It's not even something that we can recreate, it's just completely random. It stays that way until a reboot and then it's fine again. Very irritating.

try to clear data in app settings, that work for me :/ 4 days no problems

vahica said:
try to clear data in app settings, that work for me :/ 4 days no problems
Click to expand...
Click to collapse
do other keyboards work?

vahica said:
try to clear data in app settings, that work for me :/ 4 days no problems
Click to expand...
Click to collapse
not an expert here; can you explain how/where/what?

Donky1973 said:
not an expert here; can you explain how/where/what?
Click to expand...
Click to collapse
go to ;
settings-apps-all-htc sense input- clear data

mxisme said:
do other keyboards work?
Click to expand...
Click to collapse
They've never worked for me... unfortunately.

vahica said:
go to ;
settings-apps-all-htc sense input- clear data
Click to expand...
Click to collapse
ah...the sense-input thing...makes sense...thanx!

No problems here.

Deleted cache but problem still occurs...randomly of course.... not that many times anymore though..

Donky1973 said:
Deleted cache but problem still occurs...randomly of course.... not that many times anymore though..
Click to expand...
Click to collapse
Hello, the same problem with the keyboard .On any firmware, I have 6 different firmware problem persists.
p . s . TEL Verizon

Still having this damn problem.. Anyone know if it's isolated to Verizon phones? I'm on Verizon 5.0.1 stock, both the HTC and Google keyboard do it. Completely random, about once every day to 2-3 days. So annoying.

I'm having trouble with my HTC one M8
vahica said:
after i update phone to 5.0.1 sometimes i have a problem with keyboard ,randomly they stopped work ,
when i tapping the place and keyboard should appear nothing happens.
after one or two minut going back :/
any experience with this,,
thank guys
Click to expand...
Click to collapse
I had a problem with the keyboard lagging which got worse after the lollipop update, I was considering a warranty claim or rooting the phone and then the microphone packed in and the decision was made, I called the network who advised me to send it to HTC for repair which I did, it also had a few sync problems too, I asked the technical support guy about this problem and he said it would have to be reflashed, I sent it to them and they did the work, replacement microphones, replacement receiver, replacement lower board, replacement rubber something or other which I was told is something under the screen, replacement camera and a few others and of course it was flashed, I got it back after 8 days expecting my otherwise brilliant phone to be as it should be as I have come to expect from HTC, I switched it on and did the initial stages of making it work, I let it restore the last backup I made (off the phone with faults) which reported had failed but it started to restore the backed up apps, settings and my contacts, everything restored to how I had it before minus a couple of apps and a few notification settings, I have been using it for 2 days now however the keyboard has not been fixed by flashing it, unless the errors could have been brought in by the restoration? I have experienced the screen freeze and start jumping, jumping to the all open apps page, keyboard lag, keyboard is inaccurate, I went into the EE shop and they said that it should go back to HTC again, I haven't tried to hard reset it and go back to the factory settings and not restore the backup image this time, I've never had any problems with the 3 HTC phones I've owned, it is a good phone otherwise

Damn, I just went back to Dev Edition and sure enough it happened to me. Has this ever been fixed? This is way too annoying for me.

Possible Fix
For what it's worth, I went into App Manager to clear the Sense Input data as suggested by a previous poster (thank you) but did not have a 'Clear Data' button. There was a 'Settings' button though where I was able to turn off HTC Sense Input, after which my Swype keyboard immediately started working again. First time I've been able to resolve this SUPER annoying issue without rebooting the phone. Time will tell if it's a real fix; I'll update this post if not.
Phone is a brand new M8, still on stock 5.0.1