Hey guys. Just picked up the V40 and ive grown tired of the incessant hints that pop up when you dont press any buttons while on the home screen for a while. How do I stop the hints from showing up?!
No one has any suggestions? Ive searched multiple forums and get nothing. Its infuriating.
I've been sliding them to the left just enough to expose the Settings Icon, then turning them off as they pop up.
It's tedious in the beginning, but they are noticeably farther apart and much less than a few days ago.
Related
My tilt is acting very nasty lately. Over the past few weeks, I noticed that when I turned on the display, occasionally I would get something that looked like the static that you see on TV, but with colors. I would just turn off the screen, and turn it back on to clear it.
Now it's gotten worst! 98% of the time, it intermitantly gives me a blank solid white screen when I turn it on. Occasionally I can just turn to screen off, and on to reset it.
I'm running OEM WM6.1, and I've tried to reinstall the OS, but it didn't help. My phone has taken a beating, and the top corner has had a small crack in it over the past 2 months, but it didn't effect the touch screen, or picture. I also took off the cover to make sure the cables were all snug, and it didn't help.
Any suggestions?
Something got corrupted. If you search WIKI, it's call the 3 color screen stuck .. and you're better off posting at thread below. I hope someone can give you help (if you follow those steps and still no good)
As rule of thumb, do a lot of reading first
http://forum.xda-developers.com/showthread.php?t=423486
On a second thought, it might be the LCD itself broken ..
Oh, believe me.. I'm not one to turn to the forums without doing research myself! All the research I was coming up with seemed to point to a slightly different WSOD though. I think you are right about the screen being broken. I've reinstalled the software, and it acts up even when booting up!
Unfortunately, I'm not impressed with ANYTHING on the market to date! If I'm unable to fix this, I'll just go back to a RAZR until the next gen WM7 phones come out. (With a tilt screen of course!!)
Oh, and even though the screen goes white, it's not stuck, as it fully boots up; I can hear sounds, and even activate the touch screen.
Also, I forgot to mention.. the first problem I started experiencing was that my tilt would go back from landscape mode! It was like the video board was crapping out. I could even see a slight flicker in the display from the refresh rate.
hi i think you may need a new Need a new flex cable ribbon as i had the same problem once
Thanks Tayzaa, I think you could be on to something. I'll open it up and take another look!
Hi!
is this problem solved?
WSOD is bug of Hermes. I would know if kaiser have the same WSOD-bug with D-pad?
Is anyone else experiencing the occasional mixup when hitting the back button? As not always, but many times regardless of the application thats open, I'll hit the back button and the search will come up and I wondering whether thats a common problem or a sensor in my phone is defective and I need to exchange it for a new one...
Thanks in advance
im having a different problem with the buttons. a lot of times my first touch wont register and i have to press it multiple times for it to be recognized.
I've noticed that my touch buttons aren't as sensitive as the touchscreen, and that I need to use a lot of pressure to get them to activate on the first try.
not alone there.. same issue here. I have a clear screen protector over them though.. though it shouldn't be a problem.. I've had the issue even before the protector so..
I have a problem with the back button too, not the other ones. However, when I press a spot a little to the left of the back button and not exactly over the button, it seems to register the press correctly.
I have found that the buttons just do not like any other finger than the index finger try to use the thumb and it will go to search or do nothing.I also returned my first phone as the buttons were terrible 80 percent of the time they would not work.So there maybe be a flaw in some of the phones as this one works fine even with the phantom skins on.The first phone would not even register a response with the skin on.
The buttons on the Captivate suck.
Buttons, as a construct, are well known.
The functional priority of the button is not a mystery and hasn't been for 100 years.
It has to click or otherwise give the user an indication the button has been pressed far enough to take effect.
It has to be tacticle. You have to have some way of knowing that your finger is on the button before you press it.
You have to have some leverage to put enough force on the button to make it move.
It has to be about the size of a finger tip.
It has to be visible. If you can't see it you can't press it.
It has to be different than other buttons that are millimeters from it.
It has to react the first time you press it, or you will naturally press it again, achieving unwanted results.
In all of the above, the Captivate fails.
The T-Mobile Galaxy has more a lot more real estate below the buttons to allow your fingers to get on to them, and a raised ridge on the rear surface of the phone exactly to give your other fingers something to grip against to increase aim and pressure.
But the Captivate has a nice lot of space at the top OH YEAH!
The only problem I have with the buttons is that I can't see them in a dark room
Sent from my SAMSUNG-SGH-I897 using XDA App
I'm getting something similar. Sometimes when I hit the home button the search button blinks as if I had pressed it, then brings up the search screen. On my first captivate (mfg. date 7/16) sometimes it would happen once out of every hundred presses and sometimes it would happen 3 out of 5, very inconsistent. I traded that one in for one with a later manufacturing date (8/10), and my new one does it too but maybe only 1 out of every 100-200 presses. The fact that the search button blinks makes me think it's some kind of short/hardware issue. The back button has only triggered a search for me once, and that was on my first phone.
So this is a hardware issue or a software issue?
My back button on my phone must be pressed 4-5 times sometimes before it will register. The phone did not have the issue when I got it, and a friend of mine who has the Captivate as well does not have this issue.
It may be my imagination, but the phone seems to register touches better after I run a task killer or after restarting the phone, but tends to have issues when multiple apps are up and running.
I was having a button problem as well but fixed it by upgrading to JH3. h t t p://forum.xda-developers.com/showthread.php?t=767666
Your mileage may vary but it worked for me.
May be my imagination, but it seemed to be more isolated to back button on JH3 than JF6 on my machine. My perception is that if I take an additional half-second pause before pushing back button it registers more often. Do not believe it is hardware though. I believe that your home page(button), settings (button), and search(button) all reference something that resides in permanent memory(ROM) whereas the back(button) is trying to recall something that is in temporary memory (RAM) and possibly similar to lag issues may be related to Samsungs somewhat proprietary file allocation system. I am by no means computer literate enough to ponder concept any deeper than just mentioned.
I was having a problem with pushing the home button and the search would come up. I took it to a AT&T store and because I was still in the first 30 days they swapped it out for me.
i'm having a completely different issue with my touch buttons. my back button will register multiple button presses even when i'm nowhere near it. it's quite frustrating to be in the middle of an app and all of a sudden the back button goes off 3 or 4 times and gets you back to the home screen. i've tried searching the forums for some resolution or to see if someone else has had this, but not yet.
Edit: I must not have searched thoroughly enough, found another thread on this issue. http://forum.xda-developers.com/showthread.php?t=858873&highlight=back+button+issue&page=2
Has anyone else experienced the search button pushing itself? I can be touching no where near the search button, or not touching the screen at all, and I will feel the haptic feedback and the button will light up, and screen witl go to quick search.
Anyone have any ideas?
I have the same issue. Not sure why.
yup i seem to have this issue as well, doesn't happen too often though.
Thanks for posting this. I thought I was crazy when I would notice the quick search screen pop up, not thinking I had hit the button. I figured maybe I was grazing it en route to one of the other buttons.
I had the same problem with mine. I thought it was something I was doing, maybe an app, and then suspected the Body Glove case... maybe it was too tight. None of the above. Finally replaced with my 3rd and current Captivate (8/2 build), and it has been rock solid (other than the GPS).
Yeah, it drives me crazy. I think I am going to return my phone today. i have to see what they will do for me since I am outside the 30 days. Then it is time to reflash back to stock...
I had a similar issue and was able to fix it myself. See this thread: http://forum.xda-developers.com/showthread.php?t=767666
Now there is another long topic on freezing, but its basically about 10seconds freeze , then things normal and stuff. Mine is different so I made a new topic.
Have sprint note. On Marshmellow now but happened on Lollipop as well.
The problem is:
After several hours of use, or may even a day, the phone just freezes....partly. Let me explain. Basically if you touch anywhere on the screen, it won't register the touch. If you hit the hard recents button, it'll show recents, but you can't click any program (it doesn't register your touch). When it first happened I thought I needed a new screen, but quickly found out I probably don't: If I hit the nav bar, it will pull down full screen, and if I have it full of notifications, I can click any of the notifications, whether its near the top, middle, or bottom, and it registers the touch and sends me to the app. But then again, at that app, the screen doesn't register. Even if I touch in the same place on the screen where I clicked the notification that sent me to the app. But the nav bar still works. It recognizes the touch, and will pull down full screen, and I can click anywhere on the screen and my touch will register. Also if I hold the power button and the reboot options come up (which on mine has option from top down to bottom, I can click any option on the screen, and it will register my touch. But if I hit the home button, the whole screen is non responsive. So I have a partial freeze. The whole screen doesn't work, but then the whole screen will work when I pull the nav bar down, so im totally confused. I already tried usually differnt launchers, but same thing, after while, screen will be non responsive
If I reboot then everything works fine and normal, so I doubt its a screen issue. Because if its broke its broke. Also tried a hard reset,problem still came back. I guess it may be an app clashing problem but I have over 100 apps it could be any one of them
Has anybody experienced something similar?
I had a buddy give me an LG Lucid3 that had a similar issue... It actually got worse over time and the touchscreen totally stopped working. (He thought) I took it apart and actually the connection was good. Put it back together and just kept rebooting it multiple times in a row. Finally, the touch started to work a little an for some reason I thought to go and download an antivirus program. The phone had 11. Got rid of them and phone has been working fine for a couple weeks now. Idk if that's your problem but I figured I'd share this experience because I've never seen anything like it.
Sent from my KYOCERA-C6745 using Tapatalk
Is anybody else experiencing unresponsive screen on some parts?
Couple of days ago I started having problems with letter "a". It wouldn't react unless I pressed it all the way at the left side of the key, which I attributed to being close to curve of the screen - if the phone was in my left hand then I pretty much punched it on the right spot every time, so I thought it had to be it. It's an ongoing thing.
But now I was making a video in Quik app, and in one of the screens the play/pause button is right at the place where the letter "a", and I found my self having to press the key like 10 times in a row before it reacted - on a couple of occasions. I doubt it's some sort of memory issue since this thing is a beast and no way a couple of pics in Quik app could make it unresponsive.
I am utterly crushed now, since I love this phone to death. I really hope it's not a defect :crying: