Database Users

Anyone else with i9505G having this particular Bluetooth issue?

Folks whose devices fit the criteria of what I have (see attached screenshot of my "About Phone" screen), please read on. I say this only so I can figure out what is common between us to be having the following Bluetooth issue:
1) Bluetooth toggle switch is OFF.
2) You slide the switch to "on". The phone sits there for approximately 10-15 seconds, but Bluetooth doesn't come on at any point, eventually the toggle switch in settings slides back to OFF.
3) There is no setting/method in the device that will turn Bluetooth on.
From when I received the phone from Google Play store, the only thing I have done to it is root it following this method.
Clearly, something with the rooting process did this (I am also having one other issue, but that one is less annoying than this Bluetooth one). But everything in my phone points to me still having the stock ROM but just having root access.
If I can just see the common thread between my phone and others having the same issue, maybe I can figure it out.
I don't want to flash my ROM or start from scratch for the fear of making matters worst for myself; the device appears to be working fine otherwise.
If I am completely unable to fix this, my only hope is that the eventual release of 4.4 KitKat would fix it on its own (and probably break my root at that point, haha).

After searching high and low for an answer to this, I ended up doing a factory reset (Menu-->Settings-->Backup & Reset-->Factory Data Reset) and that resolved the issue (while wiping my phone).
Thanks to the Android OS, I let my phone charge overnight while on WiFi and by the morning all the apps were reinstalled and updated, including the OS itself. My Kernal/Baseband/Build versions are all back to the ones I had when I got the phone from the Google Store, so that's comforting.
Now, I just have to find the absolute least intrusive way to root my phone without any ROMs or system-level updates that could screw up stuff like Bluetooth or USB Connectivity for me.

[Q] Note 3 N9005 - LTE - No Display

few days ago during phone calls the screen started to black out - after 1 hoursof first blackout, screen started to show weird behavior, screen was being touched on random areas - i turned on show touches from dev mode and it showed random multi touches on top right corner of scree. after few minutes the screen turned black and since then i havent seen any sort of display on my note 3. i tried.
1. removed battery - let it rest for 15 minutes - connected back - phone turned on fine i could hear all sounds and notifications even receive calls if i swiped at correct screen area, However no display
2. tried to access the phone in adb but it wont show in devices even though usb debugging is enabled and all samsung drivers are correctly configured.
3. made backup of all the files on phone using kies.
4. Rooted the phone and tried to access recovery mode but vol up + home + power just turns on the phone.
5. currently the phone connects to pc as a media device with usb debugging enabled.
i think if i am able to flash firmware again it might resolve the issue, but so far i haven't been able to find latest stock builds that i can flash using odin since i cannot do anything in recovery mode (no display)
Can someone guide me on how i can get the display back ? is there any way to access the screen using a standalone pc app without the need to install any app on the phone ? can it be hardware related issue ? the phone never dropped, im a very careful user. screen is scratchless and phone is in perfect condition physically. Any help or guidance will be appreciated.
PS. Its my first time posting a thread on a forum, i hope i didnt break any rules. I searched alot on forums for someone having similar situation.

