Related
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.
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!
Hi buddies
As Grarak chose to close the thread of his rom and that maybe some of you want to have some more return and exchanges about the way the rom works, discuss about bugs etc, i open this thread, so that we will be able to do what a forum is done for : talk and exchange together.
New version is 12082014, any return?
Testing soon..
Is calling with sim 2 in 2g working Now?
If not how to use it Any tetsters!
Edit :still No sound from sim2
and there is No way to chose network type
and No 3g from sim 2 too
Im on 9-12-14 build....2g sim not working same as official cm11....3g sim is working......
i 've had terrible battery life, and searching on google lead me to a battery misc processus eating battery, problem solved with 5.0.1 by google
do you guys have the same experience, and have heard about a fix incorporation in the new builds? :good:
I had to go all the way back to the 11-20-14 build. I tried updating to the new builds 12-8, 12-9 and 12-10. No data at all on any of these builds.
Flashed the newest build! We're on Lollipop 5.0.1 now This update is supposed to help battery life. We'll see.
The new music app automaticaly force closes, and the DSPmanager was replaced with AudioFX.
thank you guys for these feedbacks.
Foxy, when you say the new music app, you mean the cyanogenmod one? strange, what could have change ?
Audio playback is fixed now ?
fabulous69 said:
thank you guys for these feedbacks.
Foxy, when you say the new music app, you mean the cyanogenmod one? strange, what could have change ?
Audio playback is fixed now ?
Click to expand...
Click to collapse
I don't know? It's just called "Music" but the icon is like a poorly designed not lollipop looking purple circle. But Apollo is gone so I suppose that's it. And audio playback works, just the app crashes right when I open it.
FoxyDrew said:
I don't know? It's just called "Music" but the icon is like a poorly designed not lollipop looking purple circle. But Apollo is gone so I suppose that's it. And audio playback works, just the app crashes right when I open it.
Click to expand...
Click to collapse
mhm then i think a change that has broke the app. I m sure Grarak will correct it in the next release
Ok, the ROM was going great for me, then yesterday at work my phone turned off when it was in my pocket. I tried turning it on, it booted, started doing the boot animation and then did that for five minutes before it shut off again. This time it wouldn't turn back on no matter how many times i tried power cycling or booting into bootloader. When I got home I tried charging it and the light wouldn't even come on. So I plugged it into my PC and the phone showed up as qhsusb_bulk. After researching that i found it means the bootloader got wiped somehow. My question is, how could my bootloader be gone, because as far as I know, no one has gotten their device S-OFF.
your device is bricked
seems there is a solution on the web but not working for everybody and for specific devices
i dont know what to advice you...
i dont know if it is rom related, but if it is, i wont flash this !
Yes that's what i figured. Luckily Amazon was nice enough to give me a new phone once I send that one in. I was just trying to figure out how it would even be possible that my bootloader got fried, considering my device was still S-ON.
any one who tried this rom found any bugs ???????? i want to know the bugs and want to know in htc 816 daul the second sim worked or not
DRAGONMM2010 said:
any one who tried this rom found any bugs ???????? i want to know the bugs and want to know in htc 816 daul the second sim worked or not
Click to expand...
Click to collapse
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
kr338r said:
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
Click to expand...
Click to collapse
Completely agreed.
kr338r said:
I'm on a single sim Virgin Mobile variant here. There are bugs, yes. This is basically an alpha going into beta of lollipop. There is no one else developing anything new for this device so this is our best bet yet. Aside for some minor niggles here and there, this ROM is very workable as a daily driver. I would recommend a backup, and try this one out. I like it a lot. Grarak is quite amazing actually, many thanks owed.
Click to expand...
Click to collapse
yes, no doubts on his knowledge there!
@FoxyDrew
do you experience better battery life now that we have 5.0.1 ? thx
fabulous69 said:
yes, no doubts on his knowledge there!
@FoxyDrew
do you experience better battery life now that we have 5.0.1 ? thx
Click to expand...
Click to collapse
Didn't test it. Haven't spent enough time on Lollipop because of the no data issue.
I've been playing around with the lastest builds, and I'm actually getting LTE to work without modifying anything, I just have to let it sit for a WHILE and it connects and works quite well.
HOWEVER, I have been getting a corrupt data partition issue with some non-google play apks. I assume that since the build are already not stable, adding homemade, root apks that modify data might cause some corruption. I'll keep playing with it and report back any further updates on how this may be happening.
thirteen_percent said:
I've been playing around with the lastest builds, and I'm actually getting LTE to work without modifying anything, I just have to let it sit for a WHILE and it connects and works quite well.
HOWEVER, I have been getting a corrupt data partition issue with some non-google play apks. I assume that since the build are already not stable, adding homemade, root apks that modify data might cause some corruption. I'll keep playing with it and report back any further updates on how this may be happening.
Click to expand...
Click to collapse
Yah data works...just not good. It has to do with not being able to access APN's.
No one want's to sit "for a WHILE" to open a webpage or read an email.
On the latest build, System UI crashes.
youtu.be/wbqOni008hc
Any solutions? I want to know is it software or hardware problem?
edit: Specs
Marshmallow 6.0.1 G900HXXSACQAA/G900HOJP1CPL1/G900HXXU1CPCA
Smart Launcher Pro 3.16.06PX
Waouuuuuuu....
Never seen that before.
Backup, flash new firmware and reboot.
If problem still present, it's a material problem.
Good luck mate
Franck
Seems to be a standard problem. I have it too.
Internet forums are full of this problem.
Buy another phone than Samsung.
fgth90 said:
Waouuuuuuu....
Never seen that before.
Backup, flash new firmware and reboot.
If problem still present, it's a material problem.
Good luck mate
Franck
Click to expand...
Click to collapse
I've seeb it alot actually. I mean the wake up problem. But noone seems to fix it yet. If anyone did please tell me
Has anyone test this with older Android 5?
The "Weird" Screen in Low Brightness is AMOLED Burn-in due to intensive use, My S5 Have this problem too.
Try changing the HW overlay / Force GPU rendering in developer options, others have said that works for them, it seemed to for me also but only temporarily. I have had to stop using auto brightness.
Device not waking up is very irritating, even double tap the screen to wake has the same problem, doesn't seem to be the buttons themselves. If you have a custom rom or other way to set double pressing the power button to launch the camera it works as a workaround for me.
Thank you for all the answers guys.
Valmerost said:
Try changing the HW overlay / Force GPU rendering in developer options, others have said that works for them, it seemed to for me also but only temporarily. I have had to stop using auto brightness.
Device not waking up is very irritating, even double tap the screen to wake has the same problem, doesn't seem to be the buttons themselves. If you have a custom rom or other way to set double pressing the power button to launch the camera it works as a workaround for me.
Click to expand...
Click to collapse
Just changed:
Force GPU rendering : on
Disable hardware overlays: on
edit1:it's better than before. I will feedback later. Also gonna try that camera trick
edit2: It's same again. Tried Home2 Shortcut the get the camera trick. It also didn't work because i want my phone to be locked and it doesn't work on locked status
Any other suggestions guys?
what ROM are you guys using? Have you tried a different one?
youdoofus said:
what ROM are you guys using? Have you tried a different one?
Click to expand...
Click to collapse
It's the stock ROM. No, I'm planning to try a new ROM today.
raiwulf said:
It's the stock ROM. No, I'm planning to try a new ROM today.
Click to expand...
Click to collapse
that would be a good place to start
Flashed Wanted ROM, it's still the same. It was better at start tho and somehow it freezes less in battery saving mode.
raiwulf said:
Flashed Wanted ROM, it's still the same. It was better at start tho and somehow it freezes less in battery saving mode.
Click to expand...
Click to collapse
if thats the case, then it might be a hardware issue
this is weird af, tons of people have this issue, no solutions yet
raiwulf said:
this is weird af, tons of people have this issue, no solutions yet
Click to expand...
Click to collapse
My solution was buying an OnePlus 3T and never buy a Samsung phone again.
derAndroidler said:
My solution was buying an OnePlus 3T and never buy a Samsung phone again.
Click to expand...
Click to collapse
baaahahahahaha!!! My fiancee has a OnePlus 2 and is a pretty big fan of it. The camera app for samsung TW is far superior tho
Hi everyone,
Don't know for sure if this is the right place to post the thread as it is a Miui 10 problem.
As I am totally happy with my rooted Poco F1 on LineageOS, I bought my girlfriend a Redmi Note 7 recently (which i keep unrooted). Great phone overall, but there is one big issue for us and that's the DND (Do Not Disturb) mode. First of all, when DND activated there are still Whatsapp notifications which is a well known bug in Miui, because I read it everywhere. Anyway, I just disabled the notifications in Whatsapp so that's no big deal anymore.
Bigger problem is the incoming phone calls in the DND mode. When someone is calling (not a favourite/starred contact), it's almost impossible to see if the phone is 'ringing'. The screen keeps black and only when you activate te screen you see a small green block in the left top corner with 00:00 written in it. This is pretty frustrating as we never can see if anyone is calling. This is the first time I face something like this, usually the screen lights up and you will see the incoming call information. On LineageOS it works perfect actually...
Somebody facing the same problem? If yes, is it possible to solve, as DND mode is complete useless for us now...
Thanks already!
Best wishes,
Mark
UP! Sorry for being pushy, but this is really important to use the phone in a proper way.
Thanks again!
Mark
I think this is just a Miui 10 'bug'. Does this forum have a Miui 10 section where I can post this question? I searched for it, but I can't find it that quick. Maybe I'm a bit blind as well
Thanks!
Mark
Sorry to bother, but is there no one who face this problem? Or is it just how the DND function works?
This is not how usual DND works. It's just an Miui thing. I too find it annoying since I depend on DND a lot. Best option is to unlock and flash a custom ROM with normal DND behaviour.
thedisturbedone said:
This is not how usual DND works. It's just an Miui thing. I too find it annoying since I depend on DND a lot. Best option is to unlock and flash a custom ROM with normal DND behaviour.
Click to expand...
Click to collapse
Thanks for your reply! Indeed, it's pretty useless this way...
I'm running a custom ROM on my Poco F1, but as this phone is for my girlfriend I don't want to flash if not needed. She just use her phone very simply, and I think rooting is not neccessary for her. She don't has any benefits from it, except a nice working DND modus
Keep us posted in case you find a solution without flashing a custom rom
kabeza said:
Keep us posted in case you find a solution without flashing a custom rom
Click to expand...
Click to collapse
I will, but untill now there is no fix I guess...
One month ahead, maybe someone has a workaround?
Still nothing I'm afraid? DND mode is pretty useless now...
Hello OP!
I do not have solution for this problem, but I'm here to cheer you up, as I came to this thread facing the same problem on my Mi Mix 3. Unfortunately, it looks like we are the only two MIUI users who suffer from this feature. Hopefully there is third one in the world wide web who knows the workaround and share it with us.
macnow30 said:
Hello OP!
I do not have solution for this problem, but I'm here to cheer you up, as I came to this thread facing the same problem on my Mi Mix 3. Unfortunately, it looks like we are the only two MIUI users who suffer from this feature. Hopefully there is third one in the world wide web who knows the workaround and share it with us.
Click to expand...
Click to collapse
Yeah, I think it's pretty strange that nobody cares about this, so maybe we are using it the wrong way. Anyway, I'm always in silent mode excluding for starred contacts. Maybe it will be solved in the future, we will see...
Take care!
I would check with the Xiaomi MIUI community forums to see if anyone's found a fix over there.
They're way more active with MIUI information vs XDA
Markie! said:
I'm running a custom ROM on my Poco F1, but as this phone is for my girlfriend I don't want to flash if not needed. She just use her phone very simply, and I think rooting is not neccessary for her. She don't has any benefits from it, except a nice working DND modus
Click to expand...
Click to collapse
What's your problem with rooting?
To use custom ROM you need open bootloader, have root... it's your choice, usually custom roms don't have root by default, who want can flash magisk package.
My wife using now phone with custom rom, without root. I changed the rom, because the phone is old, and don't get official update.
Other option can be to use alternative DND app, what you can configure as you wish.
Just posting to let you know that I have the same issue, and it is very annoying.
At least my Mi Band vibrates even on DND mode (which shouldn't happen, but lol right now it's good that it does because otherwise I'd have no way to tell that someone is calling). When sleeping, the watch detects it and also stop notifications. Which is also annoying, DND on the watch and on the phone should be in sync but that's just a perfect example of how very unperfect Xiaomi's ecosystem is.
I guess a "solution" could be to use "Silent" mode instead of DND and disable vibration? Didn't check if even possible, just a thought.
Using a Mi 9 with Miui 11.0.6...