Camera App does not launch using the double click method - ZTE Axon Pro

So I just messaged ZTE about how I think double clicking the camera button to launch the camera would be a good feature. I thought, that's too simple, there's no way its NOT there. Sure enough I look in the manual and it says " In other screens, Press twice to launch camera..." when I double press it does NOT open the camera.
I hope some dev talent picks up this device. The hardware is there just needs some polish on the software. I'm very satisfied with this phone, My first none Nexus device since before the Nexus S. I was blown away by the design and specs so I had to get a hold of one.

Yeah that feature seems to not be working at all. Bummer too.

I noticed something interesting today with my axon. When holding down the camera button in any other screen, the haptic feedback triggers. So something is assigned to the button, it may just be a programming error.

eallan said:
Yeah that feature seems to not be working at all. Bummer too.
Click to expand...
Click to collapse
So im not the only one! thank god I was worried I had some sort of internal hardware issue... It gives the slightest vibration on a double click but nothing launches.
EDIT: I just tweeted at AXON about this issue. Hopefully bring it to their attention and we start getting some polishing on this otherwise pretty great software.

Camera Key
the quick launch feature was removed last minute out of fear of taking pictures in your pocket. It may be readded at a later date with a software update. If you have any questions call 1-800-617-5065. that number is a VIP line just for the axon pro

samsung_pro_blackbird said:
the quick launch feature was removed last minute out of fear of taking pictures in your pocket. It may be readded at a later date with a software update. If you have any questions call 1-800-617-5065. that number is a VIP line just for the axon pro
Click to expand...
Click to collapse
Hmmmm well on Twitter s/he told me they would look into the issue So I hope that they come through... If anything a double press when the screen is unlocked would be cool too.

bdubs4200 said:
Hmmmm well on Twitter s/he told me they would look into the issue So I hope that they come through... If anything a double press when the screen is unlocked would be cool too.
Click to expand...
Click to collapse
Their R&D dept is very consumer friendly and one of their guys at headquarters is a nexus guy and he's on XDA all the time.

Yea their customer relations is on fire. I just got a message on Twitter about an update from the problem I asked about a few days ago. I'm very impressed.

Related

Menu button