samdada47 said:
few days ago during phone calls the screen started to black out - after 1 hoursof first blackout, screen started to show weird behavior, screen was being touched on random areas - i turned on show touches from dev mode and it showed random multi touches on top right corner of scree. after few minutes the screen turned black and since then i havent seen any sort of display on my note 3. i tried.
1. removed battery - let it rest for 15 minutes - connected back - phone turned on fine i could hear all sounds and notifications even receive calls if i swiped at correct screen area, However no display
2. tried to access the phone in adb but it wont show in devices even though usb debugging is enabled and all samsung drivers are correctly configured.
3. made backup of all the files on phone using kies.
4. Rooted the phone and tried to access recovery mode but vol up + home + power just turns on the phone.
5. currently the phone connects to pc as a media device with usb debugging enabled.
i think if i am able to flash firmware again it might resolve the issue, but so far i haven't been able to find latest stock builds that i can flash using odin since i cannot do anything in recovery mode (no display)
Can someone guide me on how i can get the display back ? is there any way to access the screen using a standalone pc app without the need to install any app on the phone ? can it be hardware related issue ? the phone never dropped, im a very careful user. screen is scratchless and phone is in perfect condition physically. Any help or guidance will be appreciated.
PS. Its my first time posting a thread on a forum, i hope i didnt break any rules. I searched alot on forums for someone having similar situation.
Click to expand...
Click to collapse
2. To access via adb you have to grant the permission, once you connect phone in adb with developer mode (usb debugging) enabled, a pop-up will come asking for granting permission., once you grant then only you can acces it in adb mode.
*Sorry buddy, i don'y know about any app that can "access the screen using a standalone pc". (Google for it, You may found)
I guess it must be hardware issues,
But you can try out this:
Download the latest firmware from SamMobile or from SamsungUpdates website, and flash using ODIN.
Before downloading firmware make sure you download the correct firmware for your region (CSC)
If didn't worked, it must be a hardware issue.
Sorry.

Phone was in usb debugging mode before screen disappeared, now i cannot see the device in adb mode maybe because i need to change the connection mode to mtp, i cant do that , theres no display :S

Help S7Edge Nougat - Two finger scroll/tap (talkback off) won't go away

Hi together,
just was able to update to upgrade to Nougat. (O2 Germany)
I just have one big problem. I have to control the screen like Talkback is activated. But it isn't. (two finger scroll, tap and so on)
Does anybody have an idea how I get rid of that really annoying thing? If possible without factory reset. My Phone isnt rooted.
My Google and forum search hasn't helped me. The answers were always turn off Talkback, which it is already.

