Related
hi all i use run.gps on my old omnia and i want it on my new htc hd2 but the app wont pick up the gps info correctly, it gets a great signal and then just wont tract my speed/distance ect
any help here would be great
I'd like to see this resolved too, since I was really keen to try this software out.
do u have same issue matey, i dont mind using other apps but i really need voice guide like speed and distance, and i think this is the only app which does this?
I was going to install today, then I saw your post, so I haven't actually tried it just yet. When I have time later I will give it a shot.
NZtechfreak said:
I was going to install today, then I saw your post, so I haven't actually tried it just yet. When I have time later I will give it a shot.
Click to expand...
Click to collapse
that would be great so i can see if its just my device or not
i think imay i have solved the problem, when i1st ran the app i used the htc hd2 lock to lock the phone and it seems doing this stops the gps from working, if u use the run.gps locking it works fine,
p.s. in menu setting check that all the buttons are locked when screen is so u dont press anything when running lol
HI MATE i can confirm it works now, u need to lock the screen with the app and let it goin to the lock wm lock screen automaticly, if u press the end key to enable the lock screen ur self the gps doesnt work correct, heres a run to show it works
my run today (i do two runs with 3min rest between for a drink)
http://www.gps-sport.net/trainings/running_200106
http://www.gps-sport.net/trainings/running_200136
Nice, thats good news. Thanks.
I am still new to the fingerprint reader so my old habit of swiping, which takes you to an pin pad. It says to Use fingerprint or enter pin, but about half the time it doesn't take the fingerprint. I'll either have to let it time out and get it on the main lockscreen or just enter the pin.
Actually the first day it was so bad that I didn't even think it was accepted on that pin screen. It wasnt until last night when I even saw it say "use fingerprint" but it works about half the time.
The fingerprint scanner works pretty reliably everywhere else so I don't think its a hardware issue. Just curious if others are having problems scanning on the pin screen.
Only time I have an issue is the first time Samsung Pay reads my print. 99% of the time, I have to put my finger on it again. Best way to solve your issue that I found is by unlocking your phone as follows:
Press and hold the home button with a finger that you have saved. When the phone unlocks, remove your finger. This way your finger is firmly on the reader. If it is still giving you issues, try making the fingerprint again in the settings.
I have big fat fingers lol. And I use my thumbs to unlock. In the fingerprint settings, I now have multiple fingers set to unlock the phone, that way, if I'm having maybe a problem hitting it right with one finger, I can get it with the other. I've got both hands covered. Multiple fingerprints to me is key. Also, when I was first learning to scan my prints, it took me a little while to get it right. For my thumbs, I'm pretty methodical... I start at the bottom left, lift up bottom middle, lift up, top left, lift up, etc... Basically let it scan a small quadrant of my thumb at a time. Seems to work really well. I have very few bad readings. Usually happens when my fingers have something on them, or the button has something on it, or my finger is laying too far sideways...
Sent from my SM-G935V using Tapatalk
No its not about reading my finger. I have multiple fingers setup (4).
I dont have an issue unlocking via fingerprint from the main lockscreen. The problem is when I try to swipe and it asks for a pin. Its this screen where it works half of the time. Its not that it isnt "matching" because when it works it will throw an error like "no match". But half the time it doesn't even recognize me trying to scan a finger.
I've been testing it more and more and it is a bug.
I understand what you're saying now. I haven't run into this problem yet. I do have some issues here and there, but it's not like an all the time situation.
Sent from my SM-G935V using Tapatalk
mwshows said:
I understand what you're saying now. I haven't run into this problem yet. I do have some issues here and there, but it's not like an all the time situation.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
I just moved to the Note 5 and grabbed Marshmallow. I can say that the issue was specific to the S7E. Even on the same screen, it is responsive regardless of whether it was successful or failed, at least it prompts and responds.
On the PIN screen, it just would recognize a fingerprint input half the time.
Update
My Note 5 did it a few times today too. Aggrevating.
When you have a bunch of notifications, you select one to open, the pin screen comes up, and occasionally doesnt take fingerprints. Its like it's looking for ONLY the pin. Weird.
Im having this exact issue as well. So annoying to be not able to unlock via fingerprint at the PIN screen!!!!
Having exact same issue, and it pretty much makes the
fingerprint unlock method useless. I'm using a Galaxy S7 Edge, in Australia with an Australian carrier, so it's a safe bet the issue isn't isolated to Verizon (perhaps move the thread in the main s7e thread to get more attention?)
*The fingerprint works
100% time on the main lock screen, but whenever you tap a notification or swipe
to unlock, and you are presented with the PIN/Fingerprint or
Password/Fingerprint screen, the fingerprint unlock method rarely works. You
either have to enter the pin/password, or go back to the main lock screen and
use your fingerprint there to unlock the phone.
Seeing as multiple people have reported the issue, safe to say its not an isolated issue. I'm surprised more people haven't complained
about it, as it really defeats the purpose of fingerprint unlocking.
*Is there a way to raise the issue with Samsung so they can address it in a future update? Or does anyone know of a temporary fix?
To solve the problem you can have your home and work address saved as a safe place and the phone will not lock at those locations.
For me this helps to not use the fingerprint scanner all of the time. I also never have a problem with it anyways.
Sent from my SM-G935V using XDA-Developers mobile app
Good suggestion, thanks for that : )
I'm hoping Samsung acknowledge the issue and fix the problem soon. TBH, I'm surprised more people haven't encountered and complained about the issue. I noticed it within a day of getting the phone. Perhaps people don't bother with fingerprint unlock? Either way, fingers crossed an update comes soon.
I traded out for a Note 5 and its MM update is doing the exact same thing. I switched to a pattern backup and I think its working much better.
I am going to try that new Good Lock that updates the UI. Running good and will report if its still broken or if it fixes the fingerprint reader.
Did some testing of my own. Issue is not present with goodlock. Did you find the same mate?
player911 said:
IWhen you have a bunch of notifications, you select one to open, the pin screen comes up, and occasionally doesnt take fingerprints. Its like it's looking for ONLY the pin. Weird.
Click to expand...
Click to collapse
Same identical problem here. It worked only one time, after that it doesn't worked anymore.
Good Lock is a modified (perhaps the next gen?) TouchWiz silently released by Samsung that is still very much in its alpha/beta stages.
Info and download link: http://9to5google.com/2016/04/04/samsung-good-lock-update-bug-fixes/
Ironic that the fingerprint bug plagues touchwiz, but doesn't seem to be present in this new good lock system UI.
invision1 said:
Good Lock is a modified (perhaps the next gen?) TouchWiz silently released by Samsung that is still very much in its alpha/beta stages.
Info and download link: http://9to5google.com/2016/04/04/samsung-good-lock-update-bug-fixes/
Ironic that the fingerprint bug plagues touchwiz, but doesn't seem to be present in this new good lock system UI.
Click to expand...
Click to collapse
I will wait for more stable version, in the meantime I continue to keep this annoying bug. I just don't understand why if it is a bug, most people doesn't have this problem.
Sended from my Samsung Galaxy S7 Edge Gold Platinum
That's a really good question. It's am extremely annoying bug that I keep running into multiple times on a daily basis.
If anyone knows how to officially report bugs to samsung please share. I'm not going to hold my breath though. Seeing as I am on a carrier firmware, the update could take quite a while before I see it on my phone. That's assuming samsung even fix the bug in the ubranded firmwares.
Grr
Apparently yestrday a dutch user got a new update on his phone. I have an unbranded phone, i will wait for it. I keep you guys posted.
invision1 said:
That's a really good question. It's am extremely annoying bug that I keep running into multiple times on a daily basis.
If anyone knows how to officially report bugs to samsung please share. I'm not going to hold my breath though. Seeing as I am on a carrier firmware, the update could take quite a while before I see it on my phone. That's assuming samsung even fix the bug in the ubranded firmwares.
Grr
Click to expand...
Click to collapse
Could it be an hardware issue? Has anyone installed last Samsung's update? Maybe it solve this issue too.
I doubt it's a hardware issue. the fingerprint reader works fine, it's only on the screen described above is when it works inconsistently. And it doesn't happen on the good lock interface. All of this clearly points to a software bug, not a hardware issue
I haven't received any need update yet but if you do please post your results!
invision1 said:
I doubt it's a hardware issue. the fingerprint reader works fine, it's only on the screen described above is when it works inconsistently. And it doesn't happen on the good lock interface. All of this clearly points to a software bug, not a hardware issue
I haven't received any need update yet but if you do please post your results!
Click to expand...
Click to collapse
I didn't tried Good Lock yet, but i wonder why some users have this issue and others have not. Anyway when i will receive the update i'll let you know
hi to all how any one that has the same setup will help me understand i will try and keep it short first im using samsung note 4 running 6.0.1 now
ok so here goes i use my gear 2 together with my note 4 as a trusted device you know like every time the gear 2 is close the device must stay unlocked but it does not stay unlocked and there is no Bluetooth disconnecting anything like this i look at that so battery is full the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage but i connect it now and its fine but after a wile (don't know the exact time here ) but say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on and there was nothing like it disconnecting it is as if the phone on its own make sure that it asks the finger print every now and again say like i leave it overnight the next morning first fingerprint then you can use the phone i hate this it kind of bugs me if the steal the phone and the range is to big the device will lock any way why lock when the gear 2 it near the phone any help please
honestly, i stopped reading after few seconds.
have you ever heard about punctuation? - you know, the thing that looks like dots and commas, makes reading much easier.
244 characters in 1 sentence.
wow dude, looks like you dont wanna get helped.
biebie29 said:
...say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on...
Click to expand...
Click to collapse
From the Google Smart Lock support page (https://support.google.com/nexus/answer/6093922):
"Note: When you don't use your phone for 4 hours, and after you reboot your phone, you'll need to manually unlock it with your PIN, pattern or password"
It's a security feature.
EDIT: ...and, wow, yes, that was some run-on sentence!
Is there a root app to disable it or not
biebie29 said:
Hi to all. How any one that has the same setup will help me understand. I will try and keep it short. First, i'm using samsung note 4 running 6.0.1 now.
Ok, so here goes:
I use my gear 2 together with my note 4 as a trusted device. You know like every time the gear 2 is close, the device must stay unlocked. But it does not stay unlocked and there is no Bluetooth disconnecting, anything like this. I looked at that. Battery is full, the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage.
I connect it now and its fine, but after a while (don't know the exact time here ), say after 3 hours of no use, i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near. The gear 2 is still on and there was nothing like disconnecting. As if the phone on its own make sure that it asks the finger print every now and again.
For example, i leave it overnight the next morning first fingerprint then you can use the phone.I hate this. It kind of bugs me if they steal the phone and the range is to big, the device will lock any way. Why lock when he gear 2 it near the phone? Any help please.
Click to expand...
Click to collapse
Fixed that for you
I really had to break that down to make it readable for me. But as others said, it's an Android feature. Afaik there is no way of disabling that all together. There might be some xposed module i haven't heard of, but with my moto360 i couldn't get it to work the way you'd want. Sorry mate
Kinsman-UK said:
It's a security feature
Click to expand...
Click to collapse
As the programmers use to says: Its a feature, not a bug
Some people are just plain jerks, and I wish XDA would take these "grammar police" trolls a bit more seriously and penalize them.
Perhaps OP is using a translator, or is from another country, or is young. That should not matter to any of us and we should offer our help regardless of whether he/she includes proper punctuation or not. I'm sure the effort he/she put into typing it was much greater than that of the ridiculous responses some of you gave.
thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing
biebie29 said:
thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing
Click to expand...
Click to collapse
The Note 4 is problematic all around, but 6.0.1 is a problem for every device that has it. It is the reason I left my Nexus 6P, and my Nexus 6. I have a Xiaomi Mi Max, also on 6.0.1 and it has the same major flaws I experienced on all devices running 6.0.1. The problems I speak of are the WiFi and Data stop working briefly while browsing the web, or downloading something. However, I believe this is an issue related to the security patches related to Qualcomm devices on 6.0.1. It seems like an overall radio problem.
I wonder If someone knows any rom or any method for enabling Ok google detection when screen off
I had the feature in nexus 5x..and it is lot lot useful
Not at this time on OOS (any version). I've not heard of any custom ROM with that feature as your question has been discussed a number of times. I posted a clumsy work around when the OP5 is in a charger using two apps but I only do that because I use the phone as a Google Home and want to avoid screen burn-in.
Ah ok, understand
Well, about your workaround, dont you think it might be harmful for the phone to be pluged in all the time?
http://www.droidviews.com/force-ok-google-detection-screen-off/
I had also seen a Xposed module that had this option. I don't remember the name. Maybe you can try some combinations of google now search etc. in the xposed repository.
Great find. thanks, but like others in the comment section of the article this doesn't work with the OP5 with OOS. When the battery set command is activated it automatically turns the screen back on. So the normal lockscreen timeout goes into an endless loop of screen off then automatically back on, not something you could tolerate. There may be a way to work around by adding another command but so far I've not found a compatible command. Tasker's own Sys Lock isn't an option as it forces a pin/swipe unlock (no fingerprint) and definitely cuts off trusted voice.
Hmm ok, thanks both! So maybe it would work with custom roms then...but for now is not my plan. But thanks anyway
Ok thank you! I've not installed Xposed yet but I note it so I will check when I do
My brother passed away and was using this phone until a couple of weeks ago. I don't have the lockscreen pattern but I'm trying to do a little detective work regarding my brothers last activity. I reached out to law enforcement, but they don't have an active investigation and they suggested that I reach out to his cell provider [Tracfone] which I might try. Of specific interest to me is his text message activity on the day of his death.
Anyhow I scoured the net and tried to beat the lockscreen via emergency dialer, and also tried to connect via adb shell and MTP. I also don't think the device was registered via the samsung tools. I'm at the point where the device told me I have 9 unlock attempts left and it will erase the device after. The lockscreen seems to appear at device power and I think that it might not have booted android completely at this point.
Is anybody aware of a method to bypass the lockscreen which would work on this device so I can look into the details surrounding his death?
Sort of desperate here. There seems to be some software called Dr Fone that claims to have a lockscreen removal. However not sure that it works and on this device.
I may have a solution for this if you are wanting to preserve data if not check around on youtube for a video on FRP resetting this. I might have wrote a tutorial on this somewhere but I cant remember atm. Basically if you don't want to preserve the devices data (your brothers as you say) then you will simply factory reset it and then follow an FRP Removal tutorial you can find on here and or youtube.
btw nice leet username =]
phonecapone said:
I may have a solution for this if you are wanting to preserve data if not check around on youtube for a video on FRP resetting this. I might have wrote a tutorial on this somewhere but I cant remember atm. Basically if you don't want to preserve the devices data (your brothers as you say) then you will simply factory reset it and then follow an FRP Removal tutorial you can find on here and or youtube.
btw nice leet username =
Click to expand...
Click to collapse
Speaking of nice usernames
If you're still around, I have an old J327t1 that I had dropped and broke the screen on a few years ago. I recently fixed it, but can't remember PIN. I would like to preserve the data and am interested in what you have
veryspecialagent said:
Speaking of nice usernames
If you're still around, I have an old J327t1 that I had dropped and broke the screen on a few years ago. I recently fixed it, but can't remember PIN. I would like to preserve the data and am interested in what you have
Click to expand...
Click to collapse
All you need to do is find a recovery for that and flash it then go into the lock files and remove those. You can find some guides here on XDA or on youtube.
This was before I got into development, so adb isn't enabled, bootloader is still locked, and the phone is not rooted, so I'm skeptical I'd be able to flash. It's also running (I believe) Marshmallow, and most of those "find and delete lock settings" methods were for 4.x Kit-Kat and below. I could be wrong though.
If you have a particular thread in your watch list, I'd be grateful for the link.
I've been all over looking for a solution, hence me posting in here as opposed to creating a thread. Didn't want to reinvent the wheel if I didn't have to.
Despite the above limitations, the device has not received any updates since June 2017, it DOES go into MTP mode when I hook it to my laptop, and I have verified that it is vulnerable to the Mtpwn exploit.
noidodroid said:
All you need to do is find a recovery for that and flash it then go into the lock files and remove those. You can find some guides here on XDA or on youtube.
Click to expand...
Click to collapse
Also, I turned a moto g7 Play into a Nethunter device and had tried Android PIN Bruteforce, but after entering in so many PINs it would make me wait 30 seconds to try again and I couldn't figure out how to get my g7 to keep the screen of the J3 on. Or wake it back up, since it requires you to hit power then swipe the screen.
I ended up wiping it because it had Pie and no workaround for the wifi throttling, and installed Q. It's rooted, but I haven't set up nethunter back up on it yet. I do have an S5 that I has Nethunter, but haven't set it up with HID support yet. Plus, the battery on that would drain too quickly to use for this process.