Do you guys think with the qfuse that with root/unlocking, the finger print sensor will be somehow disabled?
Nope. There is conflicting reports on the QFuse. Some say that it is activated at first boot of the device regardless of root, etc. Even if its not I highly doubt this is anything that Google will worry about as they provide instructions for unlocking bootloaders on their own site and have been known to walk users through doing it when troubleshooting
Which is what I figured but wanted to see what others think.
Related
Just to let you know, my week old tegra note 7 developed touchscreen issues:
After 20 or 30 minutes use the touchscreen both develops unresponsive areas (on stylus and/or finger) and eventually starts triggering random window opening and becomes unusable until left to cool off for a while, restart not necessary.
I'm sure it's a hardware issue as I have restored previous functioning twrp images, also restored a stock rom with user data davlik cache clear.. same problem, it is very interesting to utilize the developer options of "pointer location" or/and show touches as it makes it easy to see exactly what a faulty touchscreen Is reporting! no wonder random windows/menus would start opeining!!
P.S Unfortunately I've rooted the device so may not be able to get a warranty replacement I've searched and so far not found a method for restoring an original non voided bootloader for these devices.. I did however notice some interesting progress for the tegra 3 series though, where someone had worked out how to backup the original bootloader before rooting and then restore it after rooting, so there is hope..... if any devs here want to pursue that for the note 7 here's the link http://forum.xda-developers.com/showthread.php?t=1927818
gtmgtm said:
Just to let you know, my week old tegra note 7 developed touchscreen issues:
After 20 or 30 minutes use the touchscreen both develops unresponsive areas (on stylus and/or finger) and eventually starts triggering random window opening and becomes unusable until left to cool off for a while, restart not necessary.
I'm sure it's a hardware issue as I have restored previous functioning twrp images, also restored a stock rom with user data davlik cache clear.. same problem, it is very interesting to utilize the developer options of "pointer location" or/and show touches as it makes it easy to see exactly what a faulty touchscreen Is reporting! no wonder random windows/menus would start opeining!!
P.S Unfortunately I've rooted the device so may not be able to get a warranty replacement I've searched and so far not found a method for restoring an original non voided bootloader for these devices.. I did however notice some interesting progress for the tegra 3 series though, where someone had worked out how to backup the original bootloader before rooting and then restore it after rooting, so there is hope..... if any devs here want to pursue that for the note 7 here's the link http://forum.xda-developers.com/showthread.php?t=1927818
Click to expand...
Click to collapse
If you have the latest version installed, you might get lucky. The bootloader doesn't really say your warranty is voided anymore, so if all the repair center does is reboot to the bootloader and check there they won't see anything.
Perhaps they have some internal tool to check that however, in that case you might no be so lucky. At least you could try to relock the bootloader before sending it off, as well as calling the manufacturer and ask them whether the hardware is still covered by warranty.
seems mine is an older version and still has the bootloader warranty voided message. the customer support was very professional when I phoned and they approved me sending back for replacement (but I didn't mention the message)#!
I'm hoping that they'll either not check bootloader or realise this is a straightforward hardware error and replace it anyway.
Is it possible to improve the fingerprint scanner ? Its really frustrating the current method which samsung put on galaxys devices.
jeffcosta123 said:
Is it possible to improve the fingerprint scanner ? Its really frustrating the current method which samsung put on galaxys devices.
Click to expand...
Click to collapse
How do you mean improve? I can take a guess at what you mean. If your talking about how the scanner takes a few tries then you need to re-do the input scan. When you do, start normally swiping down but start rotating your finger. Also add a little roll to get the sides of your print too. The scanner should recognize your print quicker in fewer tries. Samsung's implementation of the FP scanner is just awful in my opinion anyways.
As the poster above stated, use some variation when setting up the scan. I know some people set up more than one finger and preferred that way. I just use my thumb and it always opens for me on the first try, unless my hand is wet from a glass or something.
Anybody with Lollipop know if you can use the fingerprint to unlock the phone when encrypted yet?
bbeelzebub said:
As the poster above stated, use some variation when setting up the scan. I know some people set up more than one finger and preferred that way. I just use my thumb and it always opens for me on the first try, unless my hand is wet from a glass or something.
Anybody with Lollipop know if you can use the fingerprint to unlock the phone when encrypted yet?
Click to expand...
Click to collapse
Yes you can. Both internal and sd card storage.
I registered the same fingerprint three times, 95% of the times takes just one pass, the other 5%, takes two passes
With direction lock, you can unlock your phone by drawing a pattern on it...pretty cool I think
https://youtu.be/iIQUWxuLhOI
Considering I'll be coming from a G2, it's a far cry from knock on. I will miss knock on more than anything on my G2 I'm sure. It might break the boredom of just swipe to unlock, but leaves more room for error and will take longer.
natypes said:
Considering I'll be coming from a G2, it's a far cry from knock on. I will miss knock on more than anything on my G2 I'm sure. It might break the boredom of just swipe to unlock, but leaves more room for error and will take longer.
Click to expand...
Click to collapse
Knock on was very cool, pressing the home button once with the fingerprint reader is cooler.
Well, I'm getting an S6, so I'm certainly willing to give it a shot.
After activating the direction lock feature I have run into a very serious issue. An OTA software update came in from AT&T after which the phone did a reboot. I cannot unlock the phone as it no longer recognizes the direction lock pattern and sadly, it is requiring that specific unlock method for the first unlock after reboot. Samsung tells me there is no way around this except a full master reset which the data loss would be devastating! I cannot locate any software that will pull the data via USB either as the model is an S6 Edge SM-G925A which is not offered via FonePaw, Phone Doctor or Mini Tool. Since the direction lock is located in the Accessibility menu the "unlocking" methods don't work either as the values are apparently in a different location. I seriously need some help with this issue. Losing all the critical data from my last backup to now is beyond stressing me out as it is vital as well as having some very sentimental items. If I could just find a way to either pull the data or explore the phone via third party software I would be one very happy man!! Please, if there is anyone that has an idea, I am willing to try just about anything to prevent a factory reset! Thank you very much in advance!! And yes, I have searched and read and searched and read..... over 5 hours worth of time spent online trying to get this solved... BTW, the phone does not have USB debugging enabled and is not rooted. Just stock Android 7.x
if anyone here knows how to downgrade pls help me out... i want my software status as official...
You can't completely downgrade, it isn't possible to downgrade the partition table (gpt.bin), every thing else will work fine as long as your bootloader is unlocked... problem is that after downgrading, taking an OTA in a mixed environment (partition table and rest of rom don't match versions) is potentially dangerous, you're completely on your own here, it might work, it might not, or the OTA may fail because it detects the incorrect versions (most likely case), or it applies and you bricks (least likely situation).
I will ask again... WHY is it so urgent to get back to Official state, it is merely cosmetic, it has no functional effect on anything?
FYI... the more you look for a solution to this "problem", the more curious I am as to why it's so important
If you're trying to get your warranty back, it won't happen, that was voided simply by accepting the T&C on the unlock page and receiving the unlock code, it doesn't matter if you actually used it or not or what your phone shows, the warranty is permanently gone even if you didn't get the email, Moto has shown that to be the case time and time again. If you are trying to sell it, you just need to explain to anyone who is smart enough to check it why it is like that, anyone who doesn't know to look won't care anyway as long as it works. What other reason could you possibly have?
acejavelin said:
You can't completely downgrade, it isn't possible to downgrade the partition table (gpt.bin), every thing else will work fine as long as your bootloader is unlocked... problem is that after downgrading, taking an OTA in a mixed environment (partition table and rest of rom don't match versions) is potentially dangerous, you're completely on your own here, it might work, it might not, or the OTA may fail because it detects the incorrect versions (most likely case), or it applies and you bricks (least likely situation).
I will ask again... WHY is it so urgent to get back to Official state, it is merely cosmetic, it has no functional effect on anything?
FYI... the more you look for a solution to this "problem", the more curious I am as to why it's so important
If you're trying to get your warranty back, it won't happen, that was voided simply by accepting the T&C on the unlock page and receiving the unlock code, it doesn't matter if you actually used it or not or what your phone shows, the warranty is permanently gone even if you didn't get the email, Moto has shown that to be the case time and time again. If you are trying to sell it, you just need to explain to anyone who is smart enough to check it why it is like that, anyone who doesn't know to look won't care anyway as long as it works. What other reason could you possibly have?
Click to expand...
Click to collapse
I really admire your patience. Especially with stuff like this.
Sagar_1401 said:
if anyone here knows how to downgrade pls help me out... i want my software status as official...
Click to expand...
Click to collapse
Watch this video'.
Guys - the easiest way to get development started on a new device is to NOTIFY the device manufacturer that there is a NEED for the company to fix issues. The first issue is THE BOOTLOADER UNLOCK METHOD BREAKS THE FINGERPRINT SENSOR. This is obviously highly undesirable for anyone who wants ROOT. *** NOTE THIS CAN BE AVOIDED ENTIRELY THROUGH THE ROOT BYPASS METHOD (FP STILL WORKS), AND A USER HAS FOUND HOW TO RECALIBRATE THE FP SENSOR AFTER A BL UNLOCK, XDA POS: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
The main issue is Google Pay does NOT WORK with NA and Global ROMs. It reports 2 cards instead of 1 card when you go to a terminal, so you can NEVER make a payment!!!
So how can we fix this issue? COMPLAIN!!! We got source this way already (THANK YOU FOR YOUR HELP GUYS WE DID IT!)
METHOD #1
EMAIL Nubia customer support (probably our best path) at [email protected]
You can simply report the issue similar to this message in your email:
Google Pay does not work with NFC which your Global and North American ROM claim to support. It reports 2 cards at the terminal instead of 1 card so payment fails EVERY time. This is an issue across the world for everyone with Google Pay. WE NEED THIS FIXED AS IT IS A LISTED FEATURE OF THE PHONE THAT DOES NOT WORK.
Please fix as soon as possible.
Signed,
[YOUR NAME / Country / Phone Model]
METHOD #2:
https://github.com/ztemt/NX659J_Q_kernel/issues/2
Post something like I did here - GOOGLE PAY DOES NOT WORK. FIX NFC ON GLOBAL AND NA VARIANT ROMS ASAP.
Please start posting comments here to release the source code so we can begin custom kernel and ROM development as soon as possible! Thank you everyone who contacted [email protected] or posted to the original GitHub issue, now we just need them to follow through!!! WE HAVE STRENGTH IN NUMBERS.
I have done as advised let's hope they fix this
Sent from my GM1913 using Tapatalk
I just did it too(both ways), but I don't know how much they care about the emails, I sent 3 before, for other things, without any reply
How much pay?
Guys! They do care about the device! I've emailed them three times, and I've got replies everytime!
ZTE released the source code for the Red Magic 5G... hopefully this will kick start development for this phone because it has so much potential.
nexuses said:
Guys! They do care about the device! I've emailed them three times, and I've got replies everytime!
Click to expand...
Click to collapse
Try asking about an older device that they dont produce/sell anymore. If they eager to answer they might care about devices that are older than 1 or 2 months
xabierd said:
Try asking about an older device that they dont produce/sell anymore. If they eager to answer they might care about devices that are older than 1 or 2 months
Click to expand...
Click to collapse
Well, the future updates are the only reason that hold me back from buying this phone! So I'll give it sometime to see what happens.. We will see..
Keep contacting guys..
Nevermind you closed the one with the new title ... Keeps this alive. Thanks Admins.... I don't see why closing this and opening another that resolves remaining ones is a problem. When I link it elsewhere it still looks like the original issue where we fixed or worked around 2 of them and now the last to address is GPay.
mslezak said:
Guys - the easiest way to get development started on a new device is to NOTIFY the device manufacturer that there is a NEED for the company to fix issues. The first issue is THE BOOTLOADER UNLOCK METHOD BREAKS THE FINGERPRINT SENSOR. This is obviously highly undesirable for anyone who wants ROOT. The second issue is Google Pay does NOT WORK with NA and Global ROMs. It reports 2 cards instead of 1 card when you go to a terminal, so you can NEVER make a payment!!!
So how can we fix this issue? COMPLAIN!!! We got source this way already (THANK YOU FOR YOUR HELP GUYS WE DID IT!)
METHOD #1
EMAIL Nubia customer support (probably our best path) at [email protected]
You can simply report the issue similar to this message in your email:
Google Pay does not work with NFC which your Global and North American ROM claim to support. It reports 2 cards at the terminal instead of 1 card so payment fails EVERY time. This is an issue across the world for everyone with Google Pay. WE NEED THIS FIXED AS IT IS A LISTED FEATURE OF THE PHONE THAT DOES NOT WORK.
Also, the bootloader unlock on the Redmagic 5G disables the fingerprint sensor completely - the error message says to contact Nubia support. The device will not even allow a fingerprint to be added. The Android installation detects the sensor on the "back of the phone" i.e. missing the Goodix in-screen fingerprint location, so it can not be added. Later trying to add an FP results in an error:
Loss of fingerprint calibration data
Loss of fingerprint calibration data was detected.
Currently unable to complete fingerprint entry,
please contact Nubia after-sales support via
4007006600
Please fix as soon as possible.
Signed,
[YOUR NAME / Country / Phone Model]
METHOD #2:
https://github.com/ztemt/NX659J_Q_kernel/issues/2
Post something like I did here - GOOGLE PAY DOES NOT WORK. FIX NFC ON GLOBAL AND NA VARIANT ROMS ASAP.
Please start posting comments here to release the source code so we can begin custom kernel and ROM development as soon as possible! Thank you everyone who contacted [email protected] or posted to the original GitHub issue, now we just need them to follow through!!! WE HAVE STRENGTH IN NUMBERS.
Click to expand...
Click to collapse
You can enter *#*#9959#*#* on the dial pad to enter fingerprint calibration mode, and then calibrate the fingerprint, it will return to normal
johnny886 said:
You can enter *#*#9959#*#* on the dial pad to enter fingerprint calibration mode, and then calibrate the fingerprint, it will return to normal
Click to expand...
Click to collapse
Sorry, it does not work here. I dialed the code but It doesn't do anything.
johnny886 said:
You can enter *#*#9959#*#* on the dial pad to enter fingerprint calibration mode, and then calibrate the fingerprint, it will return to normal
Click to expand...
Click to collapse
Johnny can you explain the calibration steps for everyone with this issue? We've seen the factory calibration device that no one can find for sale anywhere. But some have managed with using their finger, a piece of dark paper, and the back of a fingernail. But that doesn't seem to work for all.
mslezak said:
Johnny can you explain the calibration steps for everyone with this issue? We've seen the factory calibration device that no one can find for sale anywhere. But some have managed with using their finger, a piece of dark paper, and the back of a fingernail. But that doesn't seem to work for all.
Click to expand...
Click to collapse
You can use special fingerprint calibration weights to calibrate fingerprints. You can use weights to calibrate at some professional repair points.
johnny886 said:
You can use special fingerprint calibration weights to calibrate fingerprints. You can use weights to calibrate at some professional repair points.
Click to expand...
Click to collapse
That dial code doesn't work for some reason.
Anyways the code is *#9959# to start calibration off the TG group it works. Although what to do after launching it I have no idea.
I keep getting hung up here
viper98 said:
I keep getting hung up here
Click to expand...
Click to collapse
Same here...
My NFC Works now with Google pay only 1 out of 100 times ? it shows the message: present only one card at the terminal.