Develop Bugs

WiFi is gone

I've had this tablet (SM-P600) for almost a year now & it has worked perfectly. Over the last week or so, the WiFi has been randomly turning on & off. Not just losing signal, but actually showing as off in the menus. As of this morning, wifi will not turn on at all. Just says "turning on" on the screen & sits. Never gets to the next screen showing all the open networks.
Everything is fully backed up so I went into recovery tonight. Did the full factory reset and wipe procedures. Tablet boots back like it is as supposed to, but wifi wont turn on when getting to that screen in the initial setup.
Tablet has been well cared in a case, not dropped, and not gotten wet. However I am still positive this is a hardware issue.
Any ideas for things I might try? Help!! Thx in advance

I've the same problem with my galaxy note 10.1 2014 edition SM-P605 :crying: Still haven't found solution

I am almost 100% certain this is some type of hardware problem. I tried flashing about 3 different ROM's and 3 different kernels, all of which successfully booted up. I finished by doing a 100% re-wipe (data & system included) & reinstalling a pure stock kernel and firmware. On every single revision, the words "turning on" would appear when clicking the WiFi option, but then it would get stuck. Message would eventually clear & I could continue using everything on the tablet . . . . . . . just no WiFi or Bluetooth functionality.
Final attempt was to gently remove the back cover. When lightly tapping around different points on the MoBo, the names of my local wireless networks would OCCASIONALLY appear. At one point they locked in & I really thought I had it. However, the whole thing disconnected again after a few minutes & I was back to square 1. :crying:
I never could figure out the perfect sweet spot to pinpoint the problem. My guess now is either a chip or ribbon cable that isn't seated properly, but I poked and pushed (gently!) on everything that was visible without removing any hardware other than just the back cover. Does anyone have a link to the layout of the motherboard that shows EXACTLY which piece is the WiFi/BT module? I did find an online disassembly tutorial with a random Google search, but for some reason they failed to identify this particular module.
Sorry for the long post, but I feel I am SO CLOSE to figuring this out once and for all. Just need a little more tech help to push across the goal line. Thanks!!
~Vol

Vol4Ever said:
I've had this tablet for almost a year now & it has worked perfectly. Over the last week or so, the WiFi has been randomly turning on & off. Not just losing signal, but actually showing as off in the menus. As of this morning, wifi will not turn on at all. Just says "turning on" on the screen & sits. Never gets to the next screen showing all the open networks.
Everything is fully backed up so I went into recovery tonight. Did the full factory reset and wipe procedures. Tablet boots back like it is as supposed to, but wifi wont turn on when getting to that screen in the initial setup.
Tablet has been well cared in a case, not dropped, and not gotten wet. However I am still positive this is a hardware issue.
Any ideas for things I might try? Help!! Thx in advance
Click to expand...
Click to collapse
What model is your tablet?
This was sent from my Lenovo A850 via XDA mobile app.

irfanadli97 said:
What model is your tablet?
Click to expand...
Click to collapse
Sorry about that. It's just the initial release plain jane WiFi model. SM-P600

Update:
After a little more poking and prodding on the MoBo, I'm starting to see activity. Tablet will finally connect again, but will only hold the connection for 10-15 seconds and then drop back out. A few seconds later the cycle repeats.
I really wish I could find a good hi-res photo of the motherboard to help. HAS to be a simple loose connection, or maybe a not-so-good solder point somewhere???

