Database Develop

Home and search button's not working

Hi, I have an AT&T Nexus One, running FRF85B currently. As of lately, even before update I noticed my home and search button stopped working. The haptic feedback responds when I touch them but they don't do anything. I searched the forums so please don't flame me if I missed a thread. Much thanks to anyone that can help!
P.S. I soft reset the phone a few times and also have reflashed

can you post a logcat of what happens when you press the buttons? and also try wiping cache and dalvik cache

Try to wipe and reflash and post logcat

Gfs stock phone just started doing this. Will try to get some kind of logs... A reset wouldn't make her very happy, fffuuuu

http://www.google.com/support/forum/p/android/thread?tid=3c3ae39887a83bbc&hl=en
&
http://code.google.com/p/android/issues/detail?id=8503
according to this we arent the only ones. it looks like a factory reset can fix the problem, but some on the link above re-encountered the problem weeks later.
surprised XDA hasnt run into this before...
in addition to home/search buttons haptic'in but not doing anything, slide lock screen goes away and the phones cannot receive calls.

Those buttons are programmable, maybe some app took control and does nothing ?A launcher perhaps?

'Programmable'? How can I set Search to ixquick?

Quantumstate said:
'Programmable'? How can I set Search to ixquick?
Click to expand...
Click to collapse
The app's manifest needs to mention that it can handle that event

britoso said:
Those buttons are programmable, maybe some app took control and does nothing ?A launcher perhaps?
Click to expand...
Click to collapse
doesnt make sense though, everyone that has had this issue had all 3 completely unrelated issues:
1. buttons vibrate, do nothing
2. phone cannot receive calls
3. lock screen disappears
a wipe fixed it last night but man it was a ***** to reinstall everything for her.

turbosix said:
doesnt make sense though, everyone that has had this issue had all 3 completely unrelated issues:
1. buttons vibrate, do nothing
2. phone cannot receive calls
3. lock screen disappears
a wipe fixed it last night but man it was a ***** to reinstall everything for her.
Click to expand...
Click to collapse
This is exactly what is happening to me. I'm going to wipe now.

god damn it. this **** just started happening again... n1 has been running the OTA stock GB 2.3.3...
we ended up getting HTC to warranty the phone and everything was fine until this morning..
any help?

same
So i started having this problem about 3 weeks ago as well right after i flashed CM7's newest experimental build. first thing I witnessed was not being able to receive calls. I figured that this was a problem with CM7 and flashed modaco's r26, after a full wipe, when it just came out a few days ago. After a day, i got the problem with the lock screen and the home and search buttons not working. I again thought this was a problem with gingerbread for some reason and flashed MIUI Mod Rodriguez style rom, again full wipe. I had restored everything through titanium backup and other forms of recovery and within about 60 minutes my home button and search keys stopped working.
So I finally figured that it was some settings that I must have adjusted and carried through numerous different ROMs that caused the problems. So next time around I didn't restore anything, running on MIUI mod, and didn't restore anything for the remainder of the day to see what happened. Low and behold, after a reset the problem came back. One other complication is that the phone will always forget my google account and i'll have to re-connect it. Then I realize that the home key doesn't work. So even not importing anything from my old Rom's with a clean wipe didn't get rid of it.
I still get haptic feedback, but the buttons just don't do anything. I changed the setting for how home and search respond in both scenarios and can't get any response either. I flashed back to an old version now and so far i'm alright. But if someone can figure out why this is happening that would be awesome.
For the other people who are having this problem, when you're doing a clean wipe are you then restoring things back via titanium back up or otherwise? and when did you first start to experience these problems?

Istarted having this same problem today. I recently flashed over to cm7 rc2 and then the same thing happened. It seems like after I do a titanium backup and then change a setting it will reset to the cm boot screen and when it comes back there's no home screen or search buttons. All the same issues. Haptic feedback works but nothing happens. I'm on an evo btw.

Same thing occuring for me after flashing CM7. Reverted back to Miui, but so far no luck in fixing this. Numerous factory resets have yet to resolve as well. This is pretty frustrating...

Having this issue as well on CM7. DEFINITELY Titanium related.