Please tell me you can get rid of that ugly black bar menu button in apps. Is there a way to route the menu button to holding down the back button or something? This will decide if I buy the phone or not.
Yes it is possible but at the moment only of you root. The option was available in pre release software so it's always possible HTC will include the option in a future update.
Sent from my HTC One using xda app-developers app
tdingene said:
Yes it is possible but at the moment only of you root. The option was available in pre release software so it's always possible HTC will include the option in a future update.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks, guess I won't be purchasing the phone.
brian85 said:
Thanks, guess I won't be purchasing the phone.
Click to expand...
Click to collapse
That's awesome. Glad u made such a wise decision.
Sent from my HTC One X using xda app-developers app
Wow, not purchasing the phone due to that? Come on dude, please tell me you are not that anal retentive over something so small.
Then again what is small to me, might be huge to someone else.
Losing out on what looks to be an awesome phone and may even be fixed with a future OTA update..
Sent from a galaxy far away!
brian85 said:
Thanks, guess I won't be purchasing the phone.
Click to expand...
Click to collapse
How can you not purchase the phone over a silly problem as that?? anyways rooting is an option also wait for htc to update it
It's not a dealbreaker to me but I understand that it can be for someone as it takes away some screen real estate. For the same reason software buttons are a dealbreaker to so many people.
Because its annoying and takes up real estate on a screen that is only 4.7". I'm confident it will be fixed via software update. But if would sure piss me off until then. Assuming this thing ever gets released I the US... I'll still buy
Sent from my HTC One X using xda premium
CreepyDroid said:
It's not a dealbreaker to me but I understand that it can be for someone as it takes away some screen real estate. For the same reason software buttons are a dealbreaker to so many people.
Click to expand...
Click to collapse
CraigP17 said:
Because its annoying and takes up real estate on a screen that is only 4.7". I'm confident it will be fixed via software update. But if would sure piss me off until then. Assuming this thing ever gets released I the US... I'll still buy
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Both of these. It's annoying as hell and I don't want to "hack" my phone to get rid of it.
I'll wait and see if the US models have the option to get rid of it at launch. If not, different phone for me (I'm not going to wait for a software update that could "possibly" happen).
: Menu button
flyaway9000 said:
How can you not purchase the phone over a silly problem as that?? anyways rooting is an option also wait for htc to update it
Click to expand...
Click to collapse
Honestly... If this was the only new phone coming to the market this year your argument might make sense. I dunno his opinion but for me. I like having a consistent menu button and not having onscreen buttons... Now when you have this and the galaxy s IV among other phones coming out or currently out... And like some of the stuff with each, and one has something that you know aggravates you, it could be enough to send you to a different phone.
Sent from my SGH-T999 using xda premium
I am the one who made the mod to remove that menu button on the screen and reverted back the option to map it on the back button. Apparently it's just a bug and they did not remove it. So expect it to be fixed/back on the next standard update when the phone is already released globally.
brian85 said:
Both of these. It's annoying as hell and I don't want to "hack" my phone to get rid of it.
I'll wait and see if the US models have the option to get rid of it at launch. If not, different phone for me (I'm not going to wait for a software update that could "possibly" happen).
Click to expand...
Click to collapse
brian85 said:
Thanks, guess I won't be purchasing the phone.
Click to expand...
Click to collapse
I thought exactly the same way and even cancelled my pre-order because of that but after playing around with a mates HTC One I was like.... woah this ain't as bad as I thought it would be and ordered one again a couple of days later.
Trust me with the screen as big as it is you end up with the same usable space with the menu bar as the Nexus 4 and I am sure a firmware fix will be coming in the future and/or apps will be updated to match the google guidelines (facebook are you seeing this!!!)
---------- Post added at 07:51 AM ---------- Previous post was at 07:50 AM ----------
Riyal said:
I am the one who made the mod to remove that menu button on the screen and reverted back the option to map it on the back button. Apparently it's just a bug and they did not remove it. So expect it to be fixed/back on the next standard update when the phone is already released globally.
Click to expand...
Click to collapse
Where did you hear it's just a bug and you expect it will be fixed in the next update?
Like I said I was the one who made that mod in the development section. Obviously I already know how it functions/why it's not showing up in the menu/why it's not working in the stock ROM. And the whole code was in there and intact. It was just not updated so it's not showing itself in the menu options.
If I translate the code in english language it goes like this.
Back menu option: Hey are you "HTC One-debug"?
HTC One: No I am "HTC One"
Back menu option: Sorry then you can't use me I'm only available on a device named "HTC One-debug" not "HTC One"
Click to expand...
Click to collapse
So what I did was
HTC One: Hi!
Back menu option: Enough talk! Just use me.
Click to expand...
Click to collapse
Sounds stupid if you're not a programmer but really! That's whats happening there! lol
daleski75 said:
I thought exactly the same way and even cancelled my pre-order because of that but after playing around with a mates HTC One I was like.... woah this ain't as bad as I thought it would be and ordered one again a couple of days later.
Trust me with the screen as big as it is you end up with the same usable space with the menu bar as the Nexus 4 and I am sure a firmware fix will be coming in the future and/or apps will be updated to match the google guidelines (facebook are you seeing this!!!)
---------- Post added at 07:51 AM ---------- Previous post was at 07:50 AM ----------
Where did you hear it's just a bug and you expect it will be fixed in the next update?
Click to expand...
Click to collapse
Riyal said:
Like I said I was the one who made that mod in the development section. Obviously I already know how it functions/why it's not showing up in the menu/why it's not working in the stock ROM. And the whole code was in there and intact. It was just not updated so it's not showing itself in the menu options.
If I translate the code in english language it goes like this.
So what I did was
Sounds stupid if you're not a programmer but really! That's whats happening there! lol
Click to expand...
Click to collapse
I asked about where did you hear the information about the fix in the next update not kiddie speak for explaining how you fixed the issue.
1. Properly designed apps that use Google's design framework will have an in-app menu button. So no black menu bar. Vast majority of apps now won't require the black bar.
2. HTC got rid of it on the One X when user feedback said they wanted it gone. I see no reason to assume they won't do it again if enough people say they don't want it.
Like I said it's just a minor bug. HTC just skipped updating this one piece of code for it to work on the production units.
Meh! I give up! lol
daleski75 said:
I asked about where did you hear the information about the fix in the next update not kiddie speak for explaining how you fixed the issue.
Click to expand...
Click to collapse
daleski75 said:
I asked about where did you hear the information about the fix in the next update not kiddie speak for explaining how you fixed the issue.
Click to expand...
Click to collapse
He was merely explaining how the bug worked to point out that mapping Menu to Long-Back option is, actually, meant to still be there. HTC simply forgot to make sure that scripts in all places were talking about the same device.
Sent from my Tricked out HTC One via xda-developers application
I know it's a bug and how he fixed it but let me quote what he said...
Apparently it's just a bug and they did not remove it. So expect it to be fixed/back on the next standard update when the phone is already released globally.
Was this bit just guessing or is it from a well known source??
JesseMT4G said:
Wow, not purchasing the phone due to that? Come on dude, please tell me you are not that anal retentive over something so small.
Then again what is small to me, might be huge to someone else.
Losing out on what looks to be an awesome phone and may even be fixed with a future OTA update..
Sent from a galaxy far away!
Click to expand...
Click to collapse
Flaming isnt necessary really
People use their phone differently, its the same reason why theres never a "best rom" or a rom with the "best battery life"
And to the other comments, its likely not to be patched so that they have more reasons to sell a "developer" version
I may have a bad news related on HTC to bring back button remapping options.
Just saw engadget chinese mention in their HTC One review about that Google MIGHT be the force behind that lead to HTC sudden removal the remapping option from HTC One's newer ROM because Google insisting the menu button must somehow be 'observable' on sight.
Click to expand...
Click to collapse

