Related
Just flashed lollipop and everything works perfect except for Bluetooth. Phone simply says there are no other Bluetooth devices in range, and those devices can't see the nexus. I tried rebooting, factory reset, re-flashing stock lollipop using flash-all batch and even Wug toolkit just to cover all my options but still no work around. Anyone else experience this problem or can think of a way to fix it? Anything would help.
Wipe Cache
TheRoice said:
Just flashed lollipop and everything works perfect except for Bluetooth. Phone simply says there are no other Bluetooth devices in range, and those devices can't see the nexus. I tried rebooting, factory reset, re-flashing stock lollipop using flash-all batch and even Wug toolkit just to cover all my options but still no work around. Anyone else experience this problem or can think of a way to fix it? Anything would help.
Click to expand...
Click to collapse
Hi, one of my friend faced similar issue and wiping the cache from recovery helped solve the issue.
Try wiping cache and reboot.
pppp6071 said:
Hi, one of my friend faced similar issue and wiping the cache from recovery helped solve the issue.
Try wiping cache and reboot.
Click to expand...
Click to collapse
Just tried the wipe and reboot but the issue is still persistent. I'm still looking around for a solution but nothing has come up yet. Thanks for the input though!
lollipop im nexus5 bluetooth unstable
I just downloaded the lollipop today on my NX5 and i have a bluetooth SENA smh10 for my helmet and it was working very fine before the update, now its unstable, iv to start the music app first on phone while connecting the bluetooth inorder to be able to control it via the bluetooth device, also for calls, i recieved a call and i opened but no sound was there, i tried to call, same happened, so i had to disconnect the device, make the call and then i connected again..after a while it worked and i made a call... Theres some bug in the bluetooth i guess as my smh was working fine before. Also iv a problem in some wedges not responding like the data on off one. Oh yes..and battery empties SO Fast
TheRoice said:
Just tried the wipe and reboot but the issue is still persistent. I'm still looking around for a solution but nothing has come up yet. Thanks for the input though!
Click to expand...
Click to collapse
So I solved the issue. Re-flashed 5.0 to the device, rebooted, and wiped cache. It still didn't pick up bluetooth as of last night but it worked this morning. Also, for any android wear users (or at least moto 360) the phone wouldn't pick up the watch until I did factory reset on the watch and opened android wear on the phone itself in order to accept terms and conditions.
@TheRoice
thanks, has worked for me :good:
Hi
When I woke up today my fingerprint scanner stopped working. It have done so before, but fixed itself. Today I have not been able to unlock phone once, if I don't delete current fingerprints and add a new. It then works for half an hour or so and then it can't recognize my finger anymore.
I have tried to wipe cache on Fingerprint scanner and wipe normal cache + Dalvik cache.
Anyone know any fixes for this?
Thanks in advance
Dirt or damaged finger.
Have you tried cleaning the actual scanner with a cloth? That usually works for me. I've noticed that when my thumb is even slightly rough or has a cut in it it no longer works. Maybe try another finger?
Faspaiso said:
Hi
When I woke up today my fingerprint scanner stopped working. It have done so before, but fixed itself. Today I have not been able to unlock phone once, if I don't delete current fingerprints and add a new. It then works for half an hour or so and then it can't recognize my finger anymore.
I have tried to wipe cache on Fingerprint scanner and wipe normal cache + Dalvik cache.
Anyone know any fixes for this?
Thanks in advance
Click to expand...
Click to collapse
Did you remember to flash the Bootloader and Modem when you upgraded to 5.1.1 for your S6 variant?
d2d2d2d2 said:
Did you remember to flash the Bootloader and Modem when you upgraded to 5.1.1 for your S6 variant?
Click to expand...
Click to collapse
It has worked flawlessly for over a month. Just started today. Over a month since I upgraded.
If your on custom ROM flash stock 5.1.1 ROM via odin. If your on stock ROM bring your S6 back to Samsung for warranty repair.
i have s6 dual sim international version SM-G920FD
after updating to 5.1.1 i have weird problem
if i play music then lock the phone ,the sound become noisy and repetitive and the normal speed is changed
this happens with the phone speaker and the head phone(lt channel)
i really don't think its a hardware problem as if i turned the lock on (even if i don't unlock the device just keep the screen on) the problem disappears then come back after the screen turned off
i did factory reset but nothing changed
help plz
hardyboy_samy said:
i have s6 dual sim international version SM-G920FD
after updating to 5.1.1 i have weird problem
if i play music then lock the phone ,the sound become noisy and repetitive and the normal speed is changed
this happens with the phone speaker and the head phone(lt channel)
i really don't think its a hardware problem as if i turned the lock on (even if i don't unlock the device just keep the screen on) the problem disappears then come back after the screen turned off
i did factory reset but nothing changed
help plz
Click to expand...
Click to collapse
Does this happen with all the music players or did you just notice this with the stock samsung music player? If yes, try out poweramp or google play music and check whether the issue still persists.
This is apparently an issue for 5.1.1 update. I have been experiencing this issue and it is very annoying. I cleared "Music" app cache and data, I went to recovery and cleared cache data, and I even wiped my phone clean and installed a fresh 5.1.1 OS. I thought the last one would fix it, but the issue reappeared a few days ago. I hope someone can find a fix for this soon.
I tried other music players and the problem persists.
ultraquantum said:
Does this happen with all the music players or did you just notice this with the stock samsung music player? If yes, try out poweramp or google play music and check whether the issue still persists.
Click to expand...
Click to collapse
it happens with play music and jetaudio plus ..... it's very annoying
Makxx said:
This is apparently an issue for 5.1.1 update. I have been experiencing this issue and it is very annoying. I cleared "Music" app cache and data, I went to recovery and cleared cache data, and I even wiped my phone clean and installed a fresh 5.1.1 OS. I thought the last one would fix it, but the issue reappeared a few days ago. I hope someone can find a fix for this soon.
I tried other music players and the problem persists.
Click to expand...
Click to collapse
Is that PowerAMP also got this problem?
I have tried Power Amp and it's working great so far. I hope it won't crash anymore and I'll purchase the pro version.
I'm on 920f and luckily I don't have this problem (on h3g uk)
TheEndHK said:
Is that PowerAMP also got this problem?
Click to expand...
Click to collapse
yes bro but little less severe
Try going to download mode and wipe cache. If it does not work do a full reset.
roydok said:
Try going to download mode and wipe cache. If it does not work do a full reset.
Click to expand...
Click to collapse
i already did that many times but it didn't solve the problem
i really need a way to format system and install a fresh one but i think that needs rooting and custom recovery with probability of not solving the problem
hardyboy_samy said:
i already did that many times but it didn't solve the problem
i really need a way to format system and install a fresh one but i think that needs rooting and custom recovery with probability of not solving the problem
Click to expand...
Click to collapse
You don't need to root the system just to install a fresh OS. I did that, but the bug just kept coming back. If you really want to try a clean install, just download the ROM for your region/carrier and use Odin to flash. It doesn't require root and doesn't trip Knox counter.
Hi,
After updating to 7.0 nougat by official Europe update,
My fingerprint sensor stopped responding, when I'm trying to add new fingerprint it wouldn't let me even try, It shows a message (Attention: make sure that the home key is clean and dry, then try again) and then it goes back to the main lock screen settings menu.
I'm really desperate, already tried everything, plz help!
:crying:
Ronohayon10 said:
Hi,
After updating to 7.0 nougat by official Europe update,
My fingerprint sensor stopped responding, when I'm trying to add new fingerprint it wouldn't let me even try, It shows a message (Attention: make sure that the home key is clean and dry, then try again) and then it goes back to the main lock screen settings menu.
I'm really desperate, already tried everything, plz help!
:crying:
Click to expand...
Click to collapse
Have you tried to factory reset or just flash android 7.0 with Odin. I would recommend wiping after installing an update like 7.0 anyway updating always causes bugs and issues for me.
dylanneve1 said:
Have you tried to factory reset or just flash android 7.0 with Odin. I would recommend wiping after installing an update like 7.0 anyway updating always causes bugs and issues for me.
Click to expand...
Click to collapse
I also just updated my SM-G935FD via OTA to Android version 7.0.
Since then, fingerprint scanner is not working. Like for OP, all tests fail under HwModuleTest.
I tried to remove all fingerprints, but it is impossible to add new fingerprints - the error message is "Make sure that the Home key is clean and dry, then try again." Obviously, the fingerprint sensor is as dry and clean as it was before the update (when it worked perfectly).
Since then I tried, unsuccessfully:
- removing old fingerprints and adding new fingerprints (does not work, cf. above)
- formatting cache partition
- performing a hardware reset
- flashed the stock firmware G935FXXU1DQB3 with Odin
Please advice, thanks.
happiness_is_a_process said:
I also just updated my SM-G935FD via OTA to Android version 7.0.
Since then, fingerprint scanner is not working. Like for OP, all tests fail under HwModuleTest.
I tried to remove all fingerprints, but it is impossible to add new fingerprints - the error message is "Make sure that the Home key is clean and dry, then try again." Obviously, the fingerprint sensor is as dry and clean as it was before the update (when it worked perfectly).
Since then I tried, unsuccessfully:
- removing old fingerprints and adding new fingerprints (does not work, cf. above)
- formatting cache partition
- performing a hardware reset
- flashed the stock firmware G935FXXU1DQB3 with Odin
Please advice, thanks.
Click to expand...
Click to collapse
If you have tried to flash stock firmware in Odin, I'm really not sure what the issue is, if it was just a glitch in the software it should probably have been fixed by a wipe and flash with Odin. If your phone is still under warranty I would bring it back into the Samsung shop or contact them over the internet to inquire about fixing it.
The same exact problem has happened to me too . I'm tired of unlocking with patterns
What should we do ?
This cannot be a hardware issue cuz phone was fine right before the update
---------- Post added at 08:16 AM ---------- Previous post was at 08:15 AM ----------
Ronohayon10 said:
Hi,
After updating to 7.0 nougat by official Europe update,
My fingerprint sensor stopped responding, when I'm trying to add new fingerprint it wouldn't let me even try, It shows a message (Attention: make sure that the home key is clean and dry, then try again) and then it goes back to the main lock screen settings menu.
I'm really desperate, already tried everything, plz help!
:crying:
Click to expand...
Click to collapse
Do you still have the issue ?
I have the same problem ???
What the way to fix this issue
I had that problem sometimes and in the end the main reason was really sweat on my fingers and dirt on the home button.
I know this doesn't sound like a solution, but it surprised me as well. Just try drying your fingers and clean the surface of the home button.
Hi There! I encountered the same issue earlier but then suddenly my fingerprint sensor works normally. The last thing I that I made changes to my phone was to reset the password of my samsung account. Not if there was a security breach that happened but after resetting the password, works fine for me. I suggest that you back up your phone's data before and after resetting your Samsung account.
I have this problem for 1 year, tried to change the password but didnt work.
IS someone still struggling with this problem ? Yesterday i upgraded to DevBase 6.0 Oreo newest build. But after the flashing process the fingerprint sensor act in a unusual manner. Sometimes i could unlock the phone sometimes it directly jumps to the pattern unlock screen. Any news about the problem ? I wiped cache/dalvik and i resetted my password of the samsung account - nothing helps.
Any help, ideas, links are highly appreciated
Cheers
Rhonin
Hi folks,
I've just updated my one plus 6 to android 10 and I already have many problems. The rotation and the automatic brightness are not working anymore. Plus, when you try to put your phone near your ear to listen to an audio message on WhatsApp is not working as well. Am I the only one with these problems?
Thanks
Same here.
Is this a bug or did I something wrong?
mine worked perfectly fine. but i find some issues where when i type on my keyboard it's little bit laggy. that's bother me a lot. so i had to soft reboot it
I get the same issues.. I'd fixed with factory reset, now everything works fine
I wasn't getting notifications of missed calls so factory reset. Then I couldn't access my contacts with the message saying something like, you haven't given all permissions. I downloaded another call app and gave all permissions. It worked fine, so I deleted it and gave all permissions to the OnePlus phone app (including location which I'm sure I never had to give previous). It now works...
rrubio999 said:
I get the same issues.. I'd fixed with factory reset, now everything works fine
Click to expand...
Click to collapse
Oh my... I don't want to do a factory reset ?
I fixed it by uninstalling Magisk via TWRP (there's now an easy guide to install it in Android 10), rebooting to system, check if the sensors are working again, and then reinstalling Magisk through TWRP again. If this happens again just re-do the procedure, an update will probably fix this.
my sensors went bad when first installing the open beta 30, but with a cache wipe in the recovery, everything should be back to normal again. Well, in my case it was so you should give it a shot as well
HighOnLinux said:
my sensors went bad when first installing the open beta 30, but with a cache wipe in the recovery, everything should be back to normal again. Well, in my case it was so you should give it a shot as well
Click to expand...
Click to collapse
I usally don't post comments on this forum but i would like to thank you. I had the same sensor issues since Android 10 and it really grinded my gears..
Just wiped cache from recovery and voila, the auto rotate works like a charm.
Thank you very much my friend and have a great day! :good: