I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.
GHII said:
I've had my G2 for almost a month now and the knock on/off always worked flawlessly. Then today it just stopped working, my knock off works but knock ON will not work, at ALL! I've restarted, turned the feature off/on, nothing is getting it to work again. Any ideas? What exactly triggers the knock on feature? Surely it can be the touch of the lcd if the screen is off...is it somehow the proximity sensor or gyro sensor? If I can figure out how it works maybe I can start there..Thanks for any help you can give me.
Click to expand...
Click to collapse
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it
tiguy99 said:
Backup first...then Factory reset
Should fix whatever file or resource that got screwed up. Install your apps 1by1 until you find what app caused your issue & delete it
Click to expand...
Click to collapse
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply
I'm having the same issue with knock on not working. i've wiped a few times and have flashed diferent roms but it wont turn the phone back on. i'm also having this strange issue where i cant pull the notification bar down.
EDIT: I figured it out. did you install TWRP Recovery? i did and mine was messed up. i flashed back to stock and re-rooted and everything works again. I'm not sure if TWRP is the reason since im on a t-mobile G2 but reflashing to stock definitely worked. also i think you have to do a reset after flashing rom because the changes wont take effect unless you do
GHII said:
Well I havent installed anything new recently but maybe I'll take the opportunity to try one of the new CM/ASOP roms...Thanks for the reply
Click to expand...
Click to collapse
Wow that's a relief, I'm having the same pull down issue too.. Even scrolling here is a dead spot on the screen if I'm scrolling a page or list as I get in that area it "slows". I thought my digitizer was going bad. I found my knock on works but I have to do it extremely slow... Tap... Pause 1-2...tap.
Edit yes to twrp.
Sent from my VS980 4G using xda app-developers app
well i re-rooted and it doesnt work anymore. i deleted stuff so i need to see if its something that is being removed that causes it to not work
I just flashed the stock rom back..shows unrooted again, and it is still doing the same thing. Im still under my 30 days, Im going to return it, hope for the Nexus 5 on verizon by the weekend and if not I guess buy a new G2.
mine still says rooted so i'm kinda screwed right now
Same issue
Same thing with my T Mo G2. Using Nova launcher. Knock on worked flawlessly since new, about 2 months,use Nova gesture for knock off. Suddenly knock on stopped working. Too bad, because I like the feature, got used to using it. Did a restore and wipe using TWRP, kept root access, but still no knock on. Next I'll try going back to stock ROM, but I'd rather go an easier route. Has anyone successfully restored knock on?
Hi i have a dead spot somewhere app in the screen and when i pull down the notification bar it doesnt goind down.Also i tryed to draw with quick memo and i can see that it is a dead spot somewhere near the top of the screen
Does anyone has the probleme and have you fixed it
The only solution is returning the phone
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped
rastigo said:
No...first try this.
Open phone app and go to dialer
Dial 3845#*XXX# where XXX is your phone model i.e. 800/1/2/3.. You will come accross a menu.
Select settings
Select touchscreen firmware update...
Wait for couple of minutes...screen will become unresponsive...
when it responds reboot....
Go to settings gestures...ensure knock on is selected.
It should work then,
Let me know...Best of Luck....
---prs thx if helped
Click to expand...
Click to collapse
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
ankurcshah said:
It is a ls 980 model so the code is 5689#*980# and i did that and after doing that also its the same. no reponse ! So tired of this
Click to expand...
Click to collapse
I read the following posts on some other forum...so essentially its a hardware issue....try stock jb rom kdz, then factory reset and reboot. If this helps solve the problem you are lucky. If not, try getting your phone replaced with 802 model. That is practically most stable with a lot of devlopment and tons of ROMS stable and working.
I will still keep looking for a solution and let you know consulting a few senior xda devs I know... sorry man, it hurts to see a fellow indian in distress.....:crying:
Tons of lg users are experiencing this issue. Its a design flaw with a hardware component that easily breaks. Wonderful build quality -_-...right. So only option is replacing the phone. But to how soon, until the other one breaks. So its kinda like. Well. This blows. I suppose Ill install a custom kernel and enable screen wake features that way.
Sent from my LG-LS980 using xda app-developers app
That's odd, I have not seen much on this... if running stock
Quote:
Originally Posted by Burkettacb View Post
Okay. So after hours of tapping. Which might i add. My fingers hurt, I am now able to activate the screen. Pausing after each tap, using my finger print area to tap "not to be confused with finger tip". The screen will activate. Also note, the standard two taps works sometimes, but with four presses, i seem to get the best results. Give it a try people. I have a theory the hardware has not failed. But yet, the activation area pixel size value changed. Either due to a conflicting app install. A intermittent system glitch etc
Sent from my LG-LS980 using xda app-developers app
Or againg, a ROM you may be using.
More detail would be helpful
ankurcshah said:
The only solution is returning the phone
Click to expand...
Click to collapse
Good luck with that if the phone is a D800. I took my G2 to the local AT&T store just a couple of hours ago with the same "no knock on" bug. But the sales person (who had bad breath) told me that because there was another way to get the phone to function (the back button), they won't even look at it. The fact that the knock off/on feature was a MAJOR selling point when the phone was released is apparently irrelevant.
He has a ls980 so it might not be the same for him. He can ask for a replacement
Sent from my LG-D802 using XDA Premium 4 mobile app
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Andrew_han said:
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Click to expand...
Click to collapse
Did you try the "Hidden Menu" "Touch firmware update" option? I had this issue and it got fixed with it.
try 3845#*modelnumber# eg: 3845#*800# change model number 800 with your phones model number, then tap on "Settings" and scroll down to "Update Touch Firmware"
I have a few more suggestions to make it work, let me know how it goes.
Related
Hi,
I did the 2.2 update for the Epic through Samsung's website before it was it was warned not to download/update. Now that my phone has the update my proximity sensor is not working at all. When I put my phone up to my ear during a phone call, it does not shut the screen off, it keeps it on where I am able to press keys during calls. It really annoys me and want to know if there is a fix for this or if anyone else is having the same problem?
Thanks,
katie
should probably backup your things and reflash, preferable with odin i would think.
KateC1 said:
Hi,
I did the 2.2 update for the Epic through Samsung's website before it was it was warned not to download/update. Now that my phone has the update my proximity sensor is not working at all. When I put my phone up to my ear during a phone call, it does not shut the screen off, it keeps it on where I am able to press keys during calls. It really annoys me and want to know if there is a fix for this or if anyone else is having the same problem?
Thanks,
katie
Click to expand...
Click to collapse
You could take it in to the store and see what they can do...they will probably just do a hard reset....I think your best bet is to, like the other poster said, do a fresh install of EB13. Most of the problems with this update were with the update and not with the clean install...good luck!
I could probably assume you don't know what odin is and everything so.. maybe someone could post a link to odin and the eb13 tar??
From My Samsung Epic Using TapaTalk.
It's just your install, use the full 200MB samsung exe after backing up your data and you should be good to go. That's not a bug of EB13, just the way your phone patched to it.
So I reinstalled it using Odin and it started up fine, acts fine, but the proximity sensor still does not work. Any other ideas?
KateC1 said:
So I reinstalled it using Odin and it started up fine, acts fine, but the proximity sensor still does not work. Any other ideas?
Click to expand...
Click to collapse
Sorry you did all of that for nothing :-( Download Z-Device Test from the market. There is a test for the proximity sensor in there. If it is not working in the test, I would say you should go to Sprint and have them fix it...I searched for others with your problem and there were a few (not from updating, you might have had it stop working by coincidence). They all ended up going to sprint and having the screen replaced. Just make sure that if you have a screen protector you remove it so Sprint doesn't try to blame that.
Good luck Katie
P.S. If you are feeling adventurous, you could always Odin back to DI18 and see if the sensor works and the back to EB13 to see if it still works....you could also try installing a ROM on top of EB13 and see if that makes it work (though I don't see why it would) Good Luck
Patrick
Thanks Patrick. I have installed older ROM versions, custom ROMs, and the new update and nothing makes the proximity sensor work. I tried the app you suggested and it shows that the proximity sensor was a green check mark which must mean it works. I do not understand what is going on with it. I have done complete erase on the phone and installed several ROMs with only fail on the sensor. I guess I am going to have to go to Sprint, but I hope that if they have to replace something on the phone I do not have to pay for it.
Thanks again
KateC1 said:
Thanks Patrick. I have installed older ROM versions, custom ROMs, and the new update and nothing makes the proximity sensor work. I tried the app you suggested and it shows that the proximity sensor was a green check mark which must mean it works. I do not understand what is going on with it. I have done complete erase on the phone and installed several ROMs with only fail on the sensor. I guess I am going to have to go to Sprint, but I hope that if they have to replace something on the phone I do not have to pay for it.
Thanks again
Click to expand...
Click to collapse
No problem... just tell them it happened after the update and I don't see any reason that they should charge... they seem to be hit or miss about charging sometimes, try a different store if they want to charge... good luck Katie. Let me know how it turned out.
Sent from my SPH-D700 using XDA App
Looking for some advice/help. I got my wife the Evo Shift a couple of weeks ago. Her phone has not been rooted and other than a few added apps the phone is completely stock. The phone reboots on her 4 and 5 times a day. She does not have any kind of task killer installed so that's not it. She plays Angry Birds a lot and uses Pandora quite a bit. I have also installed Sound Manager for her. Other than that I can't think of anything that would be helpful for trouble shooting. I have searched here and through Google and have not seen any info of others having this problem. I am not sure if I should root the thing or return it to best buy. I have the Evo and previously the Hero and am no stranger to rooting or custom ROMs. Just really did not see the need to root it since my wife has no idea about any of that. Any help or advice will be appreciated.
Thanks.
root and install nfinitefx's or mik's rom; you'll have less trouble than if it was stock.
danaff37 said:
root and install nfinitefx's or mik's rom; you'll have less trouble than if it was stock.
Click to expand...
Click to collapse
That's what I was thinking. I am a little worried its a hardware problem though. I guess I could always flash back to stock and return it if that doesn't fix it.
hell return it ya got nothing to lose but a headache
Did you try a factory reset?
Sent from my PG06100 using XDA App
JKILO said:
Did you try a factory reset?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Not yet. I did get some more info from my wife though. It only happens when she is at work. And she says she get some sort of "radio error". I'm starting to think it might have something to do with the building she is in. She had my hero for a couple months before I got her the shift and had no problems. It had CM 6.1 running though.
hauntedchild said:
Not yet. I did get some more info from my wife though. It only happens when she is at work. And she says she get some sort of "radio error". I'm starting to think it might have something to do with the building she is in. She had my hero for a couple months before I got her the shift and had no problems. It had CM 6.1 running though.
Click to expand...
Click to collapse
im running mine stock and rooted and dont have any problems with reboots. sounds like a app is probably screwing something up
i had a similar problem with one of the streaming media apps i used to use a month or so ago i cant remember the name but for some reason if i lost signal it would crash the phone and need to be rebooted
i took it off and installed tuneinradio and it worked better anyways
My shift was rebooting itself 3 to 4 times a day, I just rooted it and it seemed to stop rebooting itself for a day. Now its starting to reboot itself again, but not as often.
I am almost convinced its a hardware problem. Sounds too rare to be anything else. Maybe bad memory or something.
Sent from my PC36100 using Tapatalk
I had a freezing issue with my phone which people suggested possible due to pandora and bluetooth. Perhaps you have the same issue?
Anyway, try to find "bluetooth for automotive" settings for pandora and turn it off.
I wouldn't recommend rooting your phone if you think its broken. You might just end up breaking it further and render your warranty void.
If you can't fix it, get sprint to replace it.
i dont need a signature
This may be resolved by now, but I got my shift previously used. When I first activated it, I was getting some radio errors and I could not make calls or send sms messages, but the email worked fine. I contacted Sprint customer service via chat from the website and they did something from their end to fix it. I had to turn off my phone and she said now wait till I tell you to turn it back on. I waited 5 minutes and when I turned it back on, everything was fine. So I would take it in or contact Sprint and see what they say. As for not sure if you wanna root it for her, I would definitely recommened it, she doesn't have to take advantage of all the advanced tweak that some use but it will just make the phone a lot smoother and easier to use. IMHO.
Sent from my PG06100 using XDA App
Michael61182 said:
This may be resolved by now, but I got my shift previously used. When I first activated it, I was getting some radio errors and I could not make calls or send sms messages, but the email worked fine. I contacted Sprint customer service via chat from the website and they did something from their end to fix it. I had to turn off my phone and she said now wait till I tell you to turn it back on. I waited 5 minutes and when I turned it back on, everything was fine. So I would take it in or contact Sprint and see what they say. As for not sure if you wanna root it for her, I would definitely recommened it, she doesn't have to take advantage of all the advanced tweak that some use but it will just make the phone a lot smoother and easier to use. IMHO.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Thanks for the input. I think I'm going to go ahead and root it. After keeping an eye on the situation its seems its only happening when she is at work. I can't imagine it will fix it but I think its worth a shot.
I think I fixed mine. I tried to use navigation and it kept force closing, that was strange because I've used it before with no problems. I googled around and found some info that if you had another text to speak engine in your phone then uninstalled it without setting it back to pico as default it would cause nav to FC, which is what I had done. So I set it back and checked "Always use my settings" in the Voice section of settings, nav started working and the reboot issue went away for the past 7 days.
I don't really know crap about phones and most tech stuff for that matter (heck 99% of what is said in these forums goes over my head) but I think why this fixed it is either nav or some app was trying to use pico or something and when it couldn't the phone would get an error and reboot itself. I may be wrong (probably am) but maybe she deleted something or changed a setting some app needs and that is causing her problem. Hope this helps in someway or at least gives you another direction to start checking.
Coming over from the Shift forums for a question.
I've tried getting answers over in the Shift forums but no one can seem to help. (also i've done heavy googling)
OK my issue is the lights on the home, menu, back and search buttons are not working. They went out a couple of weeks ago and when I went to sprint they told me it was due to water damage (which is bs). The weird thing is, if I toggle the brightness on my phone then the lights come back on and stay on until I sleep/lock my phone. Also if I open the camera the lights come on. I know the evo and the Shift are similar devices so thought maybe someone over here might have some thoughts on the issue. I appreciate any help.. Don't ream me for being a Shifter
Thanks in advance
Sent from my PG06100 using XDA App
Have tried a new rom?
You could always try going to a sprint store to have it repaired/replaced.
Sent from my Macbook Wheel using Rotatalk
lynyrd65 said:
Have tried a new rom?
You could always try going to a sprint store to have it repaired/replaced.
Sent from my Macbook Wheel using Rotatalk
Click to expand...
Click to collapse
Yeah, I've tried switching several different ROMs, I've ran a RUU back to stock and Still no dice. When I talked to Sprint they told me it was water damage (it's never been in water) and I need a replacement. The only problem with that is all Shift are being shipped with Gingerbread and I'm not willing to lose root.
That really stinks, you might have to live with it for a while.
It sounds like a hardware issue. Have you tried contacting htc?
Sent from my Macbook Wheel using Rotatalk
The only reason I was thinking it's not a hardware issue is because I can manually turn on the light when I toggle the screen brightness.
I may try and talk to HTC and see what they say. It's not a huge deal, I was just hoping someone had seen a similar problem.
I had the same issue earlier today and read that re-calibrating the screen fixes it. It seemed like a random fix but it actually worked for me. Try Settings > Display > G-Sensor calibration
rudolph22 said:
I had the same issue earlier today and read that re-calibrating the screen fixes it. It seemed like a random fix but it actually worked for me. Try Settings > Display > G-Sensor calibration
Click to expand...
Click to collapse
Thanks for the suggestion but still no luck. I may be stuck with no lights until a new root method is found
Sent from my PG06100 using XDA App
After toying with ROMs I've noticed that knock-on went missing on my G2 D802. Same for Knock Code on ROMs that claim to support it (and worked for me at some point earlier).
Some googling revealed that it could be related to bad touchscreen/proximity sensor error.
However, this is not the case: during call the screen turns off and on correcly, not getting stuck after call etc.
Touch works perfectly as well: dragging notification center at any point, could fill the screen in draw app with a single, long stroke.
Flashing to stock KK using this guide, then resetting to factory settings (which took reeeeally long, like 10-13 minutes. Also scared the cr*p out of me because I thought I bricked it ) didn't help as well.
Has anyone encountered such issue? If yes, how can I deal with it?
Maybe some way to enable sweep2wake instead? I'm really fine with ANY gesture to wake that works.
Siema89 said:
After toying with ROMs I've noticed that knock-on went missing on my G2 D802. Same for Knock Code on ROMs that claim to support it (and worked for me at some point earlier).
Some googling revealed that it could be related to bad touchscreen/proximity sensor error.
However, this is not the case: during call the screen turns off and on correcly, not getting stuck after call etc.
Touch works perfectly as well: dragging notification center at any point, could fill the screen in draw app with a single, long stroke.
Flashing to stock KK using this guide, then resetting to factory settings (which took reeeeally long, like 10-13 minutes. Also scared the cr*p out of me because I thought I bricked it ) didn't help as well.
Has anyone encountered such issue? If yes, how can I deal with it?
Maybe some way to enable sweep2wake instead? I'm really fine with ANY gesture to wake that works.
Click to expand...
Click to collapse
you can try the 1st post from here to see if that works, different problem but it can be the solution
XxZombiePikachu said:
you can try the 1st post from here to see if that works, different problem but it can be the solution
Click to expand...
Click to collapse
IT WORKED! 1000 thanks to you man!!!!
I already managed to flash full JB initial stock firmware with flashtool (with no avail) and this simple stuff did the trick
Thank you again!
Mine are not lighting up and not working. I have done various resets and things would be back to normal, but that has stopped now. Have made enquiries and people are saying it's the Google app and you have to disable it then enable, but that doesn't work either. Has anyone else had this issue? Factory resets were advised in other threads but did not work. I'm getting so many bugs on this phone that it's starting to piss me off
Have you tried initializing in smart switch. Or using odin to flash the latest firmware?
qwewqa said:
Have you tried initializing in smart switch. Or using odin to flash the latest firmware?
Click to expand...
Click to collapse
I''ll give that a try as that seems to be the only option left apart from returning it.
Gave it a try x 2 and it initially appears to work. Then installed some apps and it reverted back. Tried again, and tried setting up as a new phone, same thing. This phone has to be the most disappointing smartphone I have ever had. Permanent bugs, poor sound. Should have waited for the HTC 10.
In Accessibility Settings check if "One touch mode" is enabled. Disable it.
themissionimpossible said:
In Accessibility Settings check if "One touch mode" is enabled. Disable it.
Click to expand...
Click to collapse
Don't have one touch mode anywhere . This phone is really beginning to piss me off. Surely a replacement can't have as many bugs as the one I have. Samsung Internet hardly ever works, the settings I save never save and now this. i'm thinking Samsung rushed this out.
Maybe it's called "Single touch mode" or something similar, I'm translating from Italian...
themissionimpossible said:
Maybe it's called "Single touch mode" or something similar, I'm translating from Italian...
Click to expand...
Click to collapse
Thanks for your help but I cannot find anything relevant on the phone or by Google.
mightywhites29111971 said:
Thanks for your help but I cannot find anything relevant on the phone or by Google.
Click to expand...
Click to collapse
Have you tried the app called galaxy button lights? It might fix the problem.
Heres a link: https://play.google.com/store/apps/details?id=com.notquiteinsane.galaxybuttonlights
Also check to see if you have powersaving enabled. When enabled the recent and back keys do not illuminate.
amar95353 said:
Have you tried the app called galaxy button lights? It might fix the problem.
Heres a link: https://play.google.com/store/apps/details?id=com.notquiteinsane.galaxybuttonlights
Also check to see if you have powersaving enabled. When enabled the recent and back keys do not illuminate.
Click to expand...
Click to collapse
Thanks, have just tried it, doesn't work or do anything I'm afraid
mightywhites29111971 said:
Thanks, have just tried it, doesn't work or do anything I'm afraid
Click to expand...
Click to collapse
I think your only option is to get a replacement then. Hope you get a working one becuase this really is a great phone.
So people say but I have had nothing but problems with it. The sound quality is poor, it never saves my settings and I had to pay £200 to replace the screen whilst out jogging. I didn't drop it, it was in my arm strap for the entire 2 mile jog back from the gym. I'd love to swap it for a HTC 10 as I had the M7 and M8 and they were great phones and I didn't have any issues with them.
mightywhites29111971 said:
So people say but I have had nothing but problems with it. The sound quality is poor, it never saves my settings and I had to pay £200 to replace the screen whilst out jogging. I didn't drop it, it was in my arm strap for the entire 2 mile jog back from the gym. I'd love to swap it for a HTC 10 as I had the M7 and M8 and they were great phones and I didn't have any issues with them.
Click to expand...
Click to collapse
You must have just got a faulty one. I have had mine since it was released here in the uk and have not had a single problem with it other than the occasional reboot but thats acceptable and is just in the nature of Android. I would try a replacement but if you prefer you could sell it and put what ever you get towards a htc 10.
mightywhites29111971 said:
Mine are not lighting up and not working. I have done various resets and things would be back to normal, but that has stopped now. Have made enquiries and people are saying it's the Google app and you have to disable it then enable, but that doesn't work either. Has anyone else had this issue? Factory resets were advised in other threads but did not work. I'm getting so many bugs on this phone that it's starting to piss me off
Click to expand...
Click to collapse
Is powersave mode on?
I've taken it to Samsung on Oxford St, London. After waiting 90 mins a member of staff tried the buttons and then said they will have to send it away for repair and it will take 7-8 days. Then instead of posting it back to me I have to go back to Oxford St and presumably have to wait the same time to get it back. Shambolic customer service.