Related
So is this possible? according to the Xperia commericals showing their NFC-badges you just swipe the phone over it. With the GNex you have to turn the screen on unfortunatly, is there a way to fix that?
EDIT: Mod can move this to Q & A, it's getting late over here.
From what I've read, this is a security feature in ICS, as NFC can be used for payments, etc.
I can understand why they have changed it, though IMO it should be an editable setting.
eddie_gordo said:
From what I've read, this is a security feature in ICS, as NFC can be used for payments, etc.
I can understand why they have changed it, though IMO it should be an editable setting.
Click to expand...
Click to collapse
Ah, ofcourse now i see why but yeah it should be editable, though NFC is not that widely used yet i'd like to turn that security feature of until i connect a creditcard to my phone.
Pliind said:
So is this possible? according to the Xperia commericals showing their NFC-badges you just swipe the phone over it. With the GNex you have to turn the screen on unfortunatly, is there a way to fix that?
EDIT: Mod can move this to Q & A, it's getting late over here.
Click to expand...
Click to collapse
Every demo in the xperia video shows the screen on as far as I can tell, and unlocked.
The short answer though is no. ICS requires the device to be on and unlocked before the NFC service is started and the polling loop starts.
If someone wants to try to modify the underlying NFC service in a custom rom it's possible. I wouldn't recommend having it on all the time, but a behavior similar to Gingerbread (unlock was not necessary) would probably be desirable for most users.
krohnjw said:
Every demo in the xperia video shows the screen on as far as I can tell, and unlocked.
The short answer though is no. ICS requires the device to be on and unlocked before the NFC service is started and the polling loop starts.
If someone wants to try to modify the underlying NFC service in a custom rom it's possible. I wouldn't recommend having it on all the time, but a behavior similar to Gingerbread (unlock was not necessary) would probably be desirable for most users.
Click to expand...
Click to collapse
Well now that you said it and i checked the video again..your right.
Think I got the idea from when he stepped out of the car and just flashed the badge.
Pliind said:
Well now that you said it and i checked the video again..your right.
Think I got the idea from when he stepped out of the car and just flashed the badge.
Click to expand...
Click to collapse
To be fair they do make it seem like that's how it would work. Who would turn their phone on, unlock it and then turn it upside down BEFORE they get out of their car just to scan an NFC tag once they got out.
I don't see that being a reality though as the rest of the demos clearly show the device on and what appears to be unlocked. Given this is how the NFC service works within ICS, I'd suspect this will be the behavior as well.
I wanted to get the opinion of the devs who make all of the ROMS for this device. Below is my experience and my theory:
I have had the phantom soft key issue on every incarnation of the GSII software. I un rooted and went all the way back to the beginning. I used each rom version till the issue occurred, then I let the phone update to the next ROM version and repeated the process. Every single un rooted update had the same issue and then every single Rooted ROM all ROMS for the ET4G were tried and the issue occurred.
Strange part is it came out of nowhere. I have had and have been flashing for an entire year without issue and one day all of a sudden... BOOM. I don't think it is as simple as the signal issue. I think it has to do with flashing as well. Unless this is happening to someone who has never rooted their device, I think something in the roms we flash trigger the issue which is related to signal.
Has anyone known anyone who has never rooted their device and has had the issue? By the way, the store gave me a brand new factory OEM screen and the issue still occurs.
Gorguts said:
I wanted to get the opinion of the devs who make all of the ROMS for this device. Below is my experience and my theory:
I have had the phantom soft key issue on every incarnation of the GSII software. I un rooted and went all the way back to the beginning. I used each rom version till the issue occurred, then I let the phone update to the next ROM version and repeated the process. Every single un rooted update had the same issue and then every single Rooted ROM all ROMS for the ET4G were tried and the issue occurred.
Strange part is it came out of nowhere. I have had and have been flashing for an entire year without issue and one day all of a sudden... BOOM. I don't think it is as simple as the signal issue. I think it has to do with flashing as well. Unless this is happening to someone who has never rooted their device, I think something in the roms we flash trigger the issue which is related to signal.
Has anyone known anyone who has never rooted their device and has had the issue? By the way, the store gave me a brand new factory OEM screen and the issue still occurs.
Click to expand...
Click to collapse
I had the issue straight out of the box when we still had gingerbread. I hardly get it anymore besides on occasion
Sent from my SPH-D710 using Tapatalk 2
Elw00d said:
I had the issue straight out of the box when we still had gingerbread. I hardly get it anymore besides on occasion
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Right outta the box before rooting it?
I personally think its hardware related with, either over time the screen moving and the heating up of the device causing phantom button presses... this only recently started happening to me and after i wipe screen with cloth while its turned off it goes away. for awhile... idk haha
I disabled the hardware capacitive keys and use the software on screen buttons. Problem solved
Sent from my SPH-D710 using xda premium
As said above, I had this issue on Gingerbread..out the box, no root. It'd press menu by itself lol, always gave me WTF moments. I'm on ICS now, and no problems at all.
Crazy, ok. Well I got the answers I was looking for. Thank you everyone for your info. Note 2, here I come.
Yup, happens here too. Menu key goes nuts when charging.
FYI just cause you want to get a developers opinion does not give you permission to ask a question in the development section.
Papa Smurf151 said:
FYI just cause you want to get a developers opinion does not give you permission to ask a question in the development section.
Click to expand...
Click to collapse
I will begin chastising myself at once....
Gorguts said:
I will begin chastising myself at once....
Click to expand...
Click to collapse
Picture please ^^^^^^^^^
I have this issue on out of box uprooted and other sget4g were okay for some time after rooting and flashing custom made roms... They too fell prey to the mysterious phantom presses... Ahhh the horror.
My fix was....... To
I have had this issue several months and now have a good solution. Use this info posted by elijahbrown on Page 464 in PA thread I believe. http://forum.xda-developers.com/showthread.php?p=34125394
" Disables menu key!
Ooookay..
Go to system/usr/keylayout
Select sec_touchkey. kl and edit as text. You'll see key 217 is search. Delete that line of code or put a "#" in front of it to turn it into a comment. Save the file.
Re boot and let meet know.
Just curious as to why you want to do this so bad? "
# comment out menu and search keys. Save file and Set permissions.
Then head over to the play store and get Button Savior. I paid for the advanced features and am very happy. Have to keep the phone until may 2013, sprint claims liquid damage so no replacement.
Button Savior on screen hidden pop up menu buttons works great and no more phantom presses menu or search pop ups ever again! 
I was fiddling with my phone settings and testing a few features. WHATEVER YOU DO, DO NOT ENABLE THE TALKBACK FEATURE.
After enabling this feature, my phone began to freeze on every screen while the voice assistant keeps speaking as I try to press anything on the screen. The entire phone just bugs out. Can't swipe or scroll. Can't select anything. Can't get to the settings to disable the talkback feature because I can't scroll. Can't do anything basically.
So, here I am with a brand new unusable HTC One M8. This is my 2nd NEW HTC One M8 that has defective software. My first one couldn't read any SIM cards after 3 new SIM cards were attempted by a T-Mobile rep.
Try factory reset.
badboy47 said:
Try factory reset.
Click to expand...
Click to collapse
Can't. As I mentioned, I cannot swipe or scroll. Factory reset requires scrolling to 'Factory Reset'. Not only that, I cannot select anything unless I get "lucky". The phone doesn't do anything I want it to do. I have a vid of the issue but I can't link it to this thread because I'm a new user.
If you have an HTC One M8, you can test this feature yourself and let me know if you run into the same problem but I warn you... if you run into the same problem, you will need to get it replaced and your phone won't work. Would be nice to know if this is a common problem but I'm not sure people are willing to take that chance and basically break their phone on purpose. It's like telling someone to press the big red self-destruct button to see what happens lol.
Factory reset from the bootloader..... and talk back works fine. And if it does fail on my phone i re install my rom, i love my unlocked, s-offed M8. Makes it all so easy
Mr Hofs said:
Factory reset from the bootloader..... and talk back works fine. And if it does fail on my phone i re install my rom, i love my unlocked, s-offed M8. Makes it all so easy
Click to expand...
Click to collapse
How do I do that exactly?
Wish I could show you the vid, then you'll understand exactly how impossible it is to do anything.
neokrizzo said:
How do I do that exactly?
Wish I could show you the vid, then you'll understand exactly how impossible it is to do anything.
Click to expand...
Click to collapse
Nvm, I figured out how to factory reset when powering it on. I guess my Talkback feature is just unusable?
talkback
no panic ,when in talkback u need to use two fingers to scroll to accesability then turn talkback off simples
paulaiks44 said:
no panic ,when in talkback u need to use two fingers to scroll to accesability then turn talkback off simples
Click to expand...
Click to collapse
Sorry, I think you're misunderstanding my previous explanation. I cannot swipe nor can I scroll. I cannot select anything. The entire phone becomes bugged/glitched. You'd be amazed if you could watch the short video I made of it. It's more extreme than you think. Everything just goes haywire.
I'd like to say I'm a very tech savvy person since I do a lot of computer-related design, I can build computers, troubleshoot viruses, clean my registry, and "techie" things. I'm not just some average consumer who bought a phone and doesn't know how to use a smart phone. I'm very proficient with smartphones. With that said, there is seriously something wrong with the Talkback function. Enabling it almost feels like a virus is attacking the OS. I honestly don't need to use that particular function but what if one day I do or someone else might need to use it.
I actually got a new replacement yesterday and I'm not even going to touch that function whatsoever until I find some answers and a possible solution. I have everything synced to my new phone with my contacts, multiple email accounts, apps, social media, etc. and I'm not going to risk running into that problem and being forced to factory reset my phone. If you know the pain of having to reinstall your OS on a PC which I've done dozens of time throughout the years then you'll understand how painful that process really is because you have to reinstall all your software again.
I found another bug on my new phone as well and made a thread about it already. +/- for Selfie Mode doesn't work. Just greaaaaaat.
n
u need to use 2 fingers when scrolling
LOOOOL...ROFLLLLL...
I remember the first time I ever turned talkback on. "Panic" should be included as an official feature. Obviously, like our friend here, I didn't bother to read all the operational instructions that came with it, and thought for sure I had killed my phone.
Hint: you really have to use "2 fingers" to go anywhere!
Cheers
shirreer said:
LOOOOL...ROFLLLLL...
I remember the first time I ever turned talkback on. "Panic" should be included as an official feature. Obviously, like our friend here, I didn't bother to read all the operational instructions that came with it, and thought for sure I had killed my phone.
Hint: you really have to use "2 fingers" to go anywhere!
Cheers
Click to expand...
Click to collapse
LOOOL.. you've killed me with this post. I experienced this same problem today and the guys freaking out almost made me lose it too. Thanks for the help. Two fingers
mulaz92 said:
LOOOL.. you've killed me with this post. I experienced this same problem today and the guys freaking out almost made me lose it too. Thanks for the help. Two fingers
Click to expand...
Click to collapse
Its a pleasure... glad you made it out without any broken fingers
Hi, first time newbie posting here
I've tried looking up my problem but I have a slightly different issue to what I've seen others have.
When I turn on the phone it says 'bad key' in an odd spot. It delays the boot up time a little but eventually loads up fine.
I was aware of this before I purchased it from the person. I think the person must of got an early release of Nougat for developers because the 'About phone' details seem different to my 2nd (store purchased) Moto Z Play even after checking for system updates.
Bad Key Photo (apologies for the bad quality)
imgur.com/a/YCwht
Settings>About Phone Screenshot
imgur.com/a/6eDtd
I would assume the bootloader is unlocked, but the message looks a little different than what it usually says. Normally there's a triangle and says the device is unlocked and cannot be trusted as well. As for the About Phone, it looks the same for me.
IncendiaryPyro said:
I would assume the bootloader is unlocked, but the message looks a little different than what it usually says. Normally there's a triangle and says the device is unlocked and cannot be trusted as well. As for the About Phone, it looks the same for me.
Click to expand...
Click to collapse
Here are the details on my other Moto Z Play (the stock one) - note the different build number and security patch (both updated).
imgur.com/a/EBs1x
Could locking the bootloader remove the 'bad key' thing? How would I go about doing that?
iivii14 said:
Here are the details on my other Moto Z Play (the stock one) - note the different build number and security patch (both updated).
imgur.com/a/EBs1x
Could locking the bootloader remove the 'bad key' thing? How would I go about doing that?
Click to expand...
Click to collapse
Sorry but once the bootloader is unlocked, there is no method to relock.
iivii14 said:
Hi, first time newbie posting here
I've tried looking up my problem but I have a slightly different issue to what I've seen others have.
When I turn on the phone it says 'bad key' in an odd spot. It delays the boot up time a little but eventually loads up fine.
I was aware of this before I purchased it from the person. I think the person must of got an early release of Nougat for developers because the 'About phone' details seem different to my 2nd (store purchased) Moto Z Play even after checking for system updates.
Bad Key Photo (apologies for the bad quality)
imgur.com/a/YCwht
Settings>About Phone Screenshot
imgur.com/a/6eDtd
Click to expand...
Click to collapse
This is just someone trying to cover up the unlocked bootloader message with an altered boot logo. Whoever you bought it from tried to hide the fact that they terminated the warranty even though you could send it to Moto for them to relock it with a new key.
DroneDoom said:
This is just someone trying to cover up the unlocked bootloader message with an altered boot logo. Whoever you bought it from tried to hide the fact that they terminated the warranty even though you could send it to Moto for them to relock it with a new key.
Click to expand...
Click to collapse
Thanks, I'll give that a shot. Hopefully it wont cost too much.
Just wondering if I changed the rom to lets say Lineage would that 'bad key' message still exist?
What is so bad about that message?
It says
"You can do backups of partitions using TWRP"
It says
"You can root, meaning you can do backups of apps using Titanium backup"
It says
"You can root, meaning you can copy files keeping timestamps like on any other OS"
It also says
"You most probably won't get repairs from Lenovo because warranty is void"
Last point is the disadvantage, but changing the image or text won't help. Lenovo has your device ID in the database of unlocked devices.
tag68 said:
What is so bad about that message?
It says
"You can do backups of partitions using TWRP"
It says
"You can root, meaning you can do backups of apps using titanium backup"
It says
"You can root, meaning you can copy files keeping timestamps like on any other OS"
It also says
"You most probably won't get repairs from Lenovo because warranty is void"
Last point is the disadvantage, but changing the image or text won't help. Lenovo has your device ID in the database of unlocked devices.
Click to expand...
Click to collapse
I got in touch with Motorola's/Lenovo's authorised repairer here in Australia. I was told the motherboard would have to be changed- around $400 so not worth it.
I was actually planning to use the phone as a gps tracker so the extended boot time bothers me a little and also the fact the system updates aren't the same as my other (stock) Moto Z Play.
iivii14 said:
I was actually planning to use the phone as a gps tracker so the extended boot time bothers me a little
Click to expand...
Click to collapse
That 5 seconds display bad key? Never had problems with it, because I usually keep my device running. Would it be difficult for you to not turn it off?
I'm more bothered by annoying boot animation, unfortunately with sound. But there locked or unlocked bootloader makes no difference.
iivii14 said:
and also the fact the system updates aren't the same as my other (stock) Moto Z Play.
Click to expand...
Click to collapse
If you don't root it and don't install another OS, there is no reason for updates to be different just because the bootloader is unlocked. What is the difference in your case?
tag68 said:
That 5 seconds display bad key? Never had problems with it, because I usually keep my device running. Would it be difficult for you to not turn it off?
I'm more bothered by annoying boot animation, unfortunately with sound. But there locked or unlocked bootloader makes no difference.
If you don't root it and don't install another OS, there is no reason for updates to be different just because the bootloader is unlocked. What is the difference in your case?
Click to expand...
Click to collapse
It's about 20 seconds- I know it's not thaaaat bad but still I'd like it to fire up asap.
Its going to live in a car and only charging while the car is running (so the car battery doesn't go flat). I still need to set it up but once the car is started it'll turn back on.
I'm uncertain if its actually a different OS- it looks like the original one but its almost like the previous owner unlocked it to get Nougat on it before it was officially released- thought someone might know from the screenshot.
iivii14 said:
Its going to live in a car and only charging while the car is running (so the car battery doesn't go flat). I still need to set it up but once the car is started it'll turn back on.
Click to expand...
Click to collapse
You may consider adding a power block to your setup. I'm usually not charging my mobile from the car, but from a power block which has the advantage that I don't need long cables (cigarette lighter is on the other side of steering wheel). They are cheap and add flexibility.
If you charge the power block at home or from the car, maybe charging power block and mobile sometimes in parallel using dual adapter in the car, and which size of power block you use, may be worth consideration.
iivii14 said:
...- thought someone might know from the screenshot.
Click to expand...
Click to collapse
Sorry, I can't tell.
If it turns out to be some wrong version or if you just don't trust the current installation, you are free to flash an original one. Unfortunately Lenovo does not release signed official versions, at least not until now. There are some links on xda. Some of them should be the right one
iivii14 said:
Thanks, I'll give that a shot. Hopefully it wont cost too much.
Just wondering if I changed the rom to lets say Lineage would that 'bad key' message still exist?
Click to expand...
Click to collapse
You would get 'N/A' in place of the 'bad key' message. This because custom rom devs don't encrypt/sign their roms like Moto does so there is no key to compare (thus N/A).
iivii14 said:
Hi, first time newbie posting here
I've tried looking up my problem but I have a slightly different issue to what I've seen others have.
When I turn on the phone it says 'bad key' in an odd spot. It delays the boot up time a little but eventually loads up fine.
I was aware of this before I purchased it from the person. I think the person must of got an early release of Nougat for developers because the 'About phone' details seem different to my 2nd (store purchased) Moto Z Play even after checking for system updates.
Bad Key Photo (apologies for the bad quality)
imgur.com/a/YCwht
Settings>About Phone Screenshot
imgur.com/a/6eDtd
Click to expand...
Click to collapse
I know this is old, but I'll place my own answer as an exercise on the subject, if you don't mind: "Bad Key" sign means that someone flashed an unsigned, stock but non-original OS version on your phone; if just unlocked bootloader and even flashed custom recovery on an otherwise original OS (as shipped) it must read "N/A" instead. In both cases, phone should be equally usable; however, if OTA updates can be downloaded, they won't be installed as usual. Assuming that forcefully needed, updates can be ADB or recovery sideload installed. Relocking bootloader won't be possible under given conditions. The black screen with "Bad Key" in there simply means that there is actually no bootlogo installed, probably because previous owner failed in flashing an unwarned one and just refused to keep trying. You can't get rid of the "Bad Key" sign, but you can cover it by flashing any bootlogo of your likes, either with a full white background or a custom made image with a white section that covers exactly on the sign coordinates. Creativity should be used here. No way someone try to charge you big fat megabucks for a new motherboard, since there is no motherboard failure and there's no actual need for such a radical "solution". According to humble my point of view, you just can go rooting Z Play and enjoy the hell out of it...
Sent from my Moto Z2 Play using XDA Labs
hello everyone
i want look phone wiht fingerprint but i can't find this option in my device settings so can someone help me ?
Are you using any root, roms or other modification ? I didnt see any accesibility or developer options to disable fingerprint option.
Also try to check gestures, if swipe fingerprint sensor for notifications is missing too, problem might be hardware or you can always try factory reset or clean flashing.
i'm on stock android 10 without root
i'm try reset phone anyway no fingerprint ootion ?
Similiar issues solved with some users by doing;
-Removing pattern or pin unlock(swipe or nothing) then restart phone
-Entering bootloader. Shut down phone, press and hold volume up+power button until phone powers and enter bootloader. Then normal boot up
I dont think these will solve anything but you might try, some say it is a hardware issue and google just saying contact google support.
i'm try but not solved ?
madjacky said:
hello everyone
i want look phone wiht fingerprint but i can't find this option in my device settings so can someone help me ?
Click to expand...
Click to collapse
That happened to my 3XL just 3 months after getting it. Google didn't send me any kind of response or replies to any of my emails or calls. Right? I got nothing from them for at least 6 months. And the answer i got was ..... This is a known issue with Google. If you still have an active warranty you can send it in for a refurbished handset. The replacement may take up to 4 weeks to receive.... Sincerely the Google team. That was it. I love several things about my Pixel XL3... But there are somethings that I cannot help but feeling like I've been ripped off and that the joke is on me and the rest of us who chose this phone. No... I'm still at a loss for words to express how disappointed and still completely dissatisfied I am with Google and their cold, care less about you way of doing business. It sucks because they are so incredible in many ways that invite them into our loving preference which has us more than happy to devote our loyalty to Google. Only to find Google doesn't give a ****. Sorry so many words. But theft is how i see it. I paid $1000 for a device they would replace with another used device. $1000 ? Gets me another used device after returning my original because of a known issue that I... you... anyone else this happened to .... has nothing to do with and is not anything we're responsible for at all other than our choice to be a loyal Google loving customer. Theft.... that's what happened to your and my fingerprint function. Google stole it along with your money.