I had this problem too. I just had to shut down the phone then leave it for about 10-15 minutes then turn it on again. Everything should be fine again. ^^

issues with rooted g1 (cm4.2) - calls to voicemail and unlock

Hi there,
So I rooted my phone about a month ago and installed an older version of cyanogen mod because I wanted 1.6 for the navigation. So I installed cm4.2.15.1. It worked fine for quite a while, then I had a few issues so I wiped and reset up the phone.
Now I am having a few issues...
-the phone's home button won't work (although I can boot into recovery mode with it so its still functional)
-calls are being sent straight to voicemail after ringing once and I do get a VM notification right after ( I checked my settings and I dont have call forwarding on)
-when I hit the red power button it should sleep. however it sleeps and wakes at the push of any button as opposed to the normal requirement of pushing menu to unlock
-when i hold down power red button there is not an option for airplane mode or I believe there was another option there too. It only shows reboot or power down
I think those are the main issues right now. I have a 16gb SD (class 2, I know its slow but i havent had any issues) with apps2sd running automatically b/c i have it partitioned. I did a backup and restore using nandroid but that didnt help.
Basically I hear I should reflash it but I am not sure I want to do that. Will I lose all my apps and stuff? I was thinking maybe they would be saved b/c of apps2sd but I dont know for sure. Also to reflash do I just do wipe at the recovery screen and then like reinstall CM again after putting the zip file on the SD card?
Also what is the latest version of CM with navigation? Where can I find that file? Is there another mod that you guys would recommend? NOthing too flashy but I do like lots of customization, navigation. BUt my highest priority is navi and just being quick and reliable.
Sorry for being a n00b. I tried searching but did not find a concrete answer..
Thanks!

bueller?
HELP

[Q] Htc Dream: Can't receive calls; home and call buttons dont work

I've searched with google and on these forums, but still haven't found an answer to this situation. Here's what I'm seeing and I'm not quite sure how to make of it.
This is on a rogers htc dream with the ebi1 port of roms. I've had 2 different roms with the same incident.
Main symptoms:
- Home and call buttons don't work
- Holding power button only gives reboot or power off
- - power off actually reboots
- can't receive calls. calls in go straight to voicemail
I had this happen on an éclair build after a long usage time(9 months?) and clearing davlik didn't work, so doing a full wipe + install fixed the issue. The new rom i used was cyanogenmod 6.1 with froyo, and everything worked fine after install. However, after installing all the apps back in, moving some to sd, getting gapps synced up correctly, etc etc, and rebooting, the same symptoms reappeared.
This seems to be some kind of issue with the phone module (is there such a thing?). I've ruled it out being a button hardware issue since the buttons feel and work fine in recovery and when i had the clean flash on. This happened on two different roms with two different android releases, so I'm thinking it's either an apps issue or some other kind of configuration issue that causes the phone functionality to partially disappear.
The only solutions I've found is to fullwipe and install, but i've tried it and it repeated itself after first reboot. So I won't go down that route just yet.
I'm not familiar with android but is there a way to access any kind of logs or how to do some debugging to figure out why these functions are missing?

[Q] nexus one have no sound ~~help

who can help me ,my nexus one can not make any sound,

I'm not sure if i can help you.
But I'm pretty sure anyone who does needs a little bit more information.
Is your N1 rooted or not? If yes which Rom do you use?
What happened before it stopped making sounds?
I could imagine that could be usefull for people trying to help.

Make a complete wipe and see if it helps