Vol4Ever said:
Sorry about that. It's just the initial release plain jane WiFi model. SM-P600
Click to expand...
Click to collapse
......
never heard of 'em, is it a cheapo tablet? In my country there's a store of them (Allwinner 6.6" tablet with microSD slot, 2gb internal w/o bluetooth WIFI ONLY INTENDED FOR CASUAL GAMING, or should I call it kids only tablet, RM130 ($35))
That thing has a cheap plasticy housing, unneat design but has a pretty good performance (it plays dead trigger pretty well)
This was sent from my Lenovo A850 via XDA mobile app.

irfanadli97 said:
......
never heard of 'em, is it a cheapo tablet?
Click to expand...
Click to collapse
SM-P600 is Samsung's actual model number for the WiFi only version of the 2014 Galaxy Note 10.1. Most definitely NOT a cheapo tablet!! Although this wifi issue makes me wonder. I had the functionality back for about a day or so, and then it disappeared again. This has to be a simple case of a loose connector, but I sure can't find it. Ugh. Utterly frustrating.

oo...my bad
maybe software issue
This was sent from my Lenovo A850 via XDA mobile app.

What firmware version are you using because I am having the same issue. I manually updated to the september update (P600UEUCNI1) for the wifi version and started experiencing the same issue.

Same here. I think it's an issue with NII firmware.

*****PARTIAL solution*****
I have proven 100% that mine is problematic hardware . . . . . NOT software or kernel. For the time being my WiFi is back up & seemingly stable. I had to remove the back from the tablet for the fix. You have to be *extremely* careful, but it just snaps off with no screws. Lots of YouTube videos if you choose to attempt, but please don't say I didn't give you fair warning!
The reason I say partial solution is that I haven't pinpointed the exact location of the short. I am 99% sure it is somewhere on the extreme upper left hand corner as you face the front of the tablet. There are a couple of ribbon connectors in that area, and a few snap on type connectors that look like little motherboard chips. After gently poking & prodding the ribbons and disconnecting & reconnecting the snap connectors (being CAREFUL; I cannot stress this enough), my WiFi reappeared.
My final tip is to keep the screen on the page that shows the list of available networks. If you are having the same problem I was, this screen will just show "turning on" and nothing else for the WiFi. While poking around, I would occasionally see the list of networks pop up & then go back off. I finally hit whatever the magic spot is, and the networks held. Snapped the back cover on again, and I've been online for probably 4-5 days now without a single hiccup.
And before I get flamed, I know how dangerous it is to poke around with a powered, exposed tablet. There are probably certain points that could make connection and FRY the entire thing in an instant. I was just willing to take the risk as my tablet was useless without network capability. I had nothing to lose. I would recommend at least trying to poke & prod with the tablet OFF a few times to be safe, but I personally got tired of rebooting over & over & over & over. My luck sucks. With the tablet ON, I was at least able to monitor when something was happening.
Good luck if you attempt it!!
~Vol

Vol4Ever said:
I've had this tablet (SM-P600) for almost a year now & it has worked perfectly. Over the last week or so, the WiFi has been randomly turning on & off. Not just losing signal, but actually showing as off in the menus. As of this morning, wifi will not turn on at all. Just says "turning on" on the screen & sits. Never gets to the next screen showing all the open networks.
Everything is fully backed up so I went into recovery tonight. Did the full factory reset and wipe procedures. Tablet boots back like it is as supposed to, but wifi wont turn on when getting to that screen in the initial setup.
Tablet has been well cared in a case, not dropped, and not gotten wet. However I am still positive this is a hardware issue.
Any ideas for things I might try? Help!! Thx in advance
Click to expand...
Click to collapse
I bought my Note in March of this year, I started having the WiFi issue after the April firmware update. At first I would get the Connected to... message at random times, even though I had full signal strength. At the end of September, I started losing connection at random times and in the middle of October, I had to send it in to Best Buy's Geek Squad service to have them repair it. It is a hardware issue, as the no matter what firmware version I use, it will never connect to the router. I know it, Geek Squad is aware of it, as I have sent it in for repair twice so far. I would have to send it in a third time before they will think about replacing it with a new Note. I will admit, that before I updated it in May, I did root it, because I tried to remove the Business Week+ and New York Times apps, as I never used either one of them. I tried disabling them, only to have them reactivate and update themselves.

Damn, what I read here is not good news. My SM-P605's died yesterday.
With Tapatalk on my Galaxy Note 10.1 (2014)

Hardware issue for sure. Same problem with mine. Opened the back case, disconnected the upper right (as your looking at the screen) small ribbon, reconnected, and boom, perfect wifi once again!

The EZ Package Disabler app is fine for debloating rooted and non-rooted devices with Touchwiz roms. It uses Knox, so that mustn't be removed. The apps are still on the system partition, but are completely dead now. While other apps, especually for non-rooted devices kill the system apps during boit and try to prevent their restart. But during boot the whole stuff is active until the app kicks in, allowing the system apps to receive updates, communicate, spam free flash mem etc.
The app wirks the same way on my rooted P605 and unrooted S5. And gives a reason to buy Samsung stuff, unlike Touchwiz and its bloatware. As far as custom roms go, i found that of my old LG L9 much better. Even if the early roms were AOSP 4.0.4 based, then 4.1.3, they had already had the fresh & bright look & feel of the future Kitkat, and a few useful enhancements like an integrated backup tool, which was more simple, but for me as useful as TB.
As for the main problem here, i think using a case with a hardened backside, and not one if these with a big hole(though being better than nothing), prevents oroblens like battery, display and seemingly wifi connectors loosening. Or bad solder joints. The backplate of the note gives thru any pressure on the back, especially in the middle area. It then rests on the battery, metal shields, connectors and stuff. This seems to generate enough wear over time for problems. The same back plate on a much smaller device(my S5, but that has a subchassis covering the innards, too) would be much stiffer, and my 7" tablet has an aluminium unibody case, such trouble is unknown there.

Hi Gents..
same problem here... I used to own a SM-600 purchased in 2014 unfortunately I lost it... (the first tablet worked without any proble until I lost it...) than I managed to found the same modell brand new on amazon... it worked for 2 weeks and 2 days ago wifi died... but funny enough not straight away.... first couple time just switched off the wifi... I managed to switch simply back... next day it only worked if restarted the device... now factory reset nothing... If it is hardware related why worked 2 weeks witout any problem? If it is software related why not working after software reset? Only installed a few apps from the store.. the device did not overheated or physically damaged...

I have the exact same problem.
Since I bought this a long time ago, I have to pay for the repair. I just want to know if it is worth it. How much did it cost you (if you bothered)?

In my opinion it would be foolish to spend a dime to repair a 4 year old tablet. If the battery is original, it may well be near the end of its useful life as well. FWIW, I bought this tablet used about 8 months ago and have not experienced this wifi problem.

It's still so well equipped, that you can't simply replace with a modern entry level or midline tablet, but with a top of the line one, so a repair is well an option.
I just don't have a clue about the SoCs performance level. To which current ones it would equal and where things get better. I can only compare it to my similarly(Snapdragon 801) equipped phone and my cheap 7" tablet's quad core Mediatek SoC, and that is considerably worse, though being three years newer.

LG G4 camera broke, had to replace. Anyone else?

Verizon VS-986 here.
A couple of days ago, I went into the Camera app to take a picture and it was "stuck" on the selfie camera, and the icon to switch to the main camera was gone. I went back to the home screen and back into Camera, and fiddled with the Modes, and it finally came back. I clicked on it, and the app showed an image for a couple seconds, then froze up. I did a lot of back and forth with it, and sometimes it would show an image for a second and freeze; sometimes it went totally black and froze the app; eventually, after power cycling a few times, it was stuck on the front-facing camera for good, with no icon to swap to the back camera. Basically, at this point, the app had recognized that there WAS NO back camera and didn't even bother presenting the option anymore.
This had all the hallmarks of a hardware problem. Glitchy, intermittent outages, then the hardware simply not recognized anymore. Still, I cleared out caches and searched online and found this article: How to Fix Camera Failed Problem on LG G4 (recomhub.com/blog/how-to-fix-camera-failed-problem-on-lg-g4/), none of which did anything to help. (I'm not rooted/unlocked so I couldn't clear the cache partition like they recommended, though it clearly wouldn't have helped anyway.)
Couple other things that may or may not be relevant: it was VERY hot out (80+ degrees) when then problem started and the phone was hot as a result of it. But it kept happening after cool down.
A crazy other thing that happened was, that evening, after rebooting one last time just to be sure, half the screen turned into rainbow noise during the Verizon logo and stayed that way for several seconds, even into the lock screen. That pushed me over the edge.
I went to a Verizon store and they kindly swapped it out for me. But that was weird and I wanted to put it on the record. Also curious whether anyone else had this problem.

Not that problem, but check out this other thread I started regarding the camera causing the phone to overheat: http://forum.xda-developers.com/showthread.php?t=3142806
Sent from my LG-H811 using Tapatalk

I've had the rainbow noise on the right half of the screen show up on boot at the Verizon screen as well. It stayed that way until the lock screen and that's when I powered the phone off, pulled the battery and let the sit for a few minutes. Haven't had the problem in the weeks since I've had the phone though.

The exact thing happened to me. My rear camera will not work at all. And the flashlight also will not work. Tried rebooting, factory resetting it, clearing cache, and took out my battery and still nothing.

I had a Verizon G4 that the rear camera stopped working on. I believe it was caused by a drop. I posted on here about it. For mine it just wouldn't focus anymore. Replacement was very easy, you only need a small Philips head screwdriver, and your fingernail, or plastic tool to remove the connector and pry the camera out which is held in by adhesive.
Replacement OEM part out of a Sprint G4 was under $14 USD on eBay.

lopezj said:
The exact thing happened to me. My rear camera will not work at all. And the flashlight also will not work. Tried rebooting, factory resetting it, clearing cache, and took out my battery and still nothing.
Click to expand...
Click to collapse
Hello,
I have the exact same issue. Do you have a solution ? I dont want to rma anymore, screen coating than bootloop than this, this phone is a true disaster.

Only other thing any one could try is a tot lgup restore if that dont work either more than likely its a hardware failure. I had issues on my g2 with a could not connect to camera from the factory. Found out my stock rom was corrupted from lg toted and worked like new. Did it again a few moths later. Toted avain worked like new. I asume something in the camera files corrupted. Just throwin in my 2 cents.

Hello, thanks for the answer.
I fixed the issue by myself few minutes ago, i simply disconnected than reconnected the rear camera plug to the motherboard.

Zenouzenou said:
Hello, thanks for the answer.
I fixed the issue by myself few minutes ago, i simply disconnected than reconnected the rear camera plug to the motherboard.
Click to expand...
Click to collapse
Did u by chance notice any corrosion or oxidation on the contact surfaces?

Nope, nothing special on these.

Well i spoke to fast, my camera is dead again.

rick09 said:
I had a Verizon G4 that the rear camera stopped working on. I believe it was caused by a drop. I posted on here about it. For mine it just wouldn't focus anymore. Replacement was very easy, you only need a small Philips head screwdriver, and your fingernail, or plastic tool to remove the connector and pry the camera out which is held in by adhesive.
Replacement OEM part out of a Sprint G4 was under $14 USD on eBay.
Click to expand...
Click to collapse
Hi, how did that 14 dollar camera work out for you? I'm getting wildly varied prices for replacement rear camera on eaby. Do you have a link to the one you bought and did it work as well as the original? Thanks.

http://m.ebay.com/itm/351575783287
Im gonna try this one

Zenouzenou said:
http://m.ebay.com/itm/351575783287
Im gonna try this one
Click to expand...
Click to collapse
I'd go for that one too but unfort it's 33 dollars to post west europe lol
I'm gonna go for this one but god knows what it's like at this cheap price but I'll take the chance.
http://www.ebay.ie/itm/151946458176?_trksid=p2057872.m2749.l2649&ssPageName=STRK:MEBIDX:IT

Jesus i didnt see that. Sorry

So my brand new original camera module arrived today, i replaced it myself and...the camera still doesn't work. Looks like it's an MB problem. I have to send this god damn phone to LG again..

Hello, here is an update about my camera. LG repair the phone by changing the motherboard and the camera module.

Camera Issues.

Hi all.
I bought a HTC One M8 after killing my Xperia Z. My dad also has an M8, and its been perfect for him since day one. I've been thoroughly impressed with the device, despite its age, and will find it hard to part with when I eventually purchase an ARA when released! This will be a lengthy post, so bare with me please.
The issues started at the beginning of the week. I hadn't done anything different, but I noticed that my camera wasn't working full stop. I'd click on the app and it would force close. So i did some research and found a couple of solutions, most of which involved Last Pass, which isn't installed on my device, however I tried those that didn't involve it, to no avail. Somewhere along the way, I must've done something wrong as I started to get the "gaaps.com has stopped" error, and the error message would reappear every few seconds, rendering the phone unusable. After a factory reset, the "gapps.com" error had stopped, but my camera issue still persisted.
It's worth noting that the night before, I did drop a dumbbell on the screen by accident, but the camera WAS working perfectly fine afterwards. The problems I described above occurred the day after.
So after getting nowhere, I decided to take the plunge and replace the camera unit. I purchased an OEM part, and then when it was delivered I continued to strip the phone down and replace the old module with the new one. That was last night. I started the phone up, and clicked on the camera. Hey Presto! The front facing camera worked. No option for the rear camera though. So i installed a 3rd party app, and in that app, the rear facing camera is upside down. I placed my finger over the bottom camera of the two rear ones (the camera i replaced) and the image wasn't blocked by my finger. I placed my finger over the top rear camera, and the image was blocked.
So my question now is, having replaced the entire lower module with a new part, what could be causing the image to be upside down on the third party app, and not showing a rear camera function at all in the stock app?
I'm 99% sure that I rebuilt the phone correctly, but I am going to strip it down again tonight and then rebuild it to make sure I hadn't missed anything out.
Any and All suggestions and questions are welcome.
Thanks,
Mylo.

Update
So, just to update.
I purchased a faulty HTC M8 off eBay for a rather good price. It's arrived, and ive just spent the last 45 minutes stripping the camera sisterboard out of the purchased one and fit it into my handset. All works perfectly. So one can only assume that my sister board was broken in some way or another.
Regards,
Myles.

Second Pixel C with same issue - backlight stops working.

I am on my second Pixel C where the backlight has stopped working after a month. The screen still works, if I shine a light at it just right I can see the contents (especially when they are white), but the backlight just doesn't come on. The previous one did this on and off for about a week while waiting for the replacement, meaning it would occasionally come back on and work for a little while. But, right before the replacement arrived, it went off and never came back on. My replacement did it for the first time today (it is one month old now), I connected to my laptop when I got home and issued an "adb reboot", and it appears to be working again. I have requested a refund from Google, but they said they couldn't authorize it, so I have filed a dispute with my credit card company in order to get my money back.
Overall, I like the device. I have had to work around a few of its shortcomings, but everything was satisfactory. I just can't keep replacing something every month.
Has anyone else experienced this? I mean, I know how to search and have found similar reports, this exact issue. Where the screen still comes on and is visible under the right lighting conditions, but the backlight is just non-functional. If so, what was the recourse you took to solve it? I have tried not putting it in my case (thinking that was the problem), rebooting (which occasionally has worked, but not always), factory resets (real tough without being able to see), plugging it in when malfunctioning, leaving adaptive brightness disabled, cursing at it and throwing my hands up in the air in frustration, etc. Nothing reliably works, and now I am afraid to let it go to sleep seeing how it came back after the reboot today.
Thanks for reading this...

My Pixel C started doing this last week. Wasn't so bad at first, but it's slowly gotten worse and starting last night the backlight will go hours without turning on. I've tried charging it, hooking it up to my computer, and just finished a factory reset and nothing has worked. Just like you if I shine a light at the right angle I can see things, but that's not exactly fun to do. Bought it at the end of March, so it almost made it 4 months.
One thing I should add, and this is probably a coincidence, is it started happening right after I downloaded the July updates. I only mention this in case someone else has had a similar experience.

My second one had gotten even worse, the screen sometimes comes on now, but the right half is either just fuzz or completely distorted, and the touch screen is non functioning.
I have ordered a Samsung galaxy tab s2, and will get my money back either from Google (doubtful), or my credit card company. Hope Samsung updates it at least to N.
I'm so torn, when it worked the pixel was awesome, I love the screen, closest any has come to the ratio of my camera. But two in a row only lasting a month each, and it's hard to consider a third, or fourth...
Sorry yours is glitching out on you, hope you get a satisfactory resolution.

I have the same problem. Exactly like you describe above. Since my Pixel C is one month out of warranty there is nothing I can do except warn others not to buy this product,
Oliver Browne.

Same here for me. First one started with screen issues as described above, lucky for me i was 3 days before the end of waranty, second one lasted 93 days... 3 days out of waranty for a replacement device! Thanks Google for a cheap device...
Envoyé de mon iPad en utilisant Tapatalk

I face the same issue, and was able to turn on the backlight by adjusting its brightness using the touch screen. Try shining a torch onto it while locating the brightness setting. This temporary fix works for me every time, and hope it helps someone.

Trying the torch was very useful! I now know for a 100% that the backlight doesn't work. I used the torch to see what I was actually doing on the screen, and erased all data & cleaned the cache.
Unfortunately the backlight stayed off, so I assume it's a hardware issue.
I've sent an email to Google support, hopefully they can get this one fixed or replaced.

did you manage to fix your issue ?

Same issue here, and no not resolved.
The only thing I can do to work around it is keep tapping the power button every second. Eventually you get lucky and the backlight will turn on. (Rebooting doesn't seem to be needed.)

Hi all,
I bought this tablet as a gift for my little brother. He encountered the very same issue 2 or 3 weeks ago, and it became worse today, as now backlight won't turn on anymore, even after a reboot and a factory reset.
It must be a hardware issue...
I will try to contact their after sales service, as the tablet isn't even 6 months old.

HI, my first Pixel c met this issues after 20 months... first it was only sometimes and backlight came back after some pushes on the power button... but it get worst and worst: 2 days without backlight and at the end half screen fuzzy issues. I order a replacement product with my warranty (2 years in Europe)... and now my second Pixel meets the same issue... with a no responding screen issue too... it's awful and my warranty is over yet... nothing can fix this...! something seems to be bad quality in this device....

I'm on my 2nd pixel c and final. Google support said that because they had replaced it under warranty the warranty only applies to the original purchase date not the replacement which seemed BS to me because I was shipped a refurb tablet
Never the less using adb/ fast boot I was able to get the device into bootloader and blindly reload the entire operating system. It was only until I performed a wipe within TWRP that the screen started working again. Interesting and now off it is working for the past hour or so. Currently applying latest updates but not holding my breath. Unfortunately it looks like Google is killing off the tablets and I don't know if any of their Engineers have actually tried to use a Chromebook in place of a tablet but it just doesn't translate well. If I cannot get this device working reliably I may buy another refurb to get a few more years out of it. The pixelbook is way too heavy for Couchsurfing

The screen comes and goes with no particular interaction. I'm really bummed because I had gotten so used to this device. I buy another but I'm afraid it's going to happen again. I don't see any tablets that are upgrades either. The Android tablet days are over. Pixelbook is not intuitive. Although it runs Android apps it does so very poorly with in Chrome OS and it's very bulky. I'm a try my luck with another refurb off eBay. Have not been able to find anyone that can repair it

[COS13]Proximity sensor not working

i have a oneplus 8 pro that was running on OOS 11 like magic
then update it to COS 12 and the proximity sensor stopped working
yesterday COS 13 came and i thought it would fix the problem but no, the problem still there.
any fix for the proximity sensor one COS 13 please.

Mine is also not working at all since oos12. Im completely stock on oos13 now.
Sensor doesnt react at all.

Hi,
mine too stopped working a few days ago.
Im on OOS13 (eu) but it worked the hole time, suddently it stopped working, without any changes to the system.
I did a proximity sensor test (dialpad : #*899# ) and it does not react at all.
PS : Can anyone tell me where the sensor is located on the phone i cant find it.

riding the same boat

I tried to reset it with "Proximity Sensor Reset" app, but it didnt work so I think its a hardware problem...
Fortunately the hardware piece costs about 5-10 bucks, unfortunately phones today are so glued that I dont wanna hassle to open it just because of the little sensor..
Edit: I found out where the sensor is located somewhere in the right corner,
yesterday I coincidentally noticed that it sometime works when the top right corner comes in contact with my pants or any other fabric.
When I try it with my hands or head it doesn't react at all...

Deavy said:
I tried to reset it with "Proximity Sensor Reset" app, but it didnt work so I think its a hardware problem...
Fortunately the hardware piece costs about 5-10 bucks, unfortunately phones today are so glued that I dont wanna hassle to open it just because of the little sensor..
Edit: I found out where the sensor is located somewhere in the right corner,
yesterday I coincidentally noticed that it sometime works when the top right corner comes in contact with my pants or any other fabric.
When I try it with my hands or head it doesn't react at all...
Click to expand...
Click to collapse
I was going to tell you that, I accidently discovered that proximity sensor is kind of working when in contact with my hoodie that is covering my ears.
but when phone is directly touching the skin it wont work.

Same here. I bought a used one in very good condition and figured out that the phone does not switch off the screen during calls. I can run the diagnostics and see that the sensor works properly when I use some fabric on it but has absolutely no effect when using the hand or the ear.
I wonder how that can be and if it's really an issue with the OS version or a hardware issue.

Also same here. Proximity sensor problems after oos13 update. Has anyone tried custom roms if problem are still occuring on those too?

i found the solution on yt

AidenDRJr said:
i found the solution on yt
Click to expand...
Click to collapse
You are the best thanks a lot
Works 100% fine after new calibration.