HTC One Home / Back capacitive buttons problem

As many people have noticed, the home/back capacitive/virtual buttons often do not work.
http://www.pocketables.com/2013/04/...-issues-with-capacitive-hardware-buttons.html
http://www.androidauthority.com/htc-one-capacitive-button-problems-198220/
http://forum.xda-developers.com/showthread.php?p=40538985
http://forum.xda-developers.com/showthread.php?t=2231832
http://forum.xda-developers.com/showthread.php?t=2243961
http://forum.xda-developers.com/showthread.php?p=40574171#post40574171
http://forum.xda-developers.com/showthread.php?t=2248951
http://www.youtube.com/watch?v=uvxi6KUR-WA
http://www.youtube.com/watch?v=V7zKpBSluKU
http://www.youtube.com/watch?v=7v5Oc5-7rbA
http://www.youtube.com/watch?v=wxkwyyvOkZ8
http://forums.androidcentral.com/htc-one/270508-home-button-shorting-out.html
http://forums.overclockers.co.uk/showthread.php?p=24147320
http://forums.androidcentral.com/htc-one/270811-back-button.html
http://forums.androidcentral.com/htc-one/271243-button-issue-htc-one.html
http://community.sprint.com/baw/message/569148
Personally, I find it to be *incredibly* annoying and pretty much ruins the experience of using this otherwise good phone. I have already been to the Sprint store to possibly exchange it, but their demo unit had the exact same problem (and the employee I was talking to had also noticed the problem). I have also ran "getevent -lt /dev/input/event6" from adb shell (/dev/input/event6 seems to be the raw output of the touchscreen, some people said it is event5 on theirs rather than event6). This shows you raw data every time you touch the screen. However I noticed that when my touches of the home button go undetected, nothing is read from /dev/input/event6...so I am afraid it may be a hardware problem. I have 11 more days before my 14 day Sprint satisfaction period ends, so I'm on the fence on whether or not I should return it and wait for a better phone, or exchange it and probably get another with the same problem, or...wait for HTC to try to fix it with software.
Some have said a recent update to the Taiwan version of the One solved the problem...:
patato2 said:
doing a bit translation from Taiwan version if you guys can't wait. not sure if I used the correct words though, hope you don't mind.
1.29.709.12(214.04MB)
1. virtual button sensitivity adjusted
2. slow motion video quality improved under low lit
3. better Beats Audio experience
4. better background noise when using headphone
5. better bluetooth device matching
some said back button issue fixed after upgrading.
Click to expand...
Click to collapse
Further evidence that a software patch fixed the home button:
http://translate.google.com/transla...a=X&ei=fy91Ua_5HYaQqgHi_ICwCA&ved=0CGgQ7gEwAw
Poor Google Translate translation:
Did not receive update notifications
Through Settings> About> Software Update> Check Now
We can immediately receive an update notification
After the update the virtual keys become normal
There is a need to go faster
PS: Please note that this is the official update, Brush, may not be updated automatically through the official update to brush back the official
Click to expand...
Click to collapse
Here is the response I got from HTC:
Thank you for retrieving the information for me, [xxxxxx]. I did some research and there will be an MR update to fix this issue with the virtual keys. We do not have any information as to the date the update will be released since it will be released via Sprint your network provider, and it is currently being worked on.
I realize that not having the specific details such as the date is annoying, but we do appreciate your patience. I want to thank you again for sending me that information because that really helps us out a lot. Let me know if you have any other questions I may be able to address with you at this time.
Sincerely,
Casey
HTC
Click to expand...
Click to collapse
I don't have this issue. I'll pay more attention to it, maybe I'm missing it.
~Sent in beast mode using my HTC One~
I've noticed that the area to hit is small. You have to hit it exactly.
Sent from my HTCONE using xda premium
fernando sor said:
I've noticed that the area to hit is small. You have to hit it exactly.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Most likely what you are actually noticing is that not all presses are registered and you are rationalizing it by assuming that you just missed the target. In reality, there is a problem with the home/back buttons that HTC needs to fix, soon.
chogardjr said:
I don't have this issue. I'll pay more attention to it, maybe I'm missing it.
~Sent in beast mode using my HTC One~
Click to expand...
Click to collapse
Be thankful you don't. It is an issue. There are videos on you tube from here in the states about it.
https://www.youtube.com/watch?v=7v5Oc5-7rbA&feature=youtube_gdata_player
Sent from my HTCONE using Xparent Blue Tapatalk 2
I have this issue as well. Seems like you have to hit the button in almost the perfect spot to get it to register.
After watching that I'm very thankful. Mine has always registered my touches. I'm very very thankful. I would be one mad mofo.
treIII said:
Be thankful you don't. It is an issue. There are videos on you tube from here in the states about it.
https://www.youtube.com/watch?v=7v5Oc5-7rbA&feature=youtube_gdata_player
Sent from my HTCONE using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
~Sent in beast mode using my HTC One~
chogardjr said:
After watching that I'm very thankful. Mine has always registered my touches. I'm very very thankful. I would be one mad mofo.
~Sent in beast mode using my HTC One~
Click to expand...
Click to collapse
Hey chogard. Waaazz up? Where's your Rom if you have the one. Wheres that odexed beauty?
Sent from my HTCONE using Xparent Blue Tapatalk 2
Lots more confirmations that OTA 1.29.709.12 solved the problem for the Taiwan variant HTC One. WHEN WILL SPRINT/HTC GIVE US AMERICANS THIS FIX?
patato2 said:
Here's some information about 1.29.709.12 upgrade (Taiwan version), and some responses I read from other forum.
And... sorry guys, I really don't know when will your updates come. and i don't have the phone yet . I envy you!
.
1.29.709.12(214.04MB)
1. virtual key sensitivity adjusted
Lots confirmed the home/back key issue fixed, looks solid.
2. slow motion video quality recording improved under low lit
Didn't see anyone post about it
3. better Beats Audio experience
Some said the left / right sound are better balanced.
4. reduce background noise when using headphone
a few guys said noise is "significantly" reduced.
5. better bluetooth device matching
a few guys confirmed bluetooth device matched faster.
Click to expand...
Click to collapse
For anyone interested, the Taiwan OTA firmware is available here:
http://www.androidrevolution.nl/downloader/download.php?file=1.29.709.12.zip
http://forum.xda-developers.com/showthread.php?t=2182823
Same here. I've found that pressing the button with the pad of my finger vs a tap with the fingertip seems to work more reliably - if only because it covers more of the screen that happens to include the tiny area that registers a button press...
jaybombz said:
Same here. I've found that pressing the button with the pad of my finger vs a tap with the fingertip seems to work more reliably - if only because it covers more of the screen that happens to include the tiny area that registers a button press...
Click to expand...
Click to collapse
I prefer to tap with my fingertip and this is rarely detected by the home/back buttons, which is SOOOO annoying. I'm debating trying to swap it out for a new one. From what I can tell the problem seems to affect EVRYONE, although many people might not notice or be annoyed by it. So the question is, is it truly a pure software fault, or is it a hardware fault that software (ie, an OTA) can mask or at least partially correct.
That's my preference as well - it has been an adjustment and one that I'm not terribly pleased with. I'm surprised the issue didn't show up in pre-release testing but I have to imagine it's something that software can fix with a remap of the area the system recognizes as buttons.
fernando sor said:
I've noticed that the area to hit is small. You have to hit it exactly.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Where's the Rom Fernando?
Sent from my HTCONE using Xparent Blue Tapatalk 2
It's really not an issue with the "area", as I can touch the dead center of the home button and it still won't work. Seems to me that it is either not sensitive enough, or some other problem.
Regardless, word is that an OTA fixed this problem on the Taiwan HTC One 2 days ago, so now I guess we just need to complain loud enough that HTC/Sprint pump out the fix to us ASAP before we all return our phones.
Mines like this as well, you can hit the back button dead on and no response. Hopefully they issue a fix somewhat quickly.
Sent from my HTCONE using Tapatalk 2
Having this problem as well. My device was built April 9th 2013. I can sit there and tap on the home button for 30 seconds or more in every way possible and have no registration of the contact.
This might just be wishful thinking but for some reason clicking the app drawer icon seems to fix the issue right away making me think this is software.
Other than this the build quality and everything else seems perfect.
Sent from my HTCONE using xda app-developers app
HTC needs to admit they have a problem here and advise us whether we should be returning these or waiting for an OTA patch which will be coming VERY soon.
I saw some people talking about this and didn't know what they were referring to.. I got my phone on launch day and have no issues with it, that looks super annoying
Someone posted this over in the international forum. I haven't tried it, as I haven't noticed a problem with my button sensitivity, but there are others who say it works. Worth a shot if you're experiencing problems.
http://forum.xda-developers.com/showthread.php?t=2231832
Sent from my HTC One using xda app-developers app
mang0 said:
Someone posted this over in the international forum. I haven't tried it, as I haven't noticed a problem with my button sensitivity, but there are others who say it works. Worth a shot if you're experiencing problems.
http://forum.xda-developers.com/showthread.php?t=2231832
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Calibration does not resolve the issue.