Royalblue said:
Hi together,
just was able to update to upgrade to Nougat. (O2 Germany)
I just have one big problem. I have to control the screen like Talkback is activated. But it isn't. (two finger scroll, tap and so on)
Does anybody have an idea how I get rid of that really annoying thing? If possible without factory reset. My Phone isnt rooted.
My Google and forum search hasn't helped me. The answers were always turn off Talkback, which it is already.
Click to expand...
Click to collapse
I had the same problem yesterday after the update, took some time to change back to normal behavior: restarted in safe mode, changed the resolution back to WQHD, changed some accessibility settings, like turning it on for Nova Launcher and turn off optical reader (I don't know why it was turned on...). After that I restarted to normal and seemed to work ok but then I turned on the accessibility feature optical reader again, too see what it does and the screen was only with 2 finger operable again, so I turned it off.
You can disable/remove Talkback in the application settings. Try in safe mode if it's not possible in normal mode. I tried to change the Talkback settings in the system settings (searched for Talkback) and it said in a pop-up that it isn't compatible with the system, so I removed it completely.

Thank you so much norti!!!!!!!!! Had the same issue with S7 (T-Mobile USA), and your advice helped!!! Actually, it was the only one I could find so far

Thank you Norti
Thank you so much. I had the same problem after performing the software update over night last night. I was so frustrated with it and the techs at the sprint store spent an hour with my phone and could not fix it. The techs recommended that I back up all my contacts and everything and then do a factory reset. I did not want to do a factory reset and searched the internet for a long time before coming across your post. I turned off optical reader and it fixed the two finger problem. Thank you so much for sharing this as I would have been lost without it.

Exactly the same happened with my S7 edge, almost drove me crazy before I figured out that it was Optical reader in accessibility that caused the problem.

That worked
Thank you for the correct fix post. Optical Reader off did it for me, too. Spent all morning wading through "Cool features of Nougat" and getting ready to break my S7 while calls were coming in...
norti said:
I had the same problem yesterday after the update, took some time to change back to normal behavior: restarted in safe mode, changed the resolution back to WQHD, changed some accessibility settings, like turning it on for Nova Launcher and turn off optical reader (I don't know why it was turned on...). After that I restarted to normal and seemed to work ok but then I turned on the accessibility feature optical reader again, too see what it does and the screen was only with 2 finger operable again, so I turned it off.
You can disable/remove Talkback in the application settings. Try in safe mode if it's not possible in normal mode. I tried to change the Talkback settings in the system settings (searched for Talkback) and it said in a pop-up that it isn't compatible with the system, so I removed it completely.
Click to expand...
Click to collapse

I figured that it had to be the optical reader as that was one of the incompatible apps it reinstalled after the upgrade. Had to use two fingers to get through most menu-options, frustrating, to manage to disable it. Glad to see I wasn't the only ripping my Hair out experiencing this issue. Hope they fix it.

For future reference (in German):
This works:
Einstellungen > Eingabehilfe > "Text & Bildscanner": turn off ("Aus")

OP8 Pro is not able to connect to my WearOS watch (Fossil Sport)

Hey guys, I have a new OP8 Pro and tried to connect it to my Fossil Sport smartwatch. The problem is that I am not even able to connect it. I did a factory reset on my watch and started the linking process in the wearOS app. Everything works fine until I select the my watch to connect. My phone asks me the check the code (it matches to the one on my watch) and after pressing pair, the phone continues with the process but the watch keeps telling me that my phone wants to connect and shows me the bt connect code. After 1/6 of the "getting informations from your watch" the app doesnt do sh*t anymore. I noticed that that the bt connection to my watch is disconnecting and connecting again and again but doesnt stay connected.
My troubleshooting is exactly Pike this redet post: https://amp.reddit.com/r/WearOS/comments/f20lxm/oneplus_7t_and_fossil_sport_not_connecting_help/
Unfortunely there isnt a solution to the problem. So maybe here is someone who had the same issue
I tried connecting my watch to another phone and it works perfectly so it is definitely a problem with my OP8.
Glad about any help. Thanks a lot!
Greetings
Marcel

I use a Fossil Sport, and had this same issue when I originally set mine up. I wish I had a better answer, but I just tried and tried again until it worked. Between each attempt I cleared everything I could think of. Reset the watch, cleared google play services cache, cleared wear os app cache, reinstalled the wear os app, manually removed the watch from bluetooth settings, reset network settings, I'm probably forgetting some things, but it did eventually connect. Frustrating, and I'm sorry I don't remember exactly what fixed it, but the good news is it will eventually work.

I don't have a sport but I have a gen 5 and there was no issue and I have had to reset and reconnect a couple times.
Best of luck!

I have a gen 5 and the devices are connect because i receive the notify but on the top of the smartwatch there is the cloud of the no connection... I think therr are some problem with the bluetooth of this phone

Wingdom said:
I use a Fossil Sport, and had this same issue when I originally set mine up. I wish I had a better answer, but I just tried and tried again until it worked. Between each attempt I cleared everything I could think of. Reset the watch, cleared google play services cache, cleared wear os app cache, reinstalled the wear os app, manually removed the watch from bluetooth settings, reset network settings, I'm probably forgetting some things, but it did eventually connect. Frustrating, and I'm sorry I don't remember exactly what fixed it, but the good news is it will eventually work.
Click to expand...
Click to collapse
Thank you very mich for the reply. I've already done that at least 20 times, but at least there is hope that it will eventually work one time/day. Really frustrating and I hope they will fix this soon so when I have to reset my phone someday I will at least not have this problem again. :silly:

Okay guys it finally worked. Im not sure why, didnt do anything else but reinstalling, deleting chache and data of WearOS and Google play Services and resetting my watch. I can only imagine that it was because the languages of my phone and my watch didnt match. My phone is in english and I set my watch to german. It worked when I set up my watch in english (GB). I really dont know if that really was the solution or if it was just luck this time because i tried english (US) before that and it didnt work. So to anyone who is having the same problem I hope I can help you with this and hang on... I'll work sometime

vuoshino said:
I have a gen 5 and the devices are connect because i receive the notify but on the top of the smartwatch there is the cloud of the no connection... I think therr are some problem with the bluetooth of this phone
Click to expand...
Click to collapse
I have the same problem with my Huawei watch gen 1. I need to reboot my phone every time if I want that cloud-icon disappear on my watch.

Eremitus said:
I have the same problem with my Huawei watch gen 1. I need to reboot my phone every time if I want that cloud-icon disappear on my watch.
Click to expand...
Click to collapse
Did you try changing the WearOS App's battery setting to not optimise and lock it in the background?

PaterProx said:
Did you try changing the WearOS App's battery setting to not optimise and lock it in the background?
Click to expand...
Click to collapse
Yes i tried. Everything works good but there is the same icon on the top...

PaterProx said:
Did you try changing the WearOS App's battery setting to not optimise and lock it in the background?
Click to expand...
Click to collapse
I have changed it already to "not optimized", but haven't locked it in the background tho.. need to try that too. Quite annoying.

[New][July-16-2020]Unlocking bootloader on VZW Pixel 1 and XL

AS OF JUL 19 THIS HAS STOPPED WORKING
I apologize if you did not get your bootloader unlocking!
At the moment, there is no information if the classic exploit will return, if it has worked for you, please make a post about it on this thread!
We will go back to work to ensure pixels will get unlocked. I do not know how long it may take, it could be a few days, a few months or a few years. For this reason I'd respectfully ask you for no ETAs on the development on the exploit.
I may keep this thread open if people are willing to crack on something or need help.
Thanks for understanding.
----
I wanted to make a new thread to clean things up as the correct answer is buried so far into the VZW thread and I don't believe people have time to dig down that far to do something so simple.
Please give @RaspberryPiBen a thanks by going to his quote for finalizing my rant and making it into doable steps.
The work by the community is absolutely incredible.
RaspberryPiBen said:
Here is what worked for me:
Prerequisites:
No SIM card in the phone
ADB and Platform Tools installed on a computer (https://www.xda-developers.com/install-adb-windows-macos-linux/)
The latest OTA image downloaded to the computer (https://developers.google.com/android/ota#sailfish for the Pixel or https://developers.google.com/android/ota#marlin for the Pixel XL)
The phone connected to the computer with USB
Learn how to use ADB and Fastboot on your computer as it can differ.
Steps:
1. On the phone, open Settings>System>Reset Options and factory reset the phone. It should say "Restarting" or something similar.
2. When the screen goes black, press and hold the Volume Down key until you get into the Bootloader mode. Use the volume keys to navigate to "Recovery Mode" and select it with the power button.
3. Hold the Volume Down key for about a minute (while it resets) until you see an android lying down.
4. Hold the Power button then press the Volume Up button once. It should give you a menu.
5. Use the volume and power buttons to select "Wipe Data/Factory Reset" and confirm the reset.
6. Once it finishes, select an option that is something like "Sideload OTA"
7. Go to your computer and type in 'adb sideload sailfish-ota-qp1a.191005.007.a3-394b5899.zip' (without quotes) for the Pixel or 'adb sideload marlin-ota-qp1a.191005.007.a3-23002a57.zip' for the Pixel XL OR you may drag the zip file into the command prompt after typing "adb sideload", either way it should look similar.
8. Factory reset again from recovery mode
9. Reboot to system
10. While it just shows the G, press the power button until the phone restarts
11. Once it boots up, skip all of the steps but disable the options for sending information to Google.
12. Enable Developer Options by tapping "Build Number" seven times
13. In Developer Options, enable USB Debugging
14. On your computer, run 'adb shell pm uninstall --user 0 com.android.phone'
15. Reboot twice
16. Connect to WiFi
17. Open google.com in Chrome
18. Check Developer Options to see if you can enable OEM unlocking
19. If you can't, swipe away Settings from the Recents menu and go back to Chrome
20. In Chrome, open a bunch of websites. After opening each one, check the OEM Unlocking option again and close Settings afterward.
21. Once you can enable it, do so! Now you can unlock the bootloader.
Unlocking the bootloader:
-Reboot and press the Volume Down key when the screen goes black
-On the computer, type 'fastboot flashing unlock'
You just unlocked the bootloader!
Credit goes to djared704 for finding this method.
Let me know if I need to change anything about this guide.
Click to expand...
Click to collapse
for other reasons, you may see my rant
djared704 said:
Hey guys. After 5 months of my purchase I finally achieved bootloader unlocking. Basically I am a user that has never updated to latest, I don't know if it makes it a variable if you're already on latest and try this. (I was coming from Sept 2019). So what I did was factory reset from the system menus. Then as soon as the screen went black, I did bootloader combos and straight to recovery. I factory resetted as prep, flashed DECEMBER patch, then after that finished, factory resetted again. Essentially, I followed the classic ADB exploit that has "never worked since Sept-Oct 2019" And yes I do have the VZW_001 CID and "_VZ" in GL website. Know when yours is bootlooping as soon as you reboot it, just hard reboot so it boots up quicker, I don't know what it does for it to take so long. Anyways when you get in, just setup like we'd always do, NO google account, turn off all setting requests (Data location, wallpapers, etc). Then as soon as I got in, I turned on debugging, ran the classic adb pm command, rebooted TWO times. This means as soon as I booted, i swiped to go to home, then rebooted a second time. As soon as I did that, I loaded up my wifi connection, I don't know if it matters but Im using the 5G wifi, then I load up google.com. Immediately, I already notice something strange. Google.com doesn't have a "valid SSL certificate" I thought it was weird, so I went to google.com on my PC and look certified SSL. As I knew that was weird, I was clicking around and I thought that was enough. so I went to the dev menu. OEM lock still grayed out. I went back to chrome and simply typed in "youtube" Let it load up. Then I clicked on the site. I went back to the dev menu. Still grayed out. I exited settings app and relaunched it to the dev menu. OEM unlock lit up in flying colors. I could not believe it. I instantly ticked it with 0 hesitation and rebooted immediately to the bootloader. The unlock command worked! I am now unlocked sailfish! I thank the community so much for all the hard work. I, only motivated the community to their potential. Thank you again!
Generally there are some kinds of factors.
Users have stated before if you OTA'd from menus to Latest patch, it would say "October", even though it's really december. This may make the unlocking procedure impossible. I have also not seen any marlin users report back to me yet about this method. You can still try flashing from googles site if you're already on "October = Dec".
Enjoy guys. We proved WE own these phones, and not VZW.
Click to expand...
Click to collapse
I hope you enjoy this guys. Regarding it, I do not know how long it will stay for so I suggest to do it now. At the moment, I do not know if this will work for pixel 2 and so on. You may try it but if you have issues you must go to your device board. Thanks.

I Can Confirm it works on Sailfish... unlock my phone on the day its discovered (July 15 ).
Big Thanks

Can this method apply for pixel 2 XL Verizon with July patch 2020???

saibharath1319 said:
Can this method apply for pixel 2 XL Verizon with July patch 2020???
Click to expand...
Click to collapse
Please read the end of the post. Thanks.

Is there a way to donate to you?
I've been waiting for so long. You literally made my day.

omg... Thank you sooooooooo much! This just more life into my device! I bow to you sir

icarus1391 said:
Is there a way to donate to you?
I've been waiting for so long. You literally made my day.
Click to expand...
Click to collapse
I've updated my profile for my donate to my paypal - However only if you really feel! I'd be the same as happy if you just gave me and @RaspberryPiBen a thanks!

How long does it usually take for people to get the option active? I followed the steps 3 times and tried loading a bunch of websites but no luck unfortunately Maybe just need to keep trying?

MangoBento said:
How long does it usually take for people to get the option active? I followed the steps 3 times and tried loading a bunch of websites but no luck unfortunately Maybe just need to keep trying?
Click to expand...
Click to collapse
How much websites did you try to load? Did you go online only after uninstalling android.phone? Cheers.

Not sure, but I was at it for around 5 minutes with no luck.
And yes I only did wifi after uninstalling the android.phone like in the steps

MangoBento said:
Not sure, but I was at it for around 5 minutes with no luck.
And yes I only did wifi after uninstalling the android.phone like in the steps
Click to expand...
Click to collapse
Try a reboot and clear data of the settings app and visit various sites. Let me know how that goes. Cheers.

Tried that and still no luck.
Oh well, I'll probably keep trying tomorrow or something, not a huge fuss as I've since bought a new phone, but would've been nice to play around with custom ROMs on this pixel.
I went to check the IMEI number for my phone but it says "Unknown" in the settings now? Not sure if that contributes to it

djared704 said:
Try a reboot and clear data of the settings app and visit various sites. Let me know how that goes. Cheers.
Click to expand...
Click to collapse
So I tried following the bootloader unlock instructions 3 times but still couldn't get my oem unlock button to activate om the night of July 18. @djared704 What do you mean by clear data of the settings app, just like clear the app from recents?

Hi! Please, remember that the button may be greyed out, but it may be toggable anyway. So try to toggle it even though it's greyed out. Good luck!

MangoBento said:
Tried that and still no luck.
Oh well, I'll probably keep trying tomorrow or something, not a huge fuss as I've since bought a new phone, but would've been nice to play around with custom ROMs on this pixel.
I went to check the IMEI number for my phone but it says "Unknown" in the settings now? Not sure if that contributes to it
Click to expand...
Click to collapse
Same. Tried 3 times just now still no luck. XL here. My IMEI is unknown as well.

Luminoux said:
Same. Tried 3 times just now still no luck. XL here. My IMEI is unknown as well.
Click to expand...
Click to collapse
Your IMEI is either unknown due to uninstalling android.phone, or actual corrupted/blacklisted EFS. If true, nothing can be done about that.
When you reset the device, did you flash December Android 10, and in the setup process, disable all the requests (data location, wallpapers, etc).
Is there a sim card in the phone?
Cheers.

CLPose said:
Hi! Please, remember that the button may be greyed out, but it may be toggable anyway. So try to toggle it even though it's greyed out. Good luck!
Click to expand...
Click to collapse
I just retried the instructions and tried the toggle even though it was greyed out and it doesn't look like it worked. It wouldn't flip to "on" no matter how many websites I tried.

androidbad said:
I just retried the instructions and tried the toggle even though it was greyed out and it doesn't look like it worked. It wouldn't flip to on no matter how many websites I tried.
Click to expand...
Click to collapse
That's strange. Have you tried repeating the process a second time?

RaspberryPiBen said:
That's strange. Have you tried repeating the process a second time?
Click to expand...
Click to collapse
This was literally my 4th time trying. I bought my phone off eBay so I'm honestly not sure if it's a verizon variant. I tried a checking my IMEI on the Verizon and Google website, neither of them actually indicate that it's a Verizon phone. But if it's a Google phone I expected to be able to unlock my bootloader already... idk Maybe it came from Canada or somewhere else like the UK.

androidbad said:
This was literally my 4th time trying. I bought my phone off eBay so I'm honestly not sure if it's a verizon variant. I tried a checking my IMEI on the Verizon and Google website, neither of them actually indicate that it's a Verizon phone. But if it's a Google phone I expected to be able to unlock my bootloader already... idk Maybe it came from Canada or somewhere else like the UK.
Click to expand...
Click to collapse
If you can gather enough evidence that your device is a Google store device, you can go here.
To get a 50% chance of displaying actual correct device, you can download Simple CID Getter on the Play store.
Cheers. Let me know how it goes.