home/menu/back/search buttons dont work at all - G2 and Desire Z General

My dad's G2 after the gingerbread upgrade started to act dumb, now the home/menu/back/search buttons dont work at all, I did factory reset, cache cleaning, erased sd card and nothing! I have been looking on google for solutions and nothing, but I have found some people having the same issue after update

same here
mine stoped responding
all four capacitive front buttons are dead

I'm having the same issue, except my phone was already rooted and running CM 7.0 without any issues to report. I have barely been using my G2 lately because I have an iPhone 4S as well for work, and it gets much more attention these days. I just noticed today that none of the aforementioned buttons work at all any more, even after reboots. Tried reinstalling, upgrading to CM 7.1, even tried MIUI's latest to see if it was some software glitch, still nothing. It just seems so weird given nothing else is wrong with the touch screen at all.
I've done some searching as well and haven't been able to find any solutions for this issue. Anyone have any updates? Is this simply a hardware issue?

mine was doing that with the tiamat kernel

hey for those that have this problem and are using cm7 try using zdunes patcher to get the tablet buttons

Related

Camera Problems

Hey guys, none of my cameras are working. When i hit the camera button the camera app turns on but the screen is white. I've tried searching but everything comes up related to a discolored camera. Ive tried flashing many roms, fixing permissions, tapping on the camera. Any help is appreciated. Thanks.
Do you have an Evo 4g? You said you "hit the camera button" but the Evo doesn't have a hardware camera button.
If it's happening across multiple roms, including stock, it's probably a hardware problem.
Sent from my PC36100 using Tapatalk
oxxomxxo said:
Hey guys, none of my cameras are working. When i hit the camera button the camera app turns on but the screen is white. I've tried searching but everything comes up related to a discolored camera. Ive tried flashing many roms, fixing permissions, tapping on the camera. Any help is appreciated. Thanks.
Click to expand...
Click to collapse
You haven't flashed a Froyo kernel on a Gingerbread ROM, have you? The issue you describe is a well-documented side-effect of doing just that. If not, I would flash back to stock and see if it works. If it does, then you know it's a software issue. If it doesn't, then I would agree with plainjane.
Did you ever get a working answer to this? I'm having the same problem. My camera won't open, it force closes before going anywhere beyond a black screen. The night before, it would at least open. The front facing camera worked but the rear facing camera seemed stuck on solarize (which I had no options to change). Seems like a software problem so I updated to the latest deck rom, updated hboot, pri, nv, wimax - now fully updated and still no fix. Tried installing miui apk and still same.
If I don't get this camera fixed, I'll have to unroot. Not looking forward to doing that but if it's between having root or camera, I'm going to pick the camera.
Hope someone can help before I have to go to such drastic measures.
midian42 said:
Did you ever get a working answer to this? I'm having the same problem. My camera won't open, it force closes before going anywhere beyond a black screen. The night before, it would at least open. The front facing camera worked but the rear facing camera seemed stuck on solarize (which I had no options to change). Seems like a software problem so I updated to the latest deck rom, updated hboot, pri, nv, wimax - now fully updated and still no fix. Tried installing miui apk and still same.
If I don't get this camera fixed, I'll have to unroot. Not looking forward to doing that but if it's between having root or camera, I'm going to pick the camera.
Hope someone can help before I have to go to such drastic measures.
Click to expand...
Click to collapse
Rooting won't break your camera.
I would flash back to a rooted stock ROM, and confirm whether camera works or not on it. If it does, then you know the issue is in fact software related (which it doesn't sound like it is). If it doesn't, then you have a hardware failure.
A corrupt sd cars gave me the same problem. Try re-formatting it.
Sent from my PC36100 using XDA App
I took it to Best Buy and they told me it's a sensor issue. My phone gets replaced so it's all good.
Thanks for all the suggestions. I tried them all before deciding it must be a hardware issue and going to BB.
I know this is a few months late, but I recently had a similar problem. I would click the camera icon and the screen would just go black and then f/c on me. I was running ICS roms, so I flashed to Decks GB rom, Mik 3.1 rom and had the same problem. So I figured it was a hardware problem.
I decided to open up my evo and take a look inside and found the camera housing was not seated completely. Pushed it back down and it has been working for days now
I guess it probably jarred loose when I dropped it or bumped it or something.
Thought I would share, because it was very frustrating for me, so I figured it might be bothering someone else.

[Q] Camera problems.

Hello
I have been having some problems with the main camera on the A500. It has different tints to it. Sometimes the picture seems to be divided in 4 and all 4 squares have a different hue to them. Restoring to factory settings seem to take care of it for a while. Initially I thought it was "skype" that messed it up, but it is not.
I just restarted the tablet and the camera is giving me a yellow tint, with a clear horizontal stripe about 3/4 inch wide through the middle.
The tab has stock 3.2 on it.
I was wondering if anyone has experienced similar problems and if there was a solution to the problem.
Thank you
Well, I would think the problem seems to be some app/apps you have installed. Based on when you do a factory reset, it goes away.
I would just do another factory reset. Then verify it went away. Run it for a couple of days WITHOUT installing any apps. This will probably rule out a hardware issue.
Then install apps, 1 at a time. Use the camera, and look for issues.
Thanx. I will give that a try.
I traced it back to Swift Key X keyboard for tablets. How is that even possible?
Also yahoo messenger is another one that ruins the camera. As soon as I install any of those apps and reboot, the camera is back to normal.
Does anyone out there use either of those apps?
mobilebone said:
I traced it back to Swift Key X keyboard for tablets. How is that even possible?
Also yahoo messenger is another one that ruins the camera. As soon as I install any of those apps and reboot, the camera is back to normal.
Does anyone out there use either of those apps?
Click to expand...
Click to collapse
So, everything is ok?
Rule #1,
Stay away from apps meant for phones.
Yes, they "may" have tested it it on "1" tablet, then gave it a clean bill of health. Maybe.
Moscow Desire said:
So, everything is ok?
Rule #1,
Stay away from apps meant for phones.
Yes, they "may" have tested it it on "1" tablet, then gave it a clean bill of health. Maybe.
Click to expand...
Click to collapse
I thought it would be ok. But after restarting a few times, the camera colors are off. I'm going to root and install a custom 3.2 to make sure it is not the hardware.
Spasiba for all your help )
any news about this problems.
it seems that my iconia has the same problem- i never noticed it because i dont use the rear camera.
i sold it it today and the guy who bought has described something like what you folks are talking about
the strange thing is that i had done a clean boot before i sold it, and the buyer hasnt installed anything on it yet.
im waiting to hear back from him after he tries another clean boot.
anyone else have any ideas ?
I'm having the same problem. I don't use it much, but the camera was ok before. When I tried using it this weekend, it showed colored translucent squares on the sides. It is not a config problem, as there are no effects turned on. The front camera works 100%. I will post a sample when I get home.
If I change the "whites" config to Incandescent, it kind of solves the problem. Sometimes, the squares appear, but not for most the time.
I believe this is not a harware issue, unless that whites configuration is made with hardware (highly doubt it). I don't have Swift key, or Yahoo messenger, or any other apps that use the camera (other than Skype, but it was already installed when the camera worked).
Did anybody find a fix to this? It seems it is only a problem on stock 3.2.
Edit: not an exclusive 3.2 stock issue, it appears that custom roms have this problem as well.
I have the same issue after ICS ota upgrade...
Any ideas?
I haven't had the issue since the ICS upgrade. Only tested once or twice, but it is working properly.
What I did to partially fix it was changing the White Balance to "Incandescent".