Performance Update

According to Slashgear.com there is an update that will fix some of the quality settings in the camera. Read on :http://www.slashgear.com/htc-one-updated-with-camera-enhancement-suite-and-more-in-europe-23278984/
Yeah, a little disappointing to see that this update isn't moving out to all HTC One handsets, just in the UK. Looks like we'll see the same pattern for updates coming to phones as we've seen in the past. 3 months at a time.
It also depends on the carrier. Hopefully they'll send it out soon.
It has only been pushed out to UNBRANDED handsets in Europe and Asia. This is software 1.29.XXX.12 (where XXX is the region code) and contains many fixes. Personally, the fix I'm most eager to see is the fix for the home/back button sensitivity, but who knows how long it's gonna take for Sprint to push this.
m03sizlak said:
It has only been pushed out to UNBRANDED handsets in Europe and Asia. This is software 1.29.XXX.12 (where XXX is the region code) and contains many fixes. Personally, the fix I'm most eager to see is the fix for the home/back button sensitivity, but who knows how long it's gonna take for Sprint to push this.
Click to expand...
Click to collapse
I'm going to root this mofo and let a ROM set the sensibility for me.
There are little quirks here are there that I would address if I could..
I wish they would have implemented a dedicated camera button.
They are making this phone a camera first, phone second item.
They should have kept it the dedicated camera button like the 4G LTE.
Update before and after
This site has a before and after shot with the camera. One can def. see an improvement.
http://www.androidpit.com/htc-one-u...&utm_medium=News-Stream&utm_content=Variant_1
Meh, with the power of root and our devs, I'm sure someone will port over the enhancements to our device.
robfactory said:
This site has a before and after shot with the camera. One can def. see an improvement.
http://www.androidpit.com/htc-one-u...&utm_medium=News-Stream&utm_content=Variant_1
Click to expand...
Click to collapse
Nice. Hope we get this soon
Sent from my Nexus 7 using Tapatalk HD
I spoke to HTC in the US and the rep told me very soon for an update. He called it a maintenance update. He also told he didn't know about the button issue he spoke with his Cain of command and they had no idea. So he's submitting a ticket about it. I hope more people call in about this and report it that way things can get done quicker.
Sent from my HTCONE using xda premium
aFoodStampBaby said:
I spoke to HTC in the US and the rep told me very soon for an update. He called it a maintenance update. He also told he didn't know about the button issue he spoke with his Cain of command and they had no idea. So he's submitting a ticket about it. I hope more people call in about this and report it that way things can get done quicker.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Awesome!

