Database Develop

Weird dialer problem and no hardware buttons work PLEASE HELP

I am having the strangest problem. Everytime I turn my phone off and on again the dialer starts up along with the wifi settings. On top of that none of the buttons work except the middle directional pad, power and camra button. I have no idea what is wrong. One day everything is fine then the next its not. Any help will be appreciated.

Hard Reset

I just reflashed and the problem is still there. Except now instead of the wifi setting I get the ringtone creation tool and it creates a new dogbark midi file everytime I turn my phone on and off.

Any help? I have reflashed 3 times now.

If you've done a hard reset and it still does it, it's pretty much a hardware fault by definition. Return to vendor!

hicks said:
If you've done a hard reset and it still does it, it's pretty much a hardware fault by definition. Return to vendor!
Click to expand...
Click to collapse
Not true at all. If you were to flash to another ROM, I'm prtty sure it'd be gone. It's more than likely a softare related issue and check your start-up folder to see what it has there.

I was, perhaps incorrectly, assuming the OP was on original ROM as he didn't detail what he had changed to

I was on L26 diamond V4 when it started up. Then I flashed to V9....then I restored all my settings and rom back to the original ATT and I am getting a new replacement phone today lol Thanks to everyone who responded.

dtjunkie07 said:
I was on L26 diamond V4 when it started up. Then I flashed to V9....then I restored all my settings and rom back to the original ATT and I am getting a new replacement phone today lol Thanks to everyone who responded.
Click to expand...
Click to collapse
ouch... I don't think that solution will work for me.
Mexy

same problem here with L26 v12 the hardware buttons sometimes don't work they work fine after softreset!

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. ^^

screen freezes when i wake my phone

Ever since i manually updated to frf91 sometimes when i try to wake my phone my screen freezes an i can't unlock it also when i try to power my phone back on it will vibrate 7 times an it wont come on. I guts take the battery out an put it back it to get my phone to turn back on. I've never had this problem until i manually updated my phone. I did a factory reset an it helped for a while but the problems come back. Has anyone had this problem an does anyone know how i can fix this? I'd really appreciate any help i can get

Help please

Is the bootloader unlocked?

this seems to be a common issue with FRF91, although most people's phones will unfreeze after a minute or two, does your backlight turn on and off when you press the power button?

Jep4444 said:
this seems to be a common issue with FRF91, although most people's phones will unfreeze after a minute or two, does your backlight turn on and off when you press the power button?
Click to expand...
Click to collapse
whether it unfreezes after a minute or two depends on what it's doing..there have been many times where i have to pull battery...........

rensky said:
whether it unfreezes after a minute or two depends on what it's doing..there have been many times where i have to pull battery...........
Click to expand...
Click to collapse
ya i have had to as well but most of the time it wakes just fine

No my bootloader is not unlocked an yea the backlight will come on but it won't unlock. Ive never tried waitin a min to see if it fixes itself i just usually pull the battery when it happens an sometimes when i try to turn my phone back on it does the 7 vibrating thing. Like i said before it never happened until frf91

I have an app called AutoKiller installed. It tweaks the Android system's inner memory management routines. it was set to something other than default. I changed it back to default, and haven't had a problem since. if you have this installed, maybe try and switch it to default settings.

Sounds like a data issue. A factory reset only wipes user data, You must wipe in recovery to wipe rom data. Also make sure you have the correct radio for the build especially coming from lower build. If that's the issue flash radio first to support the build. Then flash the rom.
Sent from my Nexus One using XDA App

How do u wipe in recovery? Yea im a newb lol

Also if i wipe in recovery will i still be on 2.2 or will i have to update to it again?

[Q] Soft Keys Not Working

This is my second SGS with this problem and I am trying to determine if it is common or if I am just monumentally unlucky.
During normal use the bottom soft keys (menu and back) will become non-functional. One will stay lit and one will go out, but both will cease to work. Everything else on the phone is still responsive, sometimes the keys 'revive' themselves after a short period of time, other times I need to lock the phone to get them back.
I got this phone (a replacement) on the 6th, and this started on the 12th and has been happening more and more often ever since. Has anyone else seen this or have an idea what it may be? Or is this phone is destined to be my 2nd DOA in a month?

Here is a video showing the problem: '
you tube.com/watch?v=1s-wqWsHaIs

That is definitely not normal behaviour.

Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s

hol17 said:
Exact same problem here; it seems to happen when I'm using the phone quite a bit but when I leave the phone alone for awhile, problem seems to go away then return because I'm using it too much.
// galaxy s
Click to expand...
Click to collapse
FYI: Samsung support told me to return my phone.
It is almost like one of the soft keys gets stuck 'down', because it is the same behavior if you just hold down one of the keys. Mine seems to happen more when bluetooth is on and it comes and goes in spurts; good for an hour, bad for an hour, etc.
ETA: I am sure now that the soft keys are getting 'stuck down'. I have seen it 3 times now where I would press the left soft key and the light on the key will remain out, then after a second or so the quick search screen comes up and the left soft key light is still out.