My home button stops working after a while (CM10.1/Franco)

hello fellow xda-ers
I recently updated to the latest and stable CM10.1 (after using M2,M3, RC3 and RC5) and noticed that my home button stops working after a while. I'm not sure when it started but I think it was with the RC.
I did a search but it didn't yield anything particularly relevant. Is that a known problem?
I just reinstalled everything after resetting all data and it still happening.
thanks in advance for your input,
n
edit: before someone mentions it, I read this thread:http://forum.xda-developers.com/showthread.php?t=2340170 where the user indicates that re-flashing everything and restoring his apps using TB fixed the problem. That's exactly what I did but the problem persists unfortunately.
edit2: the problem seems to be limited to when the app drawer is opened. Home works fine with apps
same thing is happening to me. i was running cm since i bought the phone in February. Decided to flask Franco and now I'm getting this weird touch screen problems. The bottom row where the home button is located will become unresponsive. I decided to go into developer settings and enable "show touches". My phone is sometimes touches without my physical input.
Not sure if kernel related or if my touchscreen coincidentally has given out. I'm gonna try flashing stock kernel and see if that fixes things
nks2105 said:
edit2: the problem seems to be limited to when the app drawer is opened. Home works fine with apps
Click to expand...
Click to collapse
I have the same problem on
Franco M3 and CM10.1 stable, just I'm not sure if it started when I flashed CM stable or Franco M3. Home button doesn't work with app draw open and also it doesn't swap from one homescreen to the default.
However if I got to settings>Launcher>Homescreen>Default screen and change it to another screen then back again the home button works properly but after a few days it stops again.
edit: its as if it just forgets what screen is supposed to be default

SM-N900W8 & CM11 M12 bugs and issues :(

I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.
I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app

TouchScreen Calibration

Hi guys something has happened to the touch at the top of the screen its about an inch off too high. I tried flashing and wiping even went back down to lolipop but nothing is working.
How exactly does the touch key study work ? Like if its off how does one recalibrate it ? Its almost like the top menu bar has been disabled somehow...
Its a MTCD-Sofia MCU-HXD2.15 currently on 5.1.1
Cheers
Same problem here, did you find a solution?
I'm having a similar problem on lots of different vehicle where the touchscreen calibration is off while in maps and Waze. It worked as recently as 3 weeks ago and I've tried rolling back Android auto versions and no difference.
I've read on other forums that reducing the screen resolution on your phone will fix the issue, hopefully an update will provide a full fix at some point.

Categories

Resources