Hi!
Initially had this issue when I bought my N1 (a store sample) and it re-surfaced a week ago. Now this is from experience only, so I'm not pretending to know whether "your N1 fails to initialize soundboard for reason X"....
Issue that I solved succesfully is this:
I had no sound from the phone speaker (no ringing, no alerts, no music) - and actually all phonecalls were also silent (and ended up rebooting the phone about 15 secs into the call). What's freaky is that I was able to play music, hear alerts, take calls etc. over my headphones!
I was suspecting something to be wrong with the ringtones from the SD card.
So before wiping your phone (even with nandroid recovery it's a b*tch of a job) try this: Reset all alert tones to some default tones (which are in the rom). Turn N1 off, remove SD & sim, then let it reboot. Then power down, insert sim, keep SD out. Reboot. You should get the tones/sounds/in-call audio back after a few tries of these combinations. You can also try unmounting/remounting the card repeatedly. Also, it may help if you have a second SD card ready (empty or without). When you get the sound back, you can again start using your custom tones off the SD card.
(I usually wipe any unused ringtones in the process, and have even removed the tones from my card, and then reinserted them on the SD, which also seems to work after a few power-down/power-up cycles.)
Sorry, it's totally "unscientific" but if you have, say, half an hour to a full hour to spare do the above and your N1 will be back on track.

Pistolero0 is right we could use a little more info. Another thing that I would like to know is can you play sound through the headphone jack or Bluetooth or is it just the phone speaker.

Uh-oh... Just when I answered, I got the same problem again. This time, it's taken me a day to cycle/recycle. I've gotten the sounds back twice, only to lose them due to a random re-boot. I'm still suspecting it's a question of the SD notifications/ringtones messing up something in the system. (Or it's due to a certain app getting installed or uninstalled.)
So, the sound sometimes comes back, sometimes doesn't.
So, I'm also asking for help on this one....
Symptoms
No in-call audio whatsoever
No audio through internal speaker (the ear-speaker)
No audio through the speakerphone-speaker (on the back)
No notification sounds, no alarm sounds, no ringing.
Music cannot play (the track doesn't seem to advance).
All audio works over bluetooth headset - I can hear notifications/ringtones/alarms, screenlock sound, and even music (winamp & stock).
However, I still cannot make a call over BT (I do hear the ringing, but the audio doesn't connect on an incoming call. Outbound calls are completely silent on BT phones as well.
No sound whatsoever over the standard plugin HF-headphones (the ones that came with the N1).
So my plea is also, how do I fix this? (Wiped & Nandroid-backuped once, but the problem resurfaced, so I don't think that's the thing, then).
EDIT: Now trying the passimg method (FRG83-->GRI40-->root-->GRJ22+SU.zip) - I guess I should have done this aways back, (like 3months ago when I got my N1) but didn't.
There we go, froyoed for a while

EDIT: Now trying the passimg method (FRG83/D/G --> GRI40 --> root --> install GRJ22 update + SU.zip via clockwork) — I guess I should have done this aways back, (like 3months ago when I got my N1) but didn't.
There we go, froyoed for a while
Click to expand...
Click to collapse
What a bummer... Froyo, but NO sound. [O]I guess it is a hardware thing then after all, despite all the evidence I've seen so far?[/O]
RESULTS
Some hours later am now back on rooted stock GRJ22, but still no sounds. This must then be a hardware thing - albeit one that doesn't manifest itself always.
Suspecting something is wrong with the 3,5mm plug? (Or a wire is crossed somewhere, which silences the ear-speaker and speakerphone speaker alike).

Still suffering. Anyone got an idea?
Did anyone get their problem solved?

Well I've never had this problem but can I ask you a question when you flash do you use 3X system wipe and 5X data/cache wipe because I don't really think this is hardware cause or else in theory if it is hardware the problem should stay even after a reflash unless it is consistent with something else (example every time you hit X amount of memory used, every time you hit X amount of run time, etc).
So try the 3X system and 5X data/cache and see what happens.

Dude Random21 said:
So try the 3X system and 5X data/cache and see what happens.
Click to expand...
Click to collapse
You mean first do the system + data/cache wipes, then flash?
By system wipe, you mean the usual reset-to-factory status kind of wipe?
And how do you proceed with the data/cache wipe? Like, with Titanium or some other choice?
Sorry for the n00biness, I try not to flash schtuff too often. Anyway, I'm going to try your suggestion out as soon as I can.

Sorry for the late reply I haven't had much free time lately but why I say system wipe I mean either use temasek system wipe (if on Amon RA) or the built in wipe system option in clockwork mod depending on your recovery. And for data/cache that is the factory reset.

Update - One Factory Servicing Later, a fix of sorts
Okay. After two weeks of consternation I walked to the service center.
6 wks later (that would be today) I got my N1 back....
Motherboard had been replaced, rigid flex had been replaced, antenna had been replaced. Warranty repairs on level 1 & level 2 had been done. Anyway, quiiiiite happy now.
And yes, I do have sound. Luckily, I was still within warranty, and will continue to be. Lovely.
(Presently going back the FRG83 - FRG83D - FRG83G - GRI40 (gingerbreak root) - GRJ22 route).

Ear speaker stopped working after update to 5.1

Well I updated my Moto X XT1092 to 5.1 yesterday. Since then, the ear speaker has stopped working during both incoming calls and outgoing calls. I can hear everything clearly while on loud speaker, however i can't hear a thing while enabling the ear speaker. The person I am talking to can hear everything though. After the update, i cleaned the device using clean master. I haven't done a factory reset yet and haven't done anything in the recovery either, hoping there is an easier fix to it. Can anybody help me fix it?

I am having the exact same issue. But in my case the earpiece worked initially and suddenly stopped working from yesterday. I tried rebooting the phone as well as rebooting in safe mode. Both didnt help. I also tried to clear the cache and data for the phone and dialer app, which didnt help either? I am planning to do a factory reset. Will that have any impact? I was on 5.0 pure edition when i sideloaded the 5.1 soak LPE23.32-14.

I forgot to mention that the earpiece worked initially in my case too. I did make one phone call and everything was fine till that point. And then it all started few minutes later. I did an ota update and I really wasn't expecting such issue. So if clearing cache and the dialler didn't help you fix the issue, I guess our only option is to factory reset. Let me know if factory resetting fixes the issue.

rectifyy said:
I forgot to mention that the earpiece worked initially in my case too. I did make one phone call and everything was fine till that point. And then it all started few minutes later. I did an ota update and I really wasn't expecting such issue. So if clearing cache and the dialler didn't help you fix the issue, I guess our only option is to factory reset. Let me know if factory resetting fixes the issue.
Click to expand...
Click to collapse
The factory reset didnt help too. Still having the same issue after factory reset

http://salloiacono.com/2015/02/27/fix-unable-to-hear-calls-on-moto-x-2nd-gen/
Well, i found this link and it gives instructions on how to fix the earpiece issue...I will give it a go later. I am very surprised that factory reset didn't help either.

rectifyy said:
http://salloiacono.com/2015/02/27/fix-unable-to-hear-calls-on-moto-x-2nd-gen/
Well, i found this link and it gives instructions on how to fix the earpiece issue...I will give it a go later. I am very surprised that factory reset didn't help either.
Click to expand...
Click to collapse
This didnt help either, Still the issue persists even after following every steps on that tutorial. Let me know if you have any luck with that
UPDATE:Finally got it working after updating to the latest build 23.16.3 posted in the general section

Nothing has worked for me so far. Is your phone xt1905? Well mine is xt1902 and I had updated it through ota before the entire issue started, and the build is 23.16.1. So I guess I'm already on the latest build. Do you have any suggestion regarding what i should do?

Hi,
I am also facing the same problem. I just updated my phone to 5.1 and now my ear speaker is not working one thing i noticed is if i connect a headphone, i am able to hear the sound, but the internal ear speaker of the phone is not working
Have anyone found any solution for it ?

Ear Speaker stop working after 5.1 update
Hi
I am also have same issue of ear speaker after 5.1 update.
I have done cache clear it doesn,t help.
I have done factory reset thrice my Moto X2.
After reset ear speaker start working but when i update pre installed apps then again ear speaker stop working. I have done it twice.
Third time i have reset my phone and now i am not updating any app.. its working fine..
Please help me to get out from this issue..
thanks

Ravneet Lohchab said:
Hi
I am also have same issue of ear speaker after 5.1 update.
I have done cache clear it doesn,t help.
I have done factory reset thrice my Moto X2.
After reset ear speaker start working but when i update pre installed apps then again ear speaker stop working. I have done it twice.
Third time i have reset my phone and now i am not updating any app.. its working fine..
Please help me to get out from this issue..
thanks
Click to expand...
Click to collapse
Someone over in the Motorola forums suggested checking to see if hearing aid compatibility was enabled in the settings of the dialer, and disabling it if it was.

Resolution for earpiece not working after 5.1 upgrade on moto x 2nd gen
walrusmonarch said:
someone over in the motorola forums suggested checking to see if hearing aid compatibility was enabled in the settings of the dialer, and disabling it if it was.
Click to expand...
Click to collapse
please note : Go to dialer and disable hearing aid, earpiece will start working.
No need of factory reset

I haven't updated to 5.1 and hearing aid isn't enabled.. Only thing I can think of is the dictionary update wifi required notification being the last thing that was done before losing sound in the ear piece. To remove dictionary updates is there a specific app I can clear data from?

owaismomin said:
please note : Go to dialer and disable hearing aid, earpiece will start working.
No need of factory reset
Click to expand...
Click to collapse
You legend, this worked! I've been trying everything. How the hell did they get enabled during the 5.1 update?
I found it a bit weird that it was working after factory reset and then suddenly stopped.

found this thread because my earpiece stopped working today. stock android 5.1 att moto x 2014. tried a bunch of stuff (hearing aid, wipe cache, reboot,..) didnt work. What did work for me was as simple as it gets. in my settings i turned everything off except cell signal (wifi, blutooth, location, screen rotate...) tried a call it worked. Dont know why or how but it did. havent tried turning everything back on yet. a bit scared to. Hope this helps someone.
!!UPDATE!! I do not think that helped . went out again and turning everything off didnt work.... So i back tracked to what I did before turning everything off. that step got my speaker back again for now at least. What that step was is i called my voicemail and inserted headphones in and out a couple times. I am thinking that the dialer thinks there are headphones plugged in so no speaker. I also believe it has to do with the dialer software since all other sounds and apps come out loudspeaker. using internal speaker test app internal speaker does not work when it is out. If it goes out again i will try headphones in that app to see if that resets it.
on I side note i just realized all my homescreen apps and widgets are gone. they are still installed just not on homescreen

So did anyone reach an effective solution regarding this issue or determined the root cause? It just happened to me today and i have been trying everything i have read online but nothing worked. Any help would be greatly appreciated.

what finally worked for me was cleaning headphone jack. you can do this at your own risk. i pulled most of cotton off a qtip. put alcohol on it and cleaned it. i did not think this was problem because any app that used the loudspeaker worked even calling worked with speakerphone. so my thinking was it is not dirty but i cleaned it and have not had a problem for about 2 weeks now.

affiatic said:
what finally worked for me was cleaning headphone jack. you can do this at your own risk. i pulled most of cotton off a qtip. put alcohol on it and cleaned it. i did not think this was problem because any app that used the loudspeaker worked even calling worked with speakerphone. so my thinking was it is not dirty but i cleaned it and have not had a problem for about 2 weeks now.
Click to expand...
Click to collapse
Tried doing that as well, didn't work.
Did anyone else find any solution?
I have wiped cache, cleaned the headphone jack, did the hearing aid thing.
Nothing has worked.

affiatic said:
what finally worked for me was cleaning headphone jack. you can do this at your own risk. i pulled most of cotton off a qtip. put alcohol on it and cleaned it. i did not think this was problem because any app that used the loudspeaker worked even calling worked with speakerphone. so my thinking was it is not dirty but i cleaned it and have not had a problem for about 2 weeks now.
Click to expand...
Click to collapse
Found the solution, it was water damage actually.
My mom forgot to tell me that water went in through the headphone jack.
And as water conducts electricity the phone thought headphones were plugged in. Cleaning it with a cloth and a toothpick and then shaking the phone a few times fixed it.
I think that's why cleaning your headphone jack fixed it as well affiatic, water went in probably.

My friend is suffering from the same situation.
1. Tried clearing data + cache for dialer app.
2. Hearing aid compatibility disabled.
3. Did factory reset.
Nothing has worked so far.
Can anybody elaborate the solution suggested in the below link? (Im getting 403 error opening the link.)
http://salloiacono.com/2015/02/27/fix-unable-to-hear-calls-on-moto-x-2nd-gen/
Click to expand...
Click to collapse
Would be grateful if someone could provide a valide solution.
Model :- XT1092
Build :- 23.16.3

Moriarty82 said:
My friend is suffering from the same situation.
1. Tried clearing data + cache for dialer app.
2. Hearing aid compatibility disabled.
3. Did factory reset.
Nothing has worked so far.
Can anybody elaborate the solution suggested in the below link? (Im getting 403 error opening the link.)
Would be grateful if someone could provide a valide solution.
Model :- XT1092
Build :- 23.16.3
Click to expand...
Click to collapse
Have you ever tried to make or receive a call on your Moto X and you hear nothing on the other side, almost as if there isn’t even a connection made? Then when you try to call again, for some reason it works?
If you have experienced this, you also understand how frustrating it can be when you have to hang up and dial again, just to make a simple call. This problem plagued me for months of owning my 2014 Moto X, searching everywhere for a resolution to this hugely annoying problem. It wasn’t only me who was experiencing this issue either. A friend with the same phone was having the exact same problem as I, however it was impacting them even more, since it was used for their business. At this point, I figured that it wasn’t only the both of us experiencing the issue, but potentially many others owners as well. After much more searching, I came across a similar issue on a different phone, which listed some ideas to fix the issue. To my surprise, when I completed the process, the problem was fixed and has yet to return. Here is what I did…
Fix Inability to Hear Calls on Moto X
I had tried many different things to fix this issue, such as switching from Dalvik to Art, then back to Dalvik again. Rebooting the phone also didn’t seem to help much at all. Now for what fixed the error (scroll below for the steps).
First, I wanted to clear all cache, as that can sometimes fix simple issues. After I had entered the Recovery menu and cleared the cache, I noticed the problem had stayed away for a bit longer than a reboot, but eventually it came back again. Next, I put the phone into Safe Mode. Once the phone rebooted into Safe Mode, I shut down the device and plugged it in to my wall charger for two hours. To my surprise, after two hours when I turned my phone back on and tried making a call, I could hear the other side. The problem was gone and has yet to return, months later.
Anybody that has experienced this same issue, should try the steps below. It may just make your phone much less frustrating to operate.
Putting the Moto X into Recovery Mode to Delete Cache:
1. Power off your phone, by pressing down the power button until the power menu pops up and selecting*Power Off.
[http://salloiacono]
2. Wait a few seconds, then proceed to next step.
3. Hold down the*Volume Down*for a second, the while still holding down the*Volume Downbutton, also hold down the*Power Button*for about 3 seconds, then let go of*Power Button. If you did this correctly, you will see the*Boot Menu.
[http://salloiacono]4. Press the*Volume Down*button, until you have*Recovery*highlighted. Then pressVolume Up*to select*Recovery.
5. Your phone will appear to reboot and you should see this little guy.
[http://salloiacono]
Don’t worry, you didn’t break anything.
6. Now you must enter the*Recovery Menu.
– For Android 4.4.4: Hold down the*Volume Up*button for about 10-15 seconds and while holding that down, press the*Power Button.You should see a new menu pop up.
– For Android 5.0: Hold down the*Power Button*for a few seconds and while holding that down, press the*Volume Up*key. You should see a new menu pop up.
[http://salloiacono]
7. Press*Volume Down*until you have*Wipe Cache Partition*highlighted, then press thePower Button.*Your phone will now reboot. It is time for the next step.
Putting your Moto X into Safe Mode
1. Once your phone has fully rebooted, you are now ready to put your phone into*Safe Mode. Hold down the*Power Button*until thePower Menu*pops up. Now press and hold thePower Off*button.
[http://salloiacono]
2. After a few seconds, you should see a new window pop up warning about*Safe Mode. Press*OK. Your phone will now reboot intoSafe Mode.
[http://salloiacono]
3. Once your phone reboots into*Safe Mode,Power Off*your phone.
4. With your phone powered off, plug it into your wall charger for 2 hours.
5. After 2 hours, you may unplug your phone and turn it back on. Now you should be able to make and receive calls without the issues you were experiencing before!
Hope this works as well for you as it did for me!
Verstuurd vanaf mijn XT1092 met Tapatalk