any solution to this problem? i seem to have a slightly different issue
this just happened to me recently everything was working fine until this morning when i tried to press the menu and back buttons it wouldnt work, although the buttons light up and is registering my actions when i press them the light turns off and let go is lit up again.
could this be a software issue or something conflicting with my lednotification mod?
please reply ^_^

I've got the exact same issue with my soft keys getting stuck too. Just started a couple days ago, phone's less than a month old. I was also told to take my phone in for repairs.
Oh one tech support guy told me that Froyo might fix it... I'm kinda hoping for that, seeing as how this issue isn't exactly 100% reproducible for the warranty service department

I have the same problem its almost like the soft key is being held down, anyone find a fix for this?

Add me to the list
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!

robcarey said:
Add another one to the list. I too am experiencing this problem and I'm unfortunately screwed because of it. I attempted to return the phone, however the store in question refused to accept it because they tested it and found it had been unlocked. Two week old phone on stock FW bought outright ($600) and they won't replace it.
Unbelievable!
Click to expand...
Click to collapse
Lock it back and go again.

I know this post it's a bit old, but i was harvesting the web looking for an answer to my problem that seems to be the same posted here.
I have a i9000T with eclair 2.1 and soft keys get stuck now and then. I couldn't find a way to reproduce this behaviour.
Recently (yesterday) i flashed a new 2.3.3 firmware hoping this curse to end. The problem seems to persist, but in some situations that i asume for a bad flashing (i didn't repartition neither wipe the phone before flash).
Anyway, can anybody tellme if this is a software or hardware issue? I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.

cknu said:
I'll have to return my phone or this is going to be 'fixed' with a nice flash?
Thanks.
Click to expand...
Click to collapse
Only one way to find out mate.
You need to flash a 2.1 rom that consists of 3 files. 512 pit and re-partition.
Should get you back on track again.

I did flash it again with the 2.3.3 JVH, a few moments ago. Also did a repartition and wipe data and cache. It seems nice, but in a few minutes the same happend. Now, when i press the menu button it takes a nice screenshot of the phone. xD
I need to flash to a 2.1 version? Why is this? I thought flashing with any rom will work.
Thanks.

Solution to this problem!
Hey all - I found a solution to this problem - I can confirm this has fixed the problem on TWO phones for me - read the whole thread as this fix doesn't like custom firmwares, but works fine with all the regular FWs I've downloaded.
Works perfect - and simple fix!
http://forum.xda-developers.com/showthread.php?t=869492

^^^
Do not do this unless you have a i9000m. You will break your buttons.

electrotune1200 said:
^^^
Do not do this unless you have a i9000m. You will break your buttons.
Click to expand...
Click to collapse
Too bad i didn't see this before
I have I9000T used this 2663 method and now my soft buttons doesn't work anymore...
Didn't find a clear solution in the forums so i want to ask, like i said my phone is a I9000T with official 2.2.1 (UBPJA) rooted using SuperOneClick and unlocked editing the nv_data.bin file.
I was thinking on doing a hard reset to get back to the factory defaults but i see many ways of doing it that it gets confusing... i see peolple doing it through the privacy menu but i think that only erase data and doesn't restore anything OS wise, also see other people doing it using volume + home + power and selecting later clear storage, i think this is the same that the option in the privacy menu, and finally i see some people typing this code *2767*3855# what is the proper way to get back to the original OS in my case?
Thanks in advance...

[Q] Screen not waking up while on phone call

Hi,
I have a brand new Xperia SP, manufactured on 2013/W50, so it's really new. It contains the latest stock firmware.
After I start or answer a call and put the phone to my ears, it's screen doesn't came back and remains off until the call is ended by the other party. No matter if I'm moving the phone away from my head, not even the hard buttons are turning the screen back on. The touchscreen is not working either. It's just stuck as if it's near to my head. I can't even hang up the call...
It happens about 80% of time. Sometimes it works as expected without any problems. Happens more often when having an incoming call after a longer period (30+ mins) or if the call takes more than 1 minute (auto screen disable time?).
As a workaround, I turned on the function that power button hangs up call, but I cannot use my touchscreen while call.
I checked the proximity sensor with the phone's diagnostic function and with cpu-z and the sensor is just working fine 100% of the time.
Is it a known bug or a hardware problem? Does it have a workaround?

hmmm
carlosmeldano said:
Hi,
I have a brand new Xperia SP, manufactured on 2013/W50, so it's really new. It contains the latest stock firmware.
After I start or answer a call and put the phone to my ears, it's screen doesn't came back and remains off until the call is ended by the other party. No matter if I'm moving the phone away from my head, not even the hard buttons are turning the screen back on. The touchscreen is not working either. It's just stuck as if it's near to my head. I can't even hang up the call...
It happens about 80% of time. Sometimes it works as expected without any problems. Happens more often when having an incoming call after a longer period (30+ mins) or if the call takes more than 1 minute (auto screen disable time?).
As a workaround, I turned on the function that power button hangs up call, but I cannot use my touchscreen while call.
I checked the proximity sensor with the phone's diagnostic function and with cpu-z and the sensor is just working fine 100% of the time.
Is it a known bug or a hardware problem? Does it have a workaround?
Click to expand...
Click to collapse
I have the same problem. It is one of the few bugs in 12.0.a.2.254 build. Guys using unofficial release of 4.3 are not facing such problems. I suggest you to wait for the official 4.3 update which will be released soon according to SONY. :good:

really?
madhukarmohan said:
I have the same problem. It is one of the few bugs in 12.0.a.2.254 build. Guys using unofficial release of 4.3 are not facing such problems. I suggest you to wait for the official 4.3 update which will be released soon according to SONY. :good:
Click to expand...
Click to collapse
thanks!
so, this is surely a known bug in the 254 firmware? I'm just wondering because I asked this on other xperia sp forums but no users complained about it.
is there a workaround for it?

yes
carlosmeldano said:
thanks!
so, this is surely a known bug in the 254 firmware? I'm just wondering because I asked this on other xperia sp forums but no users complained about it.
is there a workaround for it?
Click to expand...
Click to collapse
Yeah, few r experiencing that. i hv seen complaints in sony blog and here too. I asked this question few days back. but, I didnt get reply.

I experienced this problem once.I think it was fixed after performing a SEUS repair...Not sure though :silly:...
Try performing a factory data reset on even reset app datas

thx
UltraWelfare said:
I experienced this problem once.I think it was fixed after performing a SEUS repair...Not sure though :silly:...
Try performing a factory data reset on even reset app datas
Click to expand...
Click to collapse
thanks to both of you, I'll do factory reset and repair via PC software, and some more factory resets. that should solve the problem.
I'm wondering why an out-of-the-box phone needs a reset, but let's see

carlosmeldano said:
thanks to both of you, I'll do factory reset and repair via PC software, and some more factory resets. that should solve the problem.
I'm wondering why an out-of-the-box phone needs a reset, but let's see
Click to expand...
Click to collapse
Don't forget to backup.First of all clear the data of the Settings -> Apps(or reset them)

UltraWelfare said:
Don't forget to backup.First of all clear the data of the Settings -> Apps(or reset them)
Click to expand...
Click to collapse
thanks. I won't backup as I installed only a few apps and the phone is almost factory state. but I'll do everything else.
hope it works. thanks to all, I'll report the results.

carlosmeldano said:
thanks. I won't backup as I installed only a few apps and the phone is almost factory state. but I'll do everything else.
hope it works. thanks to all, I'll report the results.
Click to expand...
Click to collapse
I hope everything goes fine

no success
I reset applications, did a factory reset, reinstalled phone's software with sony pc application, checked after each step, but no success...
sometimes working, sometimes not (mostly not) but the proximity sensor works fine.
out of ideas...

carlosmeldano said:
I reset applications, did a factory reset, reinstalled phone's software with sony pc application, checked after each step, but no success...
sometimes working, sometimes not (mostly not) but the proximity sensor works fine.
out of ideas...
Click to expand...
Click to collapse
Bring it to a sony service(or how's it called to your country)

it seems it's related to deep sleep. when I am called after the phone was left for 30+ minutes, it's more willing to not turning on the screen, but it turns it on after a while if having a long call. when I start the call, it mostly works. not always, but most of the time.
so it seems it's not sensor-related but something like the software is bugging.
what I don't really understand, why the hardware buttons are disabled while phoning when the phone is put to the face. it'd be enough to code that power button turns on/off the screen no matter what the proximity sensor says. I'd program it like that as a backup solution.
I wouldn't send it for repair, here in Hungary I always hear that mobile phone services just reinstall software and don't care about testing or finding the problem (if not deterministic), and do it again and again while you get tired and accept the failure. yes, it's sad but in the time of MNCs, the user doesn't matter at all after bought the product.

carlosmeldano said:
it seems it's related to deep sleep. when I am called after the phone was left for 30+ minutes, it's more willing to not turning on the screen, but it turns it on after a while if having a long call. when I start the call, it mostly works. not always, but most of the time.
so it seems it's not sensor-related but something like the software is bugging.
what I don't really understand, why the hardware buttons are disabled while phoning when the phone is put to the face. it'd be enough to code that power button turns on/off the screen no matter what the proximity sensor says. I'd program it like that as a backup solution.
I wouldn't send it for repair, here in Hungary I always hear that mobile phone services are just reinstall software and don't care about testing or finding the problem (if not deterministic), and do it again and again while you get tired and accept the failure. yes, it's sad but in the time of MNCs, the user doesn't matter at all after bought the product.
Click to expand...
Click to collapse
Try flashing custom firmware(not sure if it will work try it)...
If it doesn't work again then it's a hardware fault and not a software bug

UltraWelfare said:
Try flashing custom firmware(not sure if it will work try it)...
If it doesn't work again then it's a hardware fault and not a software bug
Click to expand...
Click to collapse
yes, that's another option. the other option is to cry off from purchase (I can do it within a week), they return the money, and I buy another one. I'll see as this is not that disturbing problem and I have no other problems with the phone like wifi bug or anything else.
someone said it's a bug so I hope 4.3 next month will solve it.