Touch input blocked

At times when i unlock my phone i get this message stating my touch input is locked. How do i fix this?
Androidwarrior said:
At times when i unlock my phone i get this message stating my touch input is locked. How do i fix this?
Click to expand...
Click to collapse
The function prevent accidently part of body skin touches the phone screen when the phone in pocket. To disable, go to Display > Block Accidental touches.
Androidwarrior said:
At times when i unlock my phone i get this message stating my touch input is locked. How do i fix this?
Click to expand...
Click to collapse
Something is covering the sensor on the top of the phone. Either clean it and make sure nothing is covering it when you wake your phone or disable the block accidental touches feature
Androidwarrior said:
At times when i unlock my phone i get this message stating my touch input is locked. How do i fix this?
Click to expand...
Click to collapse
Not to be a jerk but you could've answered your own question by simply using the search function in settings. Before you could fully type "Touch input" it will have narrowed it down to the setting you were looking for.
That setting search function is an awesome tool with all the options we have.
....
Androidwarrior said:
Not to be a bigger jerk after i couldn't figure it out by typing and googling it i figure and it being a new phone and all why not let me ask the XDA community under the Answers and questions. Yea thanks for your thoughts greatly appreciated.
Sent from my Samsung SM-N960U using XDA Labs
Click to expand...
Click to collapse
That setting search function is an awesome tool with all the options we have.
Click to expand...
Click to collapse
Lol you typed it everywhere but the settings search bar? Roger got ya.
So umm yeah, setting search. Excellent tool. Glad to be of help
...
TechOut said:
Something is covering the sensor on the top of the phone. Either clean it and make sure nothing is covering it when you wake your phone or disable the block accidental touches feature
Click to expand...
Click to collapse
Thanks i will clean it and make sure nothing is obstructing the sensor.
Sent from my Samsung SM-N960U using XDA Labs
sasmuhd said:
The function prevent accidently part of body skin touches the phone screen when the phone in pocket. To disable, go to Display > Block Accidental touches.
Click to expand...
Click to collapse
Thanks i will take a look at that setting.
Sent from my Samsung SM-N960U using XDA Labs
I have this issue. There is obviously nothing blocking the sensor, but this message pops up in a stuttering manner for a few seconds.
Androidwarrior said:
Maybe you misunderstood or completely misread my message of how i searched and couldn't find it myself. So after I've exhausted my efforts to "figure it out myself".
Click to expand...
Click to collapse
No I read that you did everything you could. The sad thing is typing on the literal text in the setting search would've taken you right to the answer.
I just wish you put as much effort in the "exhaustive search", as you put into griping about good advice..
I mean you could just take a gander at the screen shots and see how easy it is.
Nevermind next time you get a pop up that's too hard to decipher, you can make the daunting task of searching settings.
And that's how you fish.
WaxysDargle said:
I have this issue. There is obviously nothing blocking the sensor, but this message pops up in a stuttering manner for a few seconds.
Click to expand...
Click to collapse
Having this issue as well. I like the feature so I will deal with the weirdness. Whenever I plug in my charger my screen flickers with that message about 8-10 times within 2 seconds then goes away.
mikevipe said:
Having this issue as well. I like the feature so I will deal with the weirdness. Whenever I plug in my charger my screen flickers with that message about 8-10 times within 2 seconds then goes away.
Click to expand...
Click to collapse
have you tried another charger /cable?
i know back in the days when i had a bad charger i would getting small zapps and phantom touches on the screen
WaxysDargle said:
I have this issue. There is obviously nothing blocking the sensor, but this message pops up in a stuttering manner for a few seconds.
Click to expand...
Click to collapse
Daniehabazin said:
have you tried another charger /cable?
i know back in the days when i had a bad charger i would getting small zapps and phantom touches on the screen
Click to expand...
Click to collapse
That's good information but in my case it happens with the new charger that came with the Note 9. My car charger and my old Note 8 charger
mikevipe said:
That's good information but in my case it happens with the new charger that came with the Note 9. My car charger and my old Note 8 charger
Click to expand...
Click to collapse
that's to bad, hopefully it's a software bug and not hardware failure
....
Androidwarrior said:
Shame on me i should be put on a cross and burned alive for that question. I'm sure you have a group of people behind you who support your heroism ready to string me up!! Damn now this question is going to cost me everything all because i didn't search. I'm going back to bed to cry. Byeeee...
Click to expand...
Click to collapse
Wow you are seriously butt hurt over this.
Literally you could've been like "wow, so many ways to do something on this phone thanks for one more tool in my tool box".
Nevermind checking the extensive manual that answers a lot of these questions. Let's not pretend this is hard info to find. It's the phone doing what it was designed to do, not some broken feature you need to troubleshoot.
I keep forgetting this is XDA, it's easier to ask for the answer right in front of you as opposed to learning how to answer the questions yourself.
I'll report back to my support group and tell them mission accomplished. Someone learned something new.
Knowing is half the battle!
...
If you pick up your phone with your hand over the proximity sensor (top of phone), you will get this pop-up. I turned the setting off and it went away but the screen did unintentionally come on while in a pocket. Therefore, it appears best to leave it on and ignore the message.
Can a mod delete pcriz's comments and androidwarriors responses after the question was answered. I think this topic was a valid question.
Samsung has switched up a lot for the better but the downside is they moved it all around. We are stuck in such a monotonous get to point A to point B environment these days the answer was right in front of his face but he couldn't see it because he was too used to the tools he always uses. I am still learning little things about this phone as I go too. I think his question was valid, seeing as Samsung experience is still quite new, Samsung experience is such a huge improvement over TouchWiz, the note9 is loaded to the gills with features and nuances and Samsung (and other OEMs including Google) having features that have trained us to a certain mindset for years. Coming back to the note line after a hiatus hasn't been overwhelming for me but I can see where coming to the note would be like a longtime Android user switching to iOS or even vice versa. For me, still using my work iPhone is so underwhelming I can't figure stuff out and I am pretty savvy with tech. iOS users can find Android overwhelming. And listening to the apologies Apple users come up with now, compared to yesteryear, when many people are finding out iOS isn't as easy to use as has been claimed, it's just what they grew up on, kind of like learning a language. There is a lot to grasp by being immersed in the ecosystem, but more to find out by asking details and learning, learning that can be turned into a tool to find more stuff on your own. Dude obviously tried and put out one more flag up for something he might not have had control over and the response was douchebaggery at it's finest. I find the questions dumb when people are asking me how do I get such great battery life and how they can do it but are unwilling to take their phone off full brightness, theme it to take advantage of OLED's self emitting pixels and are stacked to the gills with social media and email accounts because they have to be that connected and are not willing to streamline portability. Finding the sweetspot for my notifications on the note9 was aggravating for the first time in years as there are many layers to it now. I had to experiment and read about other questions to figure it out. Settings are still taking some time to get used to with main settings, app settings and figuring out where the granular settings are when they're not in places or labeled to what we are accustomed to. To each his own but pcriz obviously overstepped the bounds for a valid question.

