Hi All,
I have a Note pro 12.2 Wifi edition (SM-P900) with a bluetooth range of effectively 0. To get it to detect any other BT device i have to put the other device on top of the front facing camera or on the edge of the device close to there. If I move it a couple of centimeters(< 1 inch) the note pro disconnects. when for example the keyboard is touching the upper edge of the note pro and they are paired they work as expected but if I move it a couple of centimeters they disconnect . I tried this with a microsoft bt keyboard, an samsung s3 mini and a note 8.0 and it's the same issue. All the other devices work with each other as expected so it's definitely the note pro.
Things I've tried:
- complete wipe/factory reset
- 2 different oem firmwares flashed through Odin (now on the KOT49H.P900XXUANI1 build) + factory resets
- the latest cm11 release from the forum here
- set the BT visibility timeout to never
- tried with wifi off (just in case)
- tried with and without cover
I have some questions:
- Anyone faced something similar on this device?
- is there a fix or a suggestion I can try?
- is there a debug menu or tool for the Bluetooth to see numeric signal strength in dbm, kernel logs, etc.
- where can I find the pit file for this device? I didn't try complete repartitioning because I couldn't find the pit file.
- is there a disassembly guid for this device? I am tending to think it's either a disconnected (or broken soldering) BT antenna issue or a firmware bug and I prefere to check the disconnected antenna issue myself if it's doable rather than send it to Samsung for a couple of weeks of wait time.
- anything else I should think of ?
Thanks
fadi said:
Hi All,
I have a Note pro 12.2 Wifi edition (SM-P900) with a bluetooth range of effectively 0. To get it to detect any other BT device i have to put the other device on top of the front facing camera or on the edge of the device close to there. If I move it a couple of centimeters(< 1 inch) the note pro disconnects. when for example the keyboard is touching the upper edge of the note pro and they are paired they work as expected but if I move it a couple of centimeters they disconnect . I tried this with a microsoft bt keyboard, an samsung s3 mini and a note 8.0 and it's the same issue. All the other devices work with each other as expected so it's definitely the note pro.
Things I've tried:
- complete wipe/factory reset
- 2 different oem firmwares flashed through Odin (now on the KOT49H.P900XXUANI1 build) + factory resets
- the latest cm11 release from the forum here
- set the BT visibility timeout to never
- tried with wifi off (just in case)
- tried with and without cover
I have some questions:
- Anyone faced something similar on this device?
- is there a fix or a suggestion I can try?
- is there a debug menu or tool for the Bluetooth to see numeric signal strength in dbm, kernel logs, etc.
- where can I find the pit file for this device? I didn't try complete repartitioning because I couldn't find the pit file.
- is there a disassembly guid for this device? I am tending to think it's either a disconnected (or broken soldering) BT antenna issue or a firmware bug and I prefere to check the disconnected antenna issue myself if it's doable rather than send it to Samsung for a couple of weeks of wait time.
- anything else I should think of ?
Thanks
Click to expand...
Click to collapse
Hi!
To me this sounds like a hardware issue. A disconnected or improperly connected antenna is a very good bet.
Is this an issue that came along together with an update, or perhaps app installation?
If it´s an issue right from you recieved the tablet i´d send it back if it´s still under warranty.
I have previously removed the back of my -905. It´s not that difficult.
You´ll need a sturdy plastic separation tool of some kind. The back is very thightly attached with closely placed plastic clips so a fairly high amount of force is needed to begin with. A guitar pick won´t cut the mustard.
I found it easiest to lay the tablet down front facing downwards on something flat that lifts the tablet about an inch off the table. This gives your hand room for the "right angle of attack" I started at the top right next to the IR-diode.
Check this out:
https://drive.google.com/folderview?id=0B6oSLdL9TfFkSXYtVDVRQW1ZNHc&usp=sharing
Regards
Elo
Elo, Thanks.
I bought it as an immaculate second hand from ebay (it didn't have a tripped knox at the time) and had it for a month before getting a BT keyboard to use it with by which time I've already had routed it and tried different firmwares. So can't tell if it's a software update that messed it up.
In fact, I wasted a couple of days going through different firmwares before discovering the range issue by chance. At first I just thought it's an incompatibility between the keyboard and the tablet.
I will try to take it apart; I'm hoping to get the "prying" kit tomorrow. Thanks for posting the pics, I was going to try from the front but from your pictures I see I have to remove the back cover.
Cheers,
Fadi
Related
Please Help: HP Pro Slate 21 AiO Touch 2 Closing App & Returning to Desktop (Reboot?)
I've got a unique situation as I use two of these AiO devices as security camera monitors and this has worked fine for months now. I bought two of these and have them in two different rooms and I have IP Cam Viewer set up on each one to display the cameras that I want to view from that room. I also have installed IP Webcam on each one so that I may use the camera built into each one to monitor the area in front of of the monitors. This worked fine for months and I hadn't updated any firmware or anything on them because they worked fine as they were so I had no need to change anything. Within the last couple of weeks I would wake up and both of the monitors would be on the home screen with the apps both closed. I don't know if it's rebooting the entire unit or if just the apps are crashing or what but it's a real PITA since they're mounted up high and require getting a step stool out to reach them each time. Since I started having issues I upgraded the device's firmware since there was an update available thinking it might fix my issue but it did not. I thought maybe a notification was causing the issue (even none of my other Android devices close out the apps when I have a notification) so I disabled the notifications for some apps that default to have them enabled since I'm not using them but it's still happening.
I dunno what to think here.
Anyone have any suggestions to fix this?
Bumping this up & hoping to get some help. The problem still persists and I haven't been able to get any closer to a solution. I've noticed a couple of times now that I will get an error that may or may not be related. The error says:
"unfortunately, com.wolo.service has stopped"
Now, I don't know if this is the causation of the issue because there has been times that the screen going black (from basically a security monitor) has caught my eye and when it comes back on to the home screen (about a second or so) there is no error message. My guess is that this is the behavior most of the time. I just thought that it might be related or help to solve the problem.
To recap, HP Pro Slate 21 running whatever version of Android came on it and I quite literally have two apps installed and ONLY two apps installed: IP Cam Viewer & IP Webcam which I run exclusively 24/7 and nothing more. It worked fine for months where IP Webcam would allow me to access the webcam on the monitors as an extra security camera and then use the display to display 9 of the security cameras as a monitor. Then, without any notice or any changes from me (I wasn't even updating any apps or anything since I had no issues) the monitor crashes several times a day. This requires me to launch IP Webcam again to allow access to the camera and then launch IP Cam Viewer to display the security cameras as a monitor. This works fine for about 1/4 or so of the day/night but then, inevitably, it will occur again.
This is SO annoying from a device that should just work w/o any input.
Hello everyone,
the wi-fi in my Nexus 5 does not work, happened suddenly, usually does not activate and when it is activated not find available networks.
I found this thread in this forum:
http://forum.xda-developers.com/general/help/qa-wifi-stuck-mac-020000000000-g2-g3-g4-t3452133
in the second message of this discussion there is a user message explaining how to solve the problem, some users managed to solve by following this information
6.a Sellotape / Scotch tape
You need to make sure that your WiFi chip is pressed against the main board (ideally, this ensures the broken contacts touch each other, solving the problem). The best way to achieve this, is to attach a series of tape strips on the top of the WiFi chip, causing it to be pressed against the main board by the surrounding cover/hull once you reassemble/close the device. The tape strips are just a suggestion, do whatever you find convenient as long as you ensure that the chip is pushed against the board at all times.
This method may solve the WiFi problem already. When you turn your device back on, give it some time (5-10 minutes) and reboot it a few times if the problem still persists. My own WiFi didn't function right away, but after a while it finally recovered - hurray!
Click to expand...
Click to collapse
and always in the same thread has a demonstration video, however, tried on a LG G3
the video is here:
https://www.youtube.com/watch?v=OJkdva2iOag
Now, I would like to try this on my nexus .... but I ask ... where's the wi-fi chip in the Nexus 5?
any of you have tried this solution?
It seems to have solved this problem to many people
nobody ?
Hello.
I wanted to post here to help out others because I too had the same problem. Background, Ive had my g pro 2 for over 1 year (bought it refurbished). Like a few other people my phone's wifi says turning on and stays like that while draining the battery. (wifi icon keeps flashing)
I tried rebooting, changing batteries, playing with wifi settings but nothing worked. I then searched online for a solution and couldnt find any... well thats because it's NOT a software problem. Its actually a hardware problem, specifically a loose wifi chip/connection on the mainboard. I believe some lg phones are prone to the exact same problem.
tldr - Anyway the solution I found that has worked can be found on these 3 videos all with lg phones that are similar to the g pro 2. It involves placing a piece of plastic or card (I used a business card) inside the phone to apply pressure so the wifi chip has a better connection. My phones wifi has been good for almost 24 hours no problems. You can view them on youtube by searching:
1) LG G3 fixing turn wifi/bluetooth on EN SUB (or add /watch?v=1zWpzYh2DPI after youtube address)
2) How To Fix LG G4 Won't Connect to Wifi (or add /watch?v=ScLWd5lQLj0 after youtube address)
3) How to fix LG G3 WIFI / Bluetooth hardware issue (or add /watch?v=CAiu3jzKExk after youtube address)
From the videos you can see these are different phones and different users. Only common thing is that they are lg phones.
Hope it helps.
Where is the chip on mother board
(Duplicated from previous post as per suggestion by admin. See here: https://forum.xda-developers.com/general/help/voice-transmission-phone-calls-t3690651 See Addendum notes)
Hello! Long-time lurker, first time poster.
I have a sudden problem with my Android phone (Samsung Galaxy S6 running Android 7.0). Hopefully you bright gentlemen and gentle-ladies can help me:
Approximately 1 week ago (edit: 3 weeks ago), my phone stopped transmitting Voice data on phone calls. I cannot hear what the other user says on their phone, and they cannot hear me, however, pressing number keys DOES transmit the dial-tone to the other user (both ways). It does not matter if I call them or if they call me. It does not matter where I am physically, I have tried in several locations around the city (likely on several towers). It does not matter if they are using a mobile or land-line. (Addendum: Hangouts dialer functions perfectly with the hardware, before and after factory reset(s), Bluetooth headset works with Hangouts but not regular Phone)
During this time, all of my data connections work fine. Texts, Email and Browsing is unaffected. Phone performance is normal.
Since this has occurred, I have:
- Simulated battery disconnect
- Wiped Cache Partition
- Force-stopped the Phone app (all three instances)
- Verified the physical Microphone is working using the Voice Recorder app (it works fine)
- Booted the phone in Safe Mode
- Contacted my service provider to check in there was any problems with my account or transmissions.
- Transferred my Sim card to another device to test if my card/connection was ok. (Voice worked 100% on the secondary device)
- And lastly today (two weeks ago); Completed a Factory Reset
(Addendum:
- Flashed stock firmware from Sammobile via Odin
- Attempted to clean out the Microphones with toothpicks and blunt metal objects, just to be sure
- Plugged in and removed a wired headset as well as checking for debris)
I am sitting here now trying to understand how a hardware problem could possibly cause a failure of Voice encoding on only one app, and how to fix it. Or how a software problem survived the Factory Reset (and Firmware flash) into the fresh install. I did indeed try without any 3rd party apps being installed, without even adding my Google or Samsung accounts to the phone, just plain old Android; no dice.
Any suggestions?
I recall one fixing another phone that had a problem with its Capacitive Touch Screen being not sensitive enough/not reading presses problem by accessing a special menu that allowed me to re-download the driver. Is there anything like that for the Voice? (Addendum - I have looked at all the star ** codes available for this model and tried several, nothing has worked so far)
Thanks!
Thoughts today (Oct 31/17): I am not sure that flashing a custom rom is really what may fix the phone. I am willing to do so, but it is somewhat frowned upon by Canadian carriers (or at least it used to be). I was curious if it was a problem with Noise Cancellation or an SD Card problem as those are issues brought up when googling the issue. My current plan is to flash to a stock Android 6.0.1 and see if the phone works then. If so, then try the standard upgrade path. Any suggestions will be helpful!
So I've recently "upgraded" my car from a Opel Zafira 2009 to a 2015 Volkswagen Golf 7 Variant(stationwagon).
In the VW there's an infotainment system, not a NAVI but still classified as MIB 1 I've figured out.
I've done a ton of searching and it seems to still be an issue with certain cars infotainment systems, I have no issues what so ever connecting my Lenovo tablet to the car and playing Spotify through that. But since there's no phone feature it's kind of not what I'm after.
I've contemplated just getting a used *insert random other brand here* and just use that until the issue is solved, but since I've done quite a bit of reading on this I see that this has been an issue since late Android 10 versions of Oxygen OS and still persists on 11...
Has anyone here found a workaround for this? Is the issue still ongoing if I use a custom rom and most important, is there a stock camera to flash on custom roms?
Needless to say, it's annoying as heck and yes I've actually done every bit of troubleshooting there is. I even reset the infotainment, removed power from it and put it back... The whole shabang so to say...
It's a bug with OnePlus and no matter what settings I use in "developer alternatives" it still keeps randomly disconnecting, sometimes after a few seconds and sometimes it's a minute and a half.
Things I've tried:
- Removed the pairing on both devices
- Removed fuses related to infotainment on car, waited 2 min and tried again
- Unplugged the infotainment from the glove compartment, waited 2 min and connected it again
- Deleted data/cache on the bluetooth app within android
- Tested another device(Lenovo tab) that worked fine.
- Hard reboot of the infotainment(10 sec power button hold)
- Rebooted the phone(obviously)
- Reset system settings on the infotainment
- Asked a VW dealer, they had no idea and wanted me to bring in the car
- Searched numerous VW forums for any updates(has to be done by a dealership I've figured and since it's working with another unit not relevant).
- Every bluetooth setting combination related to bluetooth in developer settings.
- Probably alot more, but it's been a few days now.
Note to self, the Lenovo tab is actually running android 8, so I might have to get a Android 11 device to test with as well.
This is the only community I trust when it comes to custom roms and that kind of stuff tbh, so if anyone has experienced anything similar or found a workaround, feel free to post...
Thanks in advance for any reply. If you experience this as well feel free to says so, maybe it can all be submitted to OnePlus(not that I think they would care) or something...
I've attached a video displaying the issue as well.