Hello,
today i had a mistake and a little bit cola got on my xperia. It seems like only some drops got on the display.
But 2-3 hours later I recognized that the left button is pressed automatically [the Touchflo Tabs go to left but nothing is pressed] and sometimes when I push the Powerbutton the left softkey is pressed too.
Could this two things be in a combination?
I tried to hard- and softreset but except the 1234-method nothing works, I think because of the keyproblem.
What to do now? The guarantee doesnt affect on "water"damage - right? Or isnt this a waterdamage and a known other bug?!?
I have the same problem. If I press the powerbutton, it calls somebody.
sometimes in middle of an call, it puts on hold, sometimes by its self it opens contacts... I think its the optical joystick thats have gone crazy to.
I spilldes coffe on my x1 =(
i feel with you :/
i´ll try to send it to sony ericsson support, because it was only some drops...maybe they doesnt recognice the waterdamage and will repair it on guarantee
but my biggest problem is: i´m using a custom rom...how can I set the device back to an original sony rom without pressing the power button + volume down? because this doesnt work....
when trying to connect the phone with the pc and hardspl it it stocks on the "loading..." screen
lol, kind of the same thing happened to me, but not just drop a complete glass of coca cola soaked my xperia, after drying it i had kind of the same problemas, the calls where answered automatically (no, i didný had that option on), some buttons where auto pressed randomly and of course my slider was sticky.
Regardless all warnings i didn´t desarm my xperia and just turned on right away and runned as much programs as i could so it could get as hot as possible, and after that it started working normal again, and until now (2 months) i haven´t had any problems.
Just my experience.
Sorry for the english
that sounds for me like a prety good tip...i will try it as soon as my xperia is back again
i sent it now to sony ericsson...the man at the hotline says "it sounds like a softwarebug"...maybe they doesnt check whether there is water/cola inside and repair on guarantee....
otherside i can live with it...its only bad because i cant make a rom upgrade and the screen doesnt turn off(=shorter battery life)...but it still works...
sugar is the killer
spill coffee in your keyboard and you may get it to work again
spill coffee with sugar in your keyboard and it will never work 100% again
Related
hello! i've searched but didnt find any help with my problem. When my jasjar rings (incomming call) and after i press the answer button (the green one) i need to wait about 1 to 2 seconds before i can hear the person that is calling me...strange...did this ever happen to you? how can i solve this problem? Thanks in Advance
Yes, i have the same problem on my MDA Pro
After pressing the green button, i have to wait 3 secounds with speaking.
I had the same problem and now is solved.
In phone/options/band select WCDMA (not automatic)
i think that didnt solve the problem...sorry...thanks
I have the same probelm on the incoming call. However, i finally realized that it's the problem on the Pocket Plus V3.0.4 installed on the system.
It appear to be normal once i removed the program.
It's the case for me, and i hope it would help you as well
I too have this problem with my I-Mate Jasjar. I need to wait for a few seconds after hitting the answer button before I can hear the calling party. I did a hard reset and installed the latest wwe ROM available on clubimate site. The problem still persists even without any third party software installed. So I do not blame pocketplus for this problem. I think this is a software/hardware issue which should be addressed in a ROM upgrade.
I have the same problem with my JasJar. I have also updated to the lates ROM from clubImate by advice from clubImate support.
Sometimes the phone does not even answer the call at all when pressing the green button. This is becoming an even more expensive phone since I have to call back so many people on account of missed calls
Seriously, It cannot be right that a problem like this exists on a phone in this price range. ClubImate support even said they had never heard of this problem before.
i did a few hard resets and the problem persists without any extra software installed. "Very bad bug". i've already test a K-jam and it works beautifull...i'm sad
Got my XDA Exec today. It's pretty good but is not the same as my XDA2. Even less phone. More PDA...
If I turn my machine off in landscape mode and then close the lid with the screen out (like the XDA2) then when a call arrives it takes ages to answer because the screen has to rotate first to portrait mode.
If I turn off and close in laptop mode (landscape) then it rings immediately and I can answer it immediately using the hinge buttons.
Maybe it is the same for you?
i have noticed it seems to be quicker to goto portrait than to landscape in all respects of use
ok, lets try it...thanks
how i test it: jasjar "on" charging, open in portait mode. same delay.
L to P is roughly twice as long for me.
going to L i get twist and flip and the display is done ready and waiting
going to P i get twist and flip then get a 2s ish of L before it flips to P
this was battery power
*** its the same on mains and battery !
Carnivor said:
L to P is roughly twice as long for me.
going to L i get twist and flip and the display is done ready and waiting
going to P i get twist and flip then get a 2s ish of L before it flips to P
this was battery power
*** its the same on mains and battery !
Click to expand...
Click to collapse
When my Exec is on, the rotation is pretty much instant. I have no apps running. It's only when a phone call wakes it up that the rotation is slooooow.
My Qtek 9100 also take app. 5 sec before it rings, and the S100 I had before was the same. My dad has an XDA mini, same problem. It seems like pocket plus will increase the problem, but even without any extra software its not working perfect. Its strange after such long time, they havent been able to solve simple problems like theese.
I also get this, Its very annying. Maybe they incorperated it so you can answer the call asap and the before it acually picks up, you have a few seconds to turn the screen round and see whos calling ect?
I have an Exec and there is certainly a knack to answering a call on it, but i'm getting better!!!
Firstly the voicemail seems to kick in way too early, i only get 4 rings of the 'ring' ringtone max before the VM kicks in, sometimes i think it is less, but i may just be going deaf! does anyone else find this a problem?(not deafness)
As i usually have the exec closed in my pocket, this is how i answer a call.
1, Hear the first ring, if i don't it's too late already!
2, Drop everything, and remove phone(ha!) from case and open into laptop mode only. If i rotate all the way into PDA mode the screen takes too long to change and the call goes to VM before i can see who it is.
3, Answer call after seeing who it is
4, Rotate or close screen and put to my ear and wait 2 seconds to speak.
It's a real pain in the arse and very annoying.
Great forum btw, it's been very helpful, i knew bugger all about PDAs three weeks ago.
Ian
Which button(s) do you have success with?
The small green on the side,
the green above the other keys on the keyboard,
the soft key button,
or touching the screen?
ipanter said:
...
Firstly the voicemail seems to kick in way too early, i only get 4 rings of the 'ring' ringtone max before the VM kicks in, sometimes i think it is less, but i may just be going deaf! does anyone else find this a problem?(not deafness)
...Ian
Click to expand...
Click to collapse
If you're using the Exec on o2, you can adjust the cut-in delay at the o2 end. You do so by keying in/sending the following to o2:
**61*901*11*xx# [send]
(where xx is number of seconds, e.g. 30.)
Note: I think the maximum delay allowed is about 30-secs - at least I've never got it to extend longer than that!
I have found that o2 occasionally reset mine back to about 10-secs, so have it programmed into a contact number.
HTH
I've found something interesting.
I tried to swap two sim cards.
<boring>
The one originally in my phone was a sim card from Orange Denmark (where I live). Orange has since been bought by Telia, and this same sim card is now using Telias network. This is by design. It gives my the roaming symbol all the time since the buy-over.
To say the least, some things have been very ****ty in this process, so I thougt that I might try another sim card.
</boring>
I had another one from TDC (another danish operator), and bang! My Universal (Jasjar) answers instantly - every time - on all the buttons!
Could some of you who have this problem as well, please confirm this? Please tell what kind of sim card (and country) you are networking through, and try another one.
Hi Guy's
I am getting annoyed with Internet Explorer. It keeps opening when I recieve a call. As I end the call there is a pop up box asking if I want to connect. I allways say no and then close IE. Does anybody know how to stop IE doing this as it is a pain. I only want to open it when I want to go on the internet and not on almost every call.
TIA
this could be a dumb question, but are you accidentally pressing the IE button with your cheek when you make a call?
Maybe not such a dumb question, considering where the button is it is possible the when i put the phone to my ear it does touch my cheek without my noticeing it. I will experiment.
if it is the case is ther a way to dissable that button
TIA
I cannot imagine that is the case; you have to press the button pretty hard (on my device anyway); I think you would hurt your ear or at least hear the "click" if you happen to accidently pressing the device that hard to the ear.
Martin
believe it or not there have been multiple TyTN users that never noticed the top rocker button... and there have been more than a few complaints about IE and Mail starting in the middle of a conversation...
coincidence? Methinks not...
My TyT sometimes srarts up IE for no apparent reason... ummm... Holy Crap! That bar over the lights is a rocker button? Crap, I've been using this thing for over three weeks and never knew about it. Thought the drawn on icons were just to represent the lights (internet happens to be above the WiFi light). Wonder how I missed that, considering I have read the entire instruction booklet.
Hi Guy's
Well I have solved my problem with IE, as goestoeleven pointed out I could be pressing the "WnW" button by mistake. Well I had a call today which I did not put the phone to my face but used the speaker, yep it still did it.
The problem I found was not to me pressing the button on the phone but putting it into the case supplied with the phone. As you can see the buttons are slighly raised (this does not help).
Every time I put the phone into the case, because the lid has two strong magnets it slaps shut quite hard. This force causes the button to be pushed in and thereby starting IE. This tends to happen mainly if the screen is facing out.
I thought it was every time I answered a call that IE started but it was already on from the last time I put it in the holster.
To resolve this make sure the screen is facing inward so the magnets are on the back, this should reduce the impact.
But!!! I supposed if you have the phone on the holster and nock into something this cauld also trigger IE.
It would have been better if the button were recessed then it would not happen.
I hope this will solve this issue for some of you at least
P.S. This will might also answear the "Mail" starting on its own as the button is also on the same rocker although this has not happend to me...
mutsoft said:
phone on the holster
Click to expand...
Click to collapse
Its a phone not a gun :lol: :lol: :lol:
This problem has happened to me a few times and ive put it down to me touching the wnw button at the top when taking the phone out of the case.
For the past couple of weeks. I have notice losing button functions when my phone is on landscape mode (keyboard out). This slowly progressed and I have lost the directional keys the other day. Today, I slide out the keyboard and the screen blacked out. But it still works when I slide in the keyboard and use the xperia in portrait. I packed it up and called the service center for pickup and repair. Hopefully, when I get it back in a few days I will still have the interest like when I got it early December.
did you try hard reset yet ?
I haven't done hard reset, let me try now before the service comes over.
Yes, still the same after a hard reset. Even on bootloader mode, the screen slowly dies when the keyboard when slide out
Hmm
Sounds like a power management problem, like the voltage regulation is screwed or something, sliding out the keyboard tries to pull power and the voltage is dropping elsewhere killing your screen. And of course if the keyboard can't be powered properly, it wont register button presses.
Most certainly a hardware problem, they'll have to replace the circuitboard or whatever relevent part controls voltage levels I'd guess.
SE replaced my phone
Wow, glad to hear it!
Hi my mogul has been randomly dieing on me lately, i would turn it on and call someone talk and hang up, then 2 minutes later i would try to turn it back on through the power button because it hibernates or something and it just wont let me, i would have to take out the battery and put it back in, i cant even press the reset button or anything. i dont understand! thank you in advance for any replys!
oh yea, i know the phone is on because i see the lights flashing, but when i try to call it rings but thats it, it doesnt even show up as a missing call when i take out the battery and put it back in.
Try to reflash your rom. Or maybe a replacement is necessary
Idk if this is the same as what happened to you but something like that happened to my phone. The buttons would light up and the screen would just turn a light black but wouldn't show anything. If it is, I sent it to HTC and they fixed it for me for free; when I got it back it slid easier too, it had gotten a little harder to slide after I dropped it once.
Okay I wasnt going to post about this cause there have been way too many posts and alot of back and forth and debates and even flaming, but I stumbled across something that I think is the cause for MAJORITY of the issues with why we keep having this happen. It Happened to me Today, and I Found the cause.
Before ANYONE Flames me for bringing this up, READ the post, Remember I solved the cause of why it happens to most of us, I dont take responsibility if you choose to take it upon yourself to fix it! And I know 90% of the users are going to tell me I'm wrong or I dont know what I am talking about, so be it.
If you have nothing to add other then flaming the post, just hit the back button and be on your merry way and pretend you never saw it. But I am 98% sure I am right about why its happening!
So if your interested read on:
I actually for the first time had this, and I know this is going to get flamed but its not the Screen thats the problem. And I think (BIG IF) that the dreaded unresponsive screen issue that we keep reading about Majority of them I think is not the screen.
I have 2 HD2s and both have worked flawlessly without any problems, but today I was playing with my test phone that doesnt get used that much and I noticed after installing a new rom that my screen after I played with it for a bit went black (sleep) and when I woke it up it wouldnt respond, first thing that crossed my mind is I just lost my digitizier, and started wondering okay why, I went as far to re-flash WinMo stock HD2 rom, same issue, so I decided its time to find out exactly whats causing this, and I found it. I wasnt going to make a post again cause I figured people would be "Not another thread about this" but I know whats causing the screen issue, at least this is my suspicision and I have temporarily fixed mine.
The problem is HARDWARE, The Culprit: THE END KEY (Red Button)! The Answer to "How or Why": The "End" key is used to turn the phone on and off or to put it in sleep mode, it is the most used key out of all 5 keys, it is used probably 7x more then all the rest, Its used for just about everything, now how does this cause the unresponsive screen? Easy, the phone lock or sleep is associated with this key, Its the only way to make the screen go off other then waiting for the time out period. Because by habit we mostly hit the end key to turn the screen off the phone automatically associates this with locking the phone, once that happens the screen becomes unresponsive because of several reasons: 1) The contact under the actual key has dirt which causes the button to stick in the down position, 2) the contact is bent which the "end" key is pressing down on the contact which is making contact with the board and causing it to be unresponsive, 3) The contact is worn. This is the reason why if you press the end key a few times (anywhere between 2-10) and then try the screen responds, this is cause your "unsticking" the key which then lets the screen respond.
Most of us when we hit the end key press to the far right to avoid hitting the back key (The button with the left arrow) which causes the end button to lean toward the right. But you can wake the phone up with the other 4 keys to the lock screen which will allow you to unlock the phone. As a temporary fix for myself, on my test phone I now make sure to press on the left side of the key to prevent this from happening, since its a test phone I'm not worried, but the real solution is to take the phone apart and clean the underside of the end button, and the actual contact with alcohol to remove the build up of dirt and whatever else. And also if the contact frame is bent to GENTLY bend the right side back up alittle to stop it from happening, or sending it to htc and letting them fix it.
We have to RE-TRAIN ourselves to start using the other keys to wake the phone up and not rely on the end key so much.
Hope this helps anyone finally why we have this problem. And if it works for you then hit the Thanks button
I completely agree with you. I've had the "dead digitizer" since December. It was pretty apparent it was a hardware key problem, as I could generally solve the issue by pressing the "Off" button to turn the screen off, and then one of the other keys (usually the back button, but occasionally one of the others) to wake the screen up, and the digitizer would be alive again.
As I am still under warranty, I sent mine off last week, and expect to hear back within a few days. But if I had the confidence to open it myself, I was sure it would be fixed with a good clean.
Anyway, thanks for crystallizing all this into a post. Thanked!
THANK YOU SO MUCH FOR THE INFO. i have had so much trouble with unresponsive screen after installing typhoon 2.6.3 and it from holding down the red button all the time for install and the past millions times for everything else.
Thanks for the heads up
Sent from my HD2 using XDA App
U maybe be right about why this issue happens but if u rely on other key then will also wear out soon ...
What I did is I remapped my volume up n down keys to power and back button which I believe are the most used in android and then found a app to manage my volume in android that way I don't lose my sound on rhw phone
Also I went ahead and got a another app which places virtual buttons on ur screen so u can use then instead of the actual hardware buttons
For button remapping
get the BUTTONREMAPPER for android and for on screen android buttons get BUTTON SAVIOR
hope this helps
Sent from my HTC HD2 using XDA App
Good to know... will now wake my phone up with the green key as its hardly used in Android. Button Savior is a great app, been using it a while now. Took a bit to retrain myself to not use the back key.
Sent from my HD2 using XDA App
i'm going to agree with your hypothesis or at least suspect that dirt is probably a bigger factor than most people think in these cases. i just bought a non-responsive phone today and while i stuck my nail (yes, i should probably clip them) around the edge, in between the screen and housing, i was surprised to see just how much dirt was in between that crack. same with the area around the buttons; there's a lot of grime there.
since i just got the phone i haven't even opened it up but the first thing i'm planning to do is give it a good interior clean around the buttons for sure as that seems to be the sensitive spot. touch screen devices are very delicate and the micro particles of dirt which build up over time probably create a hazard that people really don't really anticipate. compound that with having to mash on those buttons all the time probably crams the debris in there even tighter.
i'll attempt to clean and check the contact as you suggested and will report back if it helped in my case.
About hardware keys:
I don't use them at all, only for wake up the phone (it can be wake up with any key)
There is an app in market called "button saviour" it's just excellent app to keep your hardware keys for a long time
AngelDeath said:
The problem is HARDWARE, The Culprit: THE END KEY (Red Button)! The Answer to "How or Why": The "End" key is used to turn the phone on and off or to put it in sleep mode, it is the most used key out of all 5 keys, it is used probably 7x more then all the rest, Its used for just about everything, now how does this cause the unresponsive screen? Easy, the phone lock or sleep is associated with this key, Its the only way to make the screen go off other then waiting for the time out period. Because by habit we mostly hit the end key to turn the screen off the phone automatically associates this with locking the phone, once that happens the screen becomes unresponsive because of several reasons: 1) The contact under the actual key has dirt which causes the button to stick in the down position, 2) the contact is bent which the "end" key is pressing down on the contact which is making contact with the board and causing it to be unresponsive, 3) The contact is worn. This is the reason why if you press the end key a few times (anywhere between 2-10) and then try the screen responds, this is cause your "unsticking" the key which then lets the screen respond.
Most of us when we hit the end key press to the far right to avoid hitting the back key (The button with the left arrow) which causes the end button to lean toward the right. But you can wake the phone up with the other 4 keys to the lock screen which will allow you to unlock the phone. As a temporary fix for myself, on my test phone I now make sure to press on the left side of the key to prevent this from happening, since its a test phone I'm not worried, but the real solution is to take the phone apart and clean the underside of the end button, and the actual contact with alcohol to remove the build up of dirt and whatever else. And also if the contact frame is bent to GENTLY bend the right side back up alittle to stop it from happening, or sending it to htc and letting them fix it.
We have to RE-TRAIN ourselves to start using the other keys to wake the phone up and not rely on the end key so much.
Hope this helps anyone finally why we have this problem. And if it works for you then hit the Thanks button
Click to expand...
Click to collapse
You just hit d nail on d head pal...My HD2's touchscreen also stopped responding and nothing i did (software-wise) worked...i flashed several WinMo ROMs and Android builds with no luck, till i read somewhere online dat some guy seemed 2 solve his touchscreen issues by installing "CleanRam", ran a level 3 clean up (use MyMobiler for this) and by pressing real hard on the red end key button..I did just dat and voila it works!!
I have a Tmobile HD2 which is no longer covered under warranty and i'm not willing 2 part with almost $200 here 2 have d whole lcd & digitizer replaced...I recollected dat in d forum i read the suggestion from, a lot of ppl came n posed their views on why it's not possible but i tell u it is cuz it worked for me..Nw i'm comfortably dual-booting WinMo & Android via sd. i use "button savior" and "extended control" to navigate and power down/reboot respectively.
Hweva i believe its not a permanent fix as it simply refuses 2 allow me run android full-time thru MAGLDR, & i think i know y..pressing down on d end button 2 launch MAGLDR/CWR options after install messes up d connection with d digitizer underneath and d touch screen thereby causing it 2 fail again when android boots up....I just might try opening it up myself n cleaning dat area up as u suggest but dat'll be when my current fix fails cuz as d saying goes "If it aint broken? then don't fix it"
Just installed Button Remapper, and not to sound like an idiot, but can someone tell me which one I would have to remap to make the volume up key or down key to put the phone to sleep and wake it up, and would that still be able to use the volume key to turn up and down the volume as well?
AngelDeath said:
Just installed Button Remapper, and not to sound like an idiot, but can someone tell me which one I would have to remap to make the volume up key or down key to put the phone to sleep and wake it up, and would that still be able to use the volume key to turn up and down the volume as well?
Click to expand...
Click to collapse
Hmm...i don't use d app but from wat i can gather on d dev's thread, you would have 2 remap ur volume keys to "Power"...Also checkout dis review 2 learn hw 2 mk d remapped button work even in sleep-mode.
I can agree but mine's been in twice on repairs with the same error but screen was replaced both times amongst the digitizer, backcover (Can't understand why) and 3 other things were replaced. Buttons weren't replaced.
CaCtuZ123 said:
I can agree but mine's been in twice on repairs with the same error but screen was replaced both times amongst the digitizer, backcover (Can't understand why) and 3 other things were replaced. Buttons weren't replaced.
Click to expand...
Click to collapse
If I'm to base how the HD2 is setup internally, they wouldnt replace the buttons, they would replace the contact or contact board under the buttons, remember the buttons are like a keyboard, they dont wear out, its what they push on that gets dirty or worn.
I was traveling and this happen t me and became desperate.
Following the instructions I come to the clear conclusion that our HD2 has this hardware problem.
If I do not use the end call button no issues with the screen, really, no issues.
Hope my feedback will be helpfull as well. Great job done here!
pauloviegas said:
I was traveling and this happen t me and became desperate.
Following the instructions I come to the clear conclusion that our HD2 has this hardware problem.
If I do not use the end call button no issues with the screen, really, no issues.
Hope my feedback will be helpfull as well. Great job done here!
Click to expand...
Click to collapse
Yeah HTC screwed up on dat...its just as said,1 has 2 be careful n avoid using d red end key button as much as possible 2 enable d device last much longer...And if u do ave 2 use it, press on d left-most part of d key (closer 2 d back arrow button) to get d job done.
I just had this issue happen to me and thought it was my build... But I found another way, I use Cyanogen Mod 7, and in the drag down menu (from the top) I added a sleep option, because thats the only thing I use it for... and I never have a reason to press the end button now.
This is the best thing I have found to fix it without having to remap the buttons
I guess I'm lucky because I have never had a problem with the responsiveness of the touchscreen and/or end button. I got my HD2 a month before TMO release date and trust me it has been thru alot (scratches all over, even a piece of glass missing next to the call button). So my question is how much pressure and wear 'n' tear are you all putting on your end button or phone for that matter?
big3d said:
I just had this issue happen to me and thought it was my build... But I found another way, I use Cyanogen Mod 7, and in the drag down menu (from the top) I added a sleep option, because thats the only thing I use it for... and I never have a reason to press the end button now.
This is the best thing I have found to fix it without having to remap the buttons
Click to expand...
Click to collapse
Can that be done with other roms? And wouldnt a shortcut or a widget on the main screen also work?
on1ydabest said:
I guess I'm lucky because I have never had a problem with the responsiveness of the touchscreen and/or end button. I got my HD2 a month before TMO release date and trust me it has been thru alot (scratches all over, even a piece of glass missing next to the call button). So my question is how much pressure and wear 'n' tear are you all putting on your end button or phone for that matter?
Click to expand...
Click to collapse
It all depends really Understand that not all HD2's go thru the same testing process when it comes out of the manufacturer. Also take into consideration that it also depends on how often you flash a rom, if your flashing a rom every day or every week expect that you will shorten the life of the end button, also it doesnt always mean that the button is bad, it could clearly be dirt underneath that could also be causing the issue. And I said the same thing when I saw posts about people saying that android killed their screen. I even responded to it but always maintained it was hardware, even though I didn have the problem, and I bought both my HD2's used in Dec. and the day it happened and I found out why I posted this, if I was to guess, I would say that I probably flashed both my HD2's close to 200 times with different roms, or upgrades, or testing fixes out.
So if your not a flash nut, then your probably safe. There are many factors that can play a role in the end button life cycle, And no two people use their HD2's the exact same way.
the non-responsive touchscreen problem happened to me this morning. I woke up trying to unlock my phone only to find that it would not respond to any touch gestures. I was however able to uninstall HSPL and Flash the stock WM6.5 rom since I was going to T-Mobile to get a replacement. When I took it to T-Mobile the employee resetted the phone by holding the 2 volume buttons and the power button then somehow the touchscreen started to respond to touch again. I was completely puzzled as I thought it was for sure a hardware problem. But now I'm going to flash Android and hopefully the problem will not arise again, if it does, back to T-Mobile I'll go!
What Android really needs is some sort of "X" button, or even a widget on the main screen that you can just tap and put it to sleep. The three most keys used in my opinion is the windows key (Apps that use it for a menu), the back key (Since there is no damn close button), and the end key (sleep, flashing, booting to magdlr).
Some one had a concept here of buttons that looked very similar to The desire HD, the greatest thing would be if someone could make the bottom of the htc sense (app drawer, phone, and the personalize) auto hide and have the desire HD buttons come up with a power button at the end and this way if you hit menu it would bring up the original 3 button screen.