Related
Hi - I just got my Sensation a few days ago and I love it. But I have now found an annoying bug (?). When I take a picture and it involves the flash going off, 8 times out of ten the phone will just go dead immediately - screen off, no response. Sometimes a battery pull required to get it to reboot. Anyone experienced this?
Seems to happen indoors when the subject is fairly close, darker conditions.
Not sure if this is a hardware or software problem - I really don't want to return it
Try turning off geotagging.
Thanks, I tried that, then turning off gps, then turning off location, same problem every time.
I find that turning off mobile data, and even leaving all of the above on, stops the problem. Or, leaving data on but turning off the flash. Data + flash = crash...!
Still not sure if this is software related? I guess so?
dazz29 said:
Thanks, I tried that, then turning off gps, then turning off location, same problem every time.
I find that turning off mobile data, and even leaving all of the above on, stops the problem. Or, leaving data on but turning off the flash. Data + flash = crash...!
Still not sure if this is software related? I guess so?
Click to expand...
Click to collapse
Hmm. Since it's correlated with the flash, and few if any others have complained about this I'd guess HW, but who knows. I'd probably do a factory reset, and if that didn't fix it get a replacement.
Has anyone found a solution to this problem? Same thing happens to my phone.
This was posted when the phone first came out. Probably in the early threads. That was one of the first things I checked when I got my Sensation. I don't know if there was a solution other than swapping - but do a search in the forum because it was covered. Hope there was a solution for you.
Same thing happens here, Revo HD.
MEETOO
At first I just waited and it would restart THEN...
Had to pull battery and it would restart THEN...
When it restarted only a speckled screen followed by home screen THEN...
Only speckled screen THEN...
Nothing but the vibration when trying to restart THEN...
A replacement is being shipped after a trip to the T-Mobile store.
Initially I called T-Mobile and they told me the UPDATE would solve my problem but as the day progressed it was all down hill.
During the course of the sales person ordering me a new phone they automatically added a protection plan without my knowledge.
YIPPEE HUH?
So I've tried factory wiping and installing a few different roms and no matter which one I go to I keep getting these random reboots. This is particularly troubling when I restore an older rom that I know I was not having this particular issue on.
It is making my phone pretty close to unusable since it will often go into an "Optimizing apps!" speil draining battery and taking an obnoxiously long time to reboot. Not sure what is up. Any suggestions?
Snow_fox said:
So I've tried factory wiping and installing a few different roms and no matter which one I go to I keep getting these random reboots. This is particularly troubling when I restore an older rom that I know I was not having this particular issue on.
It is making my phone pretty close to unusable since it will often go into an "Optimizing apps!" speil draining battery and taking an obnoxiously long time to reboot. Not sure what is up. Any suggestions?
Click to expand...
Click to collapse
Try with a clean flash (or the factory images) without user data/modifications and see if your RRs are still there.
Is the power button stuck by any chance?
Primokorn said:
Try with a clean flash (or the factory images) without user data/modifications and see if your RRs are still there.
Click to expand...
Click to collapse
I've factory reset a few times and wiped everything except internal storage pretty much. Even tried wiping user data just to see if it would help
dicecuber said:
Is the power button stuck by any chance?
Click to expand...
Click to collapse
I don't think it's getting stuck it still seems to go in and out properly. I even took it out the case just to make sure there wasn't something I couldnt' seee putting pressure on it
Snow_fox said:
I've factory reset a few times and wiped everything except internal storage pretty much. Even tried wiping user data just to see if it would help
I don't think it's getting stuck it still seems to go in and out properly. I even took it out the case just to make sure there wasn't something I couldnt' seee putting pressure on it
Click to expand...
Click to collapse
The button will NOT seem to be stuck, even if it is, as the contact is made internally. My bro´s Nexus had this problem, and by the end it kept rebooting constantly because the button was making contact on its own. I fixed it by tapping vigorously at the area between the power button and the camera and that made it work.
A way to know if it is stuck could be to press the volume down key as soon as it restarts, if it goes into recovery, then there is no doubt the power button is stuck.
Don´t dismiss hardware problems, as many Nexus are affected by the power button issue and you already tried software solutions which didn´t work.
Hope you sort it out. Remember to use an app to avoid pressing the button so much, such as when waking the device. I recommend Gravity Screen, but there are many other options.
simonarturo said:
The button will NOT seem to be stuck, even if it is, as the contact is made internally. My bro´s Nexus had this problem, and by the end it kept rebooting constantly because the button was making contact on its own. I fixed it by tapping vigorously at the area between the power button and the camera and that made it work.
A way to know if it is stuck could be to press the volume down key as soon as it restarts, if it goes into recovery, then there is no doubt the power button is stuck.
Don´t dismiss hardware problems, as many Nexus are affected by the power button issue and you already tried software solutions which didn´t work.
Hope you sort it out. Remember to use an app to avoid pressing the button so much, such as when waking the device. I recommend Gravity Screen, but there are many other options.
Click to expand...
Click to collapse
Holding down volume after one reset actually put me into recovery. Plus it's restarting at times in recovery now :/
I doubt it's under warranty since I got it in feb 2014 x.x
Snow_fox said:
Holding down volume after one reset actually put me into recovery. Plus it's restarting at times in recovery now :/
I doubt it's under warranty since I got it in feb 2014 x.x
Click to expand...
Click to collapse
If you got it directly from Google, I'd try calling them up and asking for a replacement even if you are a few months off the warranty period, I have read some stories of them honoring warranties in order to get rid of stock. That'd be true even now that the new Nexus is supposedly releasing this year. Nothing wrong with trying, you might get a new, shiny phone.
That being said, don't worry, it's perfectly fixable. The part that gets stuck is not the button itself, but the part that goes into the motherboard, so don't bother fiddling with the black button. I managed to fix my brother's button by doing the following:
- Clean the area between the button and phone of debris or any dirt that could be causing it to be stuck. This is just to be on the safe side, as it is unlikely that it is the cause of the malfunction.
- Take the case off the phone if you haven't, and then put it upside down and tap vigorously with your fingers in the area between the camera and the power button. It might not work the first few times, but it eventually will release the part that is stuck.
- As soon as you can get it to turn on without rebooting itself, install Gravity Screen, or any other app that replaces the power button to wake up or turn the screen off. You are looking to use the button as few times as possible.
After doing that, his Nexus went for being unusable due to constant reboots to working fine. It's been almost 6 months since it happened so it is bound to work, just don't lose heart and patiently work at it. Tap a bit harder if it's not working. Let us know whether you managed to fix it.
simonarturo said:
The button will NOT seem to be stuck, even if it is, as the contact is made internally. My bro´s Nexus had this problem, and by the end it kept rebooting constantly because the button was making contact on its own. I fixed it by tapping vigorously at the area between the power button and the camera and that made it work.
A way to know if it is stuck could be to press the volume down key as soon as it restarts, if it goes into recovery, then there is no doubt the power button is stuck.
Don´t dismiss hardware problems, as many Nexus are affected by the power button issue and you already tried software solutions which didn´t work.
Hope you sort it out. Remember to use an app to avoid pressing the button so much, such as when waking the device. I recommend Gravity Screen, but there are many other options.
Click to expand...
Click to collapse
simonarturo said:
If you got it directly from Google, I'd try calling them up and asking for a replacement even if you are a few months off the warranty period, I have read some stories of them honoring warranties in order to get rid of stock. That'd be true even now that the new Nexus is supposedly releasing this year. Nothing wrong with trying, you might get a new, shiny phone.
That being said, don't worry, it's perfectly fixable. The part that gets stuck is not the button itself, but the part that goes into the motherboard, so don't bother fiddling with the black button. I managed to fix my brother's button by doing the following:
- Clean the area between the button and phone of debris or any dirt that could be causing it to be stuck. This is just to be on the safe side, as it is unlikely that it is the cause of the malfunction.
- Take the case off the phone if you haven't, and then put it upside down and tap vigorously with your fingers in the area between the camera and the power button. It might not work the first few times, but it eventually will release the part that is stuck.
- As soon as you can get it to turn on without rebooting itself, install Gravity Screen, or any other app that replaces the power button to wake up or turn the screen off. You are looking to use the button as few times as possible.
After doing that, his Nexus went for being unusable due to constant reboots to working fine. It's been almost 6 months since it happened so it is bound to work, just don't lose heart and patiently work at it. Tap a bit harder if it's not working. Let us know whether you managed to fix it.
Click to expand...
Click to collapse
I'm going to get in contact with google. I tried pushing down on the area between the camera and it didn't help much. It has started working again properly after a really peculiar work around. I just don't want to have to be super cautious of a button for the rest of the time i own my device :/
Snow_fox said:
I'm going to get in contact with google. I tried pushing down on the area between the camera and it didn't help much. It has started working again properly after a really peculiar work around. I just don't want to have to be super cautious of a button for the rest of the time i own my device :/
Click to expand...
Click to collapse
Please detail the peculiar work around you mention...
Sent from my XT1095 using Tapatalk 2
mazubo said:
Please detail the peculiar work around you mention...
Sent from my XT1095 using Tapatalk 2
Click to expand...
Click to collapse
Well someone mentioned maybe trying to clean it out somehow. I tried canned air and that didn't do anything so I formed a seal over the button using my mouth and then proceeded to exhale. It has yet to give me any trouble since then.
Had exactly the same issue, reboots over and over again, couldn't boot to bootloader without reboot...
What helped for me was something I read somewhere else, don't remember where, was knocking on the back cover between camera lense and the power switch, did it 4 days ago and it works since than..
Snow_fox said:
I formed a seal over the button using my mouth and then proceeded to exhale.
Click to expand...
Click to collapse
Sounds sexual
You can take the back cover off, and if you are careful there is no sticker or seal that would tell google you have opened the device. It is difficult to pull all the way off, the vibration motor is attached to the case back and comes off with it so it would seem stuck. You just have to keep pulling.
aaargh777 said:
Had exactly the same issue, reboots over and over again, couldn't boot to bootloader without reboot...
What helped for me was something I read somewhere else, don't remember where, was knocking on the back cover between camera lense and the power switch, did it 4 days ago and it works since than..
Click to expand...
Click to collapse
Pressing on the area between the camera and the on switch seems to help a lot of people it didn't seems ot have much of an effect for me. While my phone hasn't given me issues since shortly after I posted this thread I'm kinda worried I'm one drop away from the issue coming back
dicecuber said:
Sounds sexual
Click to expand...
Click to collapse
No way to avoid it sounding that way I fear.
fwayfarer said:
You can take the back cover off, and if you are careful there is no sticker or seal that would tell google you have opened the device. It is difficult to pull all the way off, the vibration motor is attached to the case back and comes off with it so it would seem stuck. You just have to keep pulling.
Click to expand...
Click to collapse
Would this allow me to repair it?
Yeah but you'd need to unscrew a plastic cover that is inside the phone. Phillips head screws, jewelers screwdriver size. Depends on if its dirt or a broken switch though.
fwayfarer said:
Yeah but you'd need to unscrew a plastic cover that is inside the phone. Phillips head screws, jewelers screwdriver size. Depends on if its dirt or a broken switch though.
Click to expand...
Click to collapse
Sorry to disappoint everyone but this is a widespread problem that google is aware of fro some time now. It's not the power button but it's burried deep in the software and appreas to have popped up right after the Lollipop 5.1 up date. Check out all the posts on Google
https://productforums.google.com/forum/#!topic/nexus/IJSOuc7gw0w[376-400]
While it apprears to be confined to the Nexus 5 I have had it happen with my nexus 4 just running stock L 5.1
I hope that casts some light on it
Weirdly enough, my power button works flawlessly on 5 and 5.1. Red 32gb from the google play store. I've opened the case multiple times and put Arctic silver knockoff heat compound in sloppily and without regard, no issues other than sprint screwing up their spark LTE rollout.
Blacksmith5 said:
Sorry to disappoint everyone but this is a widespread problem that google is aware of fro some time now. It's not the power button but it's burried deep in the software and appreas to have popped up right after the Lollipop 5.1 up date. Check out all the posts on Google
https://productforums.google.com/forum/#!topic/nexus/IJSOuc7gw0w[376-400]
While it apprears to be confined to the Nexus 5 I have had it happen with my nexus 4 just running stock L 5.1
I hope that casts some light on it
Click to expand...
Click to collapse
Sorry, I disagree. While some instances might be related to software, it has been proven that there is in fact a problem with the physical button getting stuck on Nexus 5 phones. You can check it online and will find lots of hits and even YouTube videos, most of them around the time before lollipop.
Best way to check whether it is software or hardware is to press the volume down key when your phone reboots by itself. If it takes you to the recovery, you can bet your cat that it is not lollipop's fault
So I'm suspecting that I have the wonky power button too but.....
I haven't been able to get it to go to recovery when pressing power down and I've defintely had a few restarts very recently.
More importantly, and something that I haven't seen anyone else post about; more often than not my N5 just shuts down. It's usually when I've doing something with the phone (today was flicking through my GPM library). I'll power it back on and it will boot cleanly and then (more often than not) power down again. Other times it will bootloop, but that's rare. It seems to me that if I let it boot up and then don't touch it for a while, it will stay up but I'm not sure that's consistent.
Anyone else seen or heard of the power button causing a powerdown instead of bootloop?
techinv said:
So I'm suspecting that I have the wonky power button too but.....
I haven't been able to get it to go to recovery when pressing power down and I've defintely had a few restarts very recently.
More importantly, and something that I haven't seen anyone else post about; more often than not my N5 just shuts down. It's usually when I've doing something with the phone (today was flicking through my GPM library). I'll power it back on and it will boot cleanly and then (more often than not) power down again. Other times it will bootloop, but that's rare. It seems to me that if I let it boot up and then don't touch it for a while, it will stay up but I'm not sure that's consistent.
Anyone else seen or heard of the power button causing a powerdown instead of bootloop?
Click to expand...
Click to collapse
You will need to troubleshoot this the old-fashioned way. Have you installed any updates, apps, mods or anything recently?
Best case scenario would be that you flash a stock image without restoring apps, kernel or any mods. Run the phone for some time, couple of days or so, and be on the lookout for power downs or reboots. After that, you can try adding a few apps at a time and keep checking. If the phone reboots even with a clean factory image, then I'd have to say the hardware is faulty. Could be the power button, could be something else.
Try it out and let us know
HI all!
I have an OnePlus One. A month ago it became unusably slow, where all animations took the phone 5-10 seconds to go through. Sounds and haptic feedback are immediate (pressing a button/typing), but the screen seems to lag behind.
One interesting example comes when rebooting the phone. The Android marshmallow bootlogo (CM13) takes at least 20 seconds to finish, but I can actually swipe up on the screen while the marshmallow logo is still on there and hear the screen unlock sound.
I have tried many different ROMs (SlimSaber, OxygenOS, CM13/12), deleting data, cache, dalvik and doing many, many factory resets. Nothing seems to help at all.
Anything that can be done to fix this little bugger? Setting the three animation settings to 0x seemed to help a little bit, but not all that much. Is there a completely animationless rom out there?
IrrationalBanana said:
HI all!
I have an OnePlus One. A month ago it became unusably slow, where all animations took the phone 5-10 seconds to go through. Sounds and haptic feedback are immediate (pressing a button/typing), but the screen seems to lag behind.
One interesting example comes when rebooting the phone. The Android marshmallow bootlogo (CM13) takes at least 20 seconds to finish, but I can actually swipe up on the screen while the marshmallow logo is still on there and hear the screen unlock sound.
I have tried many different ROMs (SlimSaber, OxygenOS, CM13/12), deleting data, cache, dalvik and doing many, many factory resets. Nothing seems to help at all.
Anything that can be done to fix this little bugger? Setting the three animation settings to 0x seemed to help a little bit, but not all that much. Is there a completely animationless rom out there?
Click to expand...
Click to collapse
Did you already tried to format your whole phone so also SD card / system/cache/ etc just make it completely clean and connect your phone to your PC while in recovery paste darkobas rom (or other rom ofcourse) on your sd-card and gapps flash it and start really clean.
Just my 2 cents
check ur phone hardware for damage as u had changed everything multiple time and still no profit which means problem is not on surface maybe its deep and i am irrational that any change of rom would help , that said maybe try to flash good firmware through fast boot ,take help from cc or more persons . i may be wrong but i had concluded this - it seems that the connection between gpu or cpu with os is kinda broken which doesn't make sense as u had changed it multiple times but still feels like it.
moneyvirus said:
Did you already tried to format your whole phone so also SD card / system/cache/ etc just make it completely clean and connect your phone to your PC while in recovery paste darkobas rom (or other rom ofcourse) on your sd-card and gapps flash it and start really clean.
Just my 2 cents
Click to expand...
Click to collapse
I have formatted everything and I believe I have removed everything useless from the memory. I have also flashed multiple roms and the issue is still there
IrrationalBanana said:
I have formatted everything and I believe I have removed everything useless from the memory. I have also flashed multiple roms and the issue is still there
Click to expand...
Click to collapse
Does the problem also occure when you have 0 extra apps installed so just rom and gapps?
It sounds like some background proces
IrrationalBanana said:
HI all!
I have an OnePlus One. A month ago it became unusably slow, where all animations took the phone 5-10 seconds to go through. Sounds and haptic feedback are immediate (pressing a button/typing), but the screen seems to lag behind.
One interesting example comes when rebooting the phone. The Android marshmallow bootlogo (CM13) takes at least 20 seconds to finish, but I can actually swipe up on the screen while the marshmallow logo is still on there and hear the screen unlock sound.
I have tried many different ROMs (SlimSaber, OxygenOS, CM13/12), deleting data, cache, dalvik and doing many, many factory resets. Nothing seems to help at all.
Anything that can be done to fix this little bugger? Setting the three animation settings to 0x seemed to help a little bit, but not all that much. Is there a completely animationless rom out there?
Click to expand...
Click to collapse
Have you tried flashing the stock rom via fastboot? If that doesn't solve your problem, it might be hardware related. You can find the latest fastboot update here: link
Keep in mind that if you want the latest cos13, you'll have to update your device via the ota. This method will also completely erase your device, including /sdcard
If there is no background processes, try to install Cynogen OS 12.0.
If the phone have the same issue, then it is hardware.
Sent from my A0001 using Tapatalk
moneyvirus said:
Does the problem also occure when you have 0 extra apps installed so just rom and gapps?
It sounds like some background proces
Click to expand...
Click to collapse
Problem is there even after many completely fresh ROM installs (formatted all data from memory)
What are the files that re absolutely necessary for the phone to operate? Could there be some hidden junk in the internal memory Im not seeing?
yeah, NAND trimming is important. But not for a fresh install
eng_saad said:
If there is no background processes, try to install Cynogen OS 12.0.
If the phone have the same issue, then it is hardware.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Phone became stuck on bootlogo after installing CM 12 snapshot
IrrationalBanana said:
Phone became stuck on bootlogo after installing CM 12 snapshot
Click to expand...
Click to collapse
firmware
IrrationalBanana said:
Phone became stuck on bootlogo after installing CM 12 snapshot
Click to expand...
Click to collapse
The best solution in my opionion is to restore the stock ROM [COS 12.1 / 12.0]
Follow the steps in this thread
NOTE that your data will be deleted.
IrrationalBanana said:
HI all!
I have an OnePlus One. A month ago it became unusably slow, where all animations took the phone 5-10 seconds to go through. Sounds and haptic feedback are immediate (pressing a button/typing), but the screen seems to lag behind.
One interesting example comes when rebooting the phone. The Android marshmallow bootlogo (CM13) takes at least 20 seconds to finish, but I can actually swipe up on the screen while the marshmallow logo is still on there and hear the screen unlock sound.
I have tried many different ROMs (SlimSaber, OxygenOS, CM13/12), deleting data, cache, dalvik and doing many, many factory resets. Nothing seems to help at all.
Anything that can be done to fix this little bugger? Setting the three animation settings to 0x seemed to help a little bit, but not all that much. Is there a completely animationless rom out there?
Click to expand...
Click to collapse
I had a similar problem on my lg g2. Some things to look out for before taking my advice:
-Is the animation/screen the only thing that's slow, but the background processes normal? (Like, if you type a bunch of letters, it registers all of them but the animation is slow).
-Prior to the problem, did you drop/bend your device, expose it to water, or take it apart?
If both (or one) of the top pertains to you, it's most likely a hardware issue. My g2 had the same problem, and it turned out to be a faulty flex cable that attached the screen output to the motherboard (I accidentally pulled too hard on it). Seeing how the OPO screen has a long black cable, that could possibly be the problem. If all else fails, and you have a bit of money to spend, get a replacement screen.
chikin said:
I had a similar problem on my lg g2. Some things to look out for before taking my advice:
-Is the animation/screen the only thing that's slow, but the background processes normal? (Like, if you type a bunch of letters, it registers all of them but the animation is slow).
-Prior to the problem, did you drop/bend your device, expose it to water, or take it apart?
If both (or one) of the top pertains to you, it's most likely a hardware issue. My g2 had the same problem, and it turned out to be a faulty flex cable that attached the screen output to the motherboard (I accidentally pulled too hard on it). Seeing how the OPO screen has a long black cable, that could possibly be the problem. If all else fails, and you have a bit of money to spend, get a replacement screen.
Click to expand...
Click to collapse
Thanks for the suggestions!! You are spot on with everything, the screen got cracked a while back and I bought a new screen for it. It was a bit dodgy and didn't fit well in the casing, so maybe a cable got pulled out lately?
On the background process thing; the typing thing is exactly as you described it. When writing my long WiFi password for example, I tap in all of the 18 characters and numbers of the password in 5 seconds, and then the screen spends the next 20 seconds doing the animation/typing in the characters, whilst I am not touching the screen. Does this mean the cables theory is solid? Or is it another hardware issue?
Stellar suggestions, I will probably spend an hour or two picking at the phone today, updates coming later
My OPO has never been slow on any ROMs. You can try to format your phone...
No result after removing and reconnecting display cables Formatted everything and installed a fresh ROM right after as well, no improvement.
Thanks however! Still open for business/suggestions
IrrationalBanana said:
No result after removing and reconnecting display cables Formatted everything and installed a fresh ROM right after as well, no improvement.
Thanks however! Still open for business/suggestions
Click to expand...
Click to collapse
send It to cc already
Traace said:
yeah, NAND trimming is important. But not for a fresh install
Click to expand...
Click to collapse
I have been reading trimming here but never found best or safe method. a link to best tutorial will be appreciated
#sychrome# said:
I have been reading trimming here but never found best or safe method. a link to best tutorial will be appreciated
Click to expand...
Click to collapse
Some roms trim by themself, others do not. It really difficult to tell which does and which not. U can test it if fstrim takes long time to run then your system usually didn't got trimmed anytime before.
Get Trimmer (fstrim) from Play Store. Its not necessary to trim system at all. Set your focus on partitions who have large amount of write processes like data or even cache.
IrrationalBanana said:
No result after removing and reconnecting display cables Formatted everything and installed a fresh ROM right after as well, no improvement.
Thanks however! Still open for business/suggestions
Click to expand...
Click to collapse
In my opinion, I still think it is a hardware error. Since you described some difficulty in replacing the screen, the cables might have been damaged, either during replacement or after. I suggest you buy a new screen, preferably one that comes already glued on to a frame.
So i've been trying to fix my wifi for the last few days, i've tried flashing the august update, factory resetting, doing This Guide, taking apart the device and it still won't ****ing work, i mean wtf? I was texting my friend and suddenly it ****ing shuts off and when it turns on it doesn't want to connect to wifi and does all short of crazy thing. No it's not a power button issue and no it's not hardware, the thing freezes constantly(and reboots afterwards). I don't know, this left a very bitter taste of android in my mouth, and that's disappointing for someone who has been in the ecosystem since donut came out. I won't blame the Nexus 5 it's a great device and it will always be a great device (If it's a hardware issue i wouldn't be this butthurt since this phone is 2+ years old).
Problem details:
*WiFi won't work. Data, bluetooth, GPS, NFC, cell network, etc works.
*MAC address stays at 02:00:00:00:00:00. When it briefly worked the MAC address was 00:8x:xx:xx:xx:xx or something.
*System has a 98% chance of freezing and ****ing up. Not power button issue. It then reboots after it freezes like ****.
*Everything else still works, i'm 99% certain that it's software's fault.
*Now it shows blank screenw with navbar and status bar present, but on the status bar it says 23.06 (its 23.10 currently), no sim icon and no battery icon. It did something similar when the issue first started
What i've tried:
*Smacking the device, jk. Clean flashing the august update.
*Wiping cache partition
*Deleted persist/wifi
*Doing the persist guide on xda
*Completely discharged and recharged it, WiFi works temporarily
*Using Pry-Fi. And wifi fixer app with a penguin icon.
*Pray to God 24/7
*Flashing AOSPA
What i will try:
????
It could be a hardware issue. I have two nexus 5 motherboards sitting in my junk pile that work perfectly except wifi either won't turn on or won't connect to any open or password-protected network. I have also tried different Roms, radios, and boot loaders. Once I changed the motherboard without changing anything else, wifi was perfect.
audit13 said:
It could be a hardware issue. I have two nexus 5 motherboards sitting in my junk pile that work perfectly except wifi either won't turn on or won't connect to any open or password-protected network. I have also tried different Roms, radios, and boot loaders. Once I changed the motherboard without changing anything else, wifi was perfect.
Click to expand...
Click to collapse
But, how could it be hardware? i haven't done anything to it, how do i know that it's hardware though? :crying:
DT1989DLX said:
But, how could it be hardware? i haven't done anything to it, how do i know that it's hardware though? :crying:
Click to expand...
Click to collapse
If you tried a complete clean install of a factory image, and it still didn't work, then it's probably an hardware issue. It really looks like it too, but I'm no expert. How would a software issue persist among different flashes? I'd say something fried on your motherboard, and now you have that issue with wifi.
It could be hardware. Both motherboards that I have came from phones that were never dropped or came in contact with any moisture.
This can happen suddenly, similar to the sudden death of the emmc chip on the Nexus 5.
The wifi and emmc issue is not that uncommon in Samsung s4 either.
Dark_Eyes_ said:
If you tried a complete clean install of a factory image, and it still didn't work, then it's probably an hardware issue. It really looks like it too, but I'm no expert. How would a software issue persist among different flashes? I'd say something fried on your motherboard, and now you have that issue with wifi.
Click to expand...
Click to collapse
audit13 said:
It could be hardware. Both motherboards that I have came from phones that were never dropped or came in contact with any moisture.
This can happen suddenly, similar to the sudden death of the emmc chip on the Nexus 5.
The wifi and emmc issue is not that uncommon in Samsung s4 either.
Click to expand...
Click to collapse
Ok so this morning it works again, but the software still kinda buggy (random freezes). I can access the web via chrome and i can download some stuff in the play store, is this still a hardware issue? I'm still worried the wifi won't turn on again though. The MAC address seems normal too now
edit: Nope, shuts off again. But it works in safe mode.... .wtf?
audit13 said:
It could be hardware. Both motherboards that I have came from phones that were never dropped or came in contact with any moisture.
This can happen suddenly, similar to the sudden death of the emmc chip on the Nexus 5.
The wifi and emmc issue is not that uncommon in Samsung s4 either.
Click to expand...
Click to collapse
The wiFi works again now, but the software is still buggy, the MAC address is normal and i can do things with wifi like i normally would. Is this hardware? I thought if the wifi hardware is dead it won't turn back on at all
edit: nope it shuts off again, works in safe mode
How long does wifi work in safe mode?
audit13 said:
How long does wifi work in safe mode?
Click to expand...
Click to collapse
Random. Today it worked for a few hours (not in safe mode). And yesterday it worked for like 30 minutes in safe mode
I still think it's a slowly dying wi-fi chip. If it's not too annoying, I would live with it.
audit13 said:
I still think it's a slowly dying wi-fi chip. If it's not too annoying, I would live with it.
Click to expand...
Click to collapse
Do you think the oven method will work to revive it?
It might but the fix would be temporary if it is a problem with the chip lifting.
same thing has happened to me just now .. its a common problem i think
wifi is f*****d
audit13 said:
It might but the fix would be temporary if it is a problem with the chip lifting.
Click to expand...
Click to collapse
Chip lifting....? What does that mean?
I define lift as a situation where the phone heats up and causes a chip to lift away from the circuit board, causing one or more broken connections at the solder points. The process of heating the circuit board in an oven is sometimes referred to as "solder reflow" by some people.
I have purchased Pixel 2 on 1st November from 3rd party online shopping, it was working fine until 5th December suddenly it's display went off , and never turned on, but phone is responding to touch, and also phone is ringing when receiving calls but not able to see anything on screen.
I have tried soft reset (holding power button for 30 sec), Flashing the OS 8.0 & 8.1 manually (successfully flashed) but still Display is not up.
If anyone has similar kind of issue & was able to resolve it. kindly let me know
Does it ever display at all, e.g. in bootloader, recovery, or splash screen when booting? If it does then the hardware is OK, and it's a firmware/software issue. If not then it may well be hardware. If you've already reflashed it with 2 different images and neither helped my suspicion is hardware anyway, so I think this is probably a warranty job.
Large Hadron said:
Does it ever display at all, e.g. in bootloader, recovery, or splash screen when booting? If it does then the hardware is OK, and it's a firmware/software issue. If not then it may well be hardware. If you've already reflashed it with 2 different images and neither helped my suspicion is hardware anyway, so I think this is probably a warranty job.
Click to expand...
Click to collapse
no, it does not display in any of the things, Bootloader, recovery, splash screen nothing....
wunnavabk said:
no, it does not display in any of the things, Bootloader, recovery, splash screen nothing....
Click to expand...
Click to collapse
The ribbon for the screen probably somehow came loose, or the screen is just defective. If there is nothing on the screen anywhere, even in bootloader, it's definitely gonna need to be replaced.