Phantom notification

On Pie and November update sideloaded. Using Nova launcher
Have started getting phantom notifications. The phone vibrated, lock screen lights up but nothing there.
Have done a reset as always do after update.
Any ideas?
WiFi lost connection on second, phone track and send you notification but nothing appears...
divvykev said:
On Pie and November update sideloaded. Using Nova launcher
Have started getting phantom notifications. The phone vibrated, lock screen lights up but nothing there.
Have done a reset as always do after update.
Any ideas?
Click to expand...
Click to collapse
Also noticed this today. Did you enabled Ambient Display -> New notifications -> Periodically?
jv.batista said:
Also noticed this today. Did you enabled Ambient Display -> New notifications -> Periodically?
Click to expand...
Click to collapse
Good spot. Hopefully that's it.
That was it. Periodical notifications in ambient display. Crazy
You sideload an update that Nokia pulled out because have serious problems so expect this kind of behaviour!
NahuelMS said:
You sideload an update that Nokia pulled out because have serious problems so expect this kind of behaviour!
Click to expand...
Click to collapse
"This kind of behaviour".....the type of behaviour standard in Pie you mean? It's not a bug just a stupid place to put the settings.
And as for the serious problem! How was it serious where the latest update is 1:1 identical to the one I sideloaded and some people got as standard??????
divvykev said:
"This kind of behaviour".....the type of behaviour standard in Pie you mean? It's not a bug just a stupid place to put the settings.
And as for the serious problem! How was it serious where the latest update is 1:1 identical to the one I sideloaded and some people got as standard??????
Click to expand...
Click to collapse
Ask Nokia then, i only got the service update, so something is going on there. They have pulled the update because problems, now they are sending it again wich have no sense at all and now they are sending also another update only with security update. I don't know. Happy anyway that is not a bug!
NahuelMS said:
Ask Nokia then, i only got the service update, so something is going on there. They have pulled the update because problems, now they are sending it again wich have no sense at all and now they are sending also another update only with security update. I don't know. Happy anyway that is not a bug!
Click to expand...
Click to collapse
I've stopped trying to work out what they are doing. Shame really as it's a good phone. Unless they sort this update stupidity this will be my last Nokia.
divvykev said:
I've stopped trying to work out what they are doing. Shame really as it's a good phone. Unless they sort this update stupidity this will be my last Nokia.
Click to expand...
Click to collapse
You are right. It makes no sense what they do with the updates. Being late, I can understand that, but having 3 different versions of updates for the same phone is crazy (it is kind of the same thing of what they do with the phones versioning numbers: 7, 7+, 7.1, 7x and now 8 which is actually 8.1 - mad)
Anyway it looks like their focus is on releasing more phones than optimize the released ones. I think in the 2 years they were banned from releasing phones after the transfer from Microsoft, they developed the phones and they are releasing them now every 2nd month.
Sorry for the long post, I had to let out some of the steam.
Seems a common feeling with most Nokia users.
Something that baffles me is that the media such as android authority and others keep praising the company and recommending them as superb phones. That bit is true but nobody seems to be picking up that it's not really Android One without regular updates.
Anyway, I'm ranting now. Maybe we need a ranting thread. :silly:
divvykev said:
Seems a common feeling with most Nokia users.
Something that baffles me is that the media such as android authority and others keep praising the company and recommending them as superb phones. That bit is true but nobody seems to be picking up that it's not really Android One without regular updates.
Anyway, I'm ranting now. Maybe we need a ranting thread. :silly:
Click to expand...
Click to collapse
That is s great idea!
I think we all feel a little bit cheated. Thinking at it though, it is only the Pixels and Essential phone (don't think OnePlus has it) that have November security patch.
And the phone is a very good one (hardware at least).
This is it. All steam is out.

Categories

Resources