Related
My brother is running oxygen rom on his ns4g and recently the ear speaker has stopped working. A factory reset, wipes and restoring a nandroid backup the problem still persists. He's going to wipe and try a different rom to see if it continues. Any ideas in the meantime?
Sent from my SPH-D700 using XDA App
I'm sure this thought has crossed your mind, but could be hardware related.
Follow the leader @corythug
Yes but I was trying to eliminate software first and thought the problem might have been know.
Sent from my SPH-D700 using XDA App
Hardware issue. Id take the phone apart and inspect the speaker and solder points. Prob an easy fix.
sent from my Nexus S
It's under warranty so he'll just take it back to sprint. Thanks for the help!
Sent from my SPH-D700 using XDA App
Hello,
my Backbutton activates itself. While I am watching Videos, or whatever I do it stops shining and I am out of every application I'm using. After about half a minute it's shining again and I can use it normally. It's like pushing the button multiple times. Does anyone has an idea how to fix it? I tried different roms but it looks like an hardware failure to me.
Sent from my Nexus S using xda app-developers app
Happened to me as well it is an issue sometimes with samsung but covered under warranty bring it in to sprint
Hit the thanks button if i helped
Sending it back for support is not an option for me. I imported my device from the US to Germany. The support at Samsung Germany told me that they are not responsible for AMOLED devices.
My second problem ist that my IMEI is crashed since I flashed a rom where the dev made a little mistake. So Samsung won't give me any support.
I thought about changing the display but the price for a new one is about 190 Euro. Way too much... I can assemble and disassemble the device but I think that cleaning the device will not solve the problem.
Any suggestions?
Sent from my Nexus S using xda app-developers app
srichter said:
Sending it back for support is not an option for me. I imported my device from the US to Germany. The support at Samsung Germany told me that they are not responsible for AMOLED devices.
My second problem ist that my IMEI is crashed since I flashed a rom where the dev made a little mistake. So Samsung won't give me any support.
I thought about changing the display but the price for a new one is about 190 Euro. Way too much... I can assemble and disassemble the device but I think that cleaning the device will not solve the problem.
Any suggestions?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
It has nothing to do with the display though.
That's likely the part failing:
http://www.globaldirectparts.com/Nexus-S-Navigator-Flex-Ribbon-p/smsng6098595.htm
http://stellatech.com/samsung-gt-i9020-nexus-s-ui-flex,a,en,810423.html
Verify that the one you currently have isn't simply not connected right.
Thank you. I will have a look if the part is not right connected.
Maybe I have to replace it. But in that case 25 Euro are much cheaper than 190.
Sent from my Nexus S using xda app-developers app
This happened to me once. A day later my display completely died. I could turn on my phone, answer calls, etc the touchscreen worked, but I couldnt see anything. I had to get a new one..
I had this problem too.
I flashed a different radio, and boom!! issue resolved
I occasionally get this too. It only comes up when I'm using cm/cm based kernels though, very odd. I'm on matrix right now and it seems to Beowulf, anybody have some tips or suggestions?
Sent from my iPad using Tapatalk HD
I tried a different kernel and it looks like the problem is solved. I know that you should not count your chickens before they are hatched. But I really think that the kernel was the problem.
Anyway, I am just happy that my phone is working properly.
And now I am waiting for jellybean.
Sent from my Nexus S using xda app-developers app
srichter said:
I tried a different kernel and it looks like the problem is solved. I know that you should not count your chickens before they are hatched. But I really think that the kernel was the problem.
Anyway, I am just happy that my phone is working properly.
And now I am waiting for jellybean.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
What kernel were you using?
It was not the Kernel!
Changing the radio solved the problem.
Sent from my Nexus S using xda app-developers app
Check out this thread
http://forum.xda-developers.com/showthread.php?t=1277226
I had same problem and fixed it that way.
Sent from my Nexus S 4G using xda premium
It's Alive!
I don't see how the kernel would have anything to do with the backbutton. Although if it worked out then hey that's awesome. Amazing how much I have learned by reading the forums on this site.:victory:
Just clean off the the backbutton, and maybe it will stop or you have a software bug.
Problem Details below:
The problem is with the screen, though there is not a single scratch or anything wrong physically..
the screen misbehaves from left side of screen, only that portion.
it automatically starts touching itself... :cyclops:
had found its solution too but it which works temporary.
have to use an electric lighter on the screen to make it stop misbehaving.
This way phone works easily for almost a day without troubles.
Please let me know if any one has a permanent solution for the problem!
In case of any further query, please post in or pm me, any help in this regard will be appreciated.
Thanks & best regards,
Mortal Eternity!
Seems to me that digitizer is broken. You'll need to replace it.
Sent from my Nexus S using xda app-developers app
Ted Mosby said:
Seems to me that digitizer is broken. You'll need to replace it.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
by digitilizer you mean screen? no sir the screen is not damaged form any where....
I mean glass or touchscreen. It doesn't matter if u can see the damage or not, it can be faulty either way...
Sent from my Nexus S using xda app-developers app
You tried changing roms, kernels, etc? This can help you identify the solution.
Hi,
I've got a Desire S on stock ICS 4.0.4. The problem with the phone is that sometimes it reboots itself for no apparent reason.
The problem isn't new to me, it had the same problem on GB 2.3.5. It happens mostly in the same physical places in my house and on route to work.. strange!!!
Could a bad sd card be the cause?
Thanks in advance for your help.
Random reboots happen wery often due to so called:kernel's panic,..
when overload of the system is so great that it could not handle it anymore,
but may also be caused by the battery that is not sitting firmly in its place,
but then switches off by no apparent reason rather than reboots,
reboots may also be caused by some nasty process, that causes kernel to panic...
but stock manufacturer software is unlikely to contain such processes,
could it be an app you've installed perhaps,
or even a physical hardware part loosing the contact with motherboard/its part,, for a moment,
To diagnose it further- if a device is still stock and unlocked,
you could reflash ics ruu and leave it to work for a while clean,
without installing anything else.
While subject it to the conditions
in which reboots were happening before
I'm really hoping it isn't a hardware problem. The reboots happen the most when calling or just after a call, very annoying and the reason i gave the phone to my wife
Sent from my GT-I8190 using xda app-developers app
Olivier V said:
I'm really hoping it isn't a hardware problem. The reboots happen the most when calling or just after a call, very annoying and the reason i gave the phone to my wife
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
The first thing to check, as suggested above, is the battery. These have a habit of not fitting firmly, so get a piece of paper, fold it in half twice, and leave it between the battery and the outer case when you insert the battery.
It may not be the cause, but it is the easiest thing to check.
Olivier V said:
I'm really hoping it isn't a hardware problem. The reboots happen the most when calling or just after a call, very annoying and the reason i gave the phone to my wife
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Hardware problem does not necessarily mean a disaster and big costs,
it may just be a loose part,
but leaviing it as is, may lead to bigger troubles in the future,
Olivier V said:
I'm really hoping it isn't a hardware problem. The reboots happen the most when calling or just after a call, very annoying and the reason i gave the phone to my wife
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
I had exactly the same issue since I bought the device with different stock and custom software.
The solution in my case was to use only GSM (2G) or only WDCMA (3G) mode, not mixed. Hope this will help you too.
Sent from my Desire S
I'll try this. Will let you know if it works :thumbup:
Sent from my GT-I8190 using xda app-developers app
Also please post the contents of the file /proc/last_kmsg after a reboot occurred.
e.g.:
Code:
adb shell cat /proc/last_kmsg>messages.txt
Is this a file i can access without root?
Sent from my GT-I8190 using xda app-developers app
Olivier V said:
Is this a file i can access without root?
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Try and see
amidabuddha said:
I had exactly the same issue since I bought the device with different stock and custom software.
The solution in my case was to use only GSM (2G) or only WDCMA (3G) mode, not mixed. Hope this will help you too.
Sent from my Desire S
Click to expand...
Click to collapse
I've just got home and set it to gsm only. If it does not reboot by itself this week I'll be a hero to my wife
Sent from my GT-I8190 using xda app-developers app
Aquous said:
Try and see
Click to expand...
Click to collapse
I've tried it and indeed, I can access it. If the phone reboots I will post a link.
Sent from my GT-I8190 using xda app-developers app
I'm having similar issues here with my Desire S, HTC ICS RUU Update Software, not rooted.
To summarize:
If I use the device with a SIM card in battery mode it reboots right after entering the PIN.
If I use the device without a SIM card in battery mode, everything works fine
If I use the device with a SIM card in charger mode, everything, including calls/text/3G Internet works fine
If I disconnect the charger and have a SIM inserted, my device reboots right away
If I use my device with networking mode "WCDMA only" in battery mode, everything works, but switch to "GSM only" or "Auto select" causes reboot
I tried 3 different SIM cards from two different carriers, hence it seems not to be related to my SIM card. I can also eliminate that this is SD card related, as I tried it with and without a SD card inserted without any difference. As the device is working in battery mode without a SIM card, I think the battery cannot be the reason either.
These reboots render my phone almost completely unusable, as using WCDMA only is not an option for me...
I must say that the gsm only mode did the trick. It's only been 3 days since but I'm hopefull
Sent from my GT-I8190 using xda app-developers app
Hi! Yesterday I took my Nexus 5 on a trip on top of my car and he decided to take a jump to see what will happen... Anyway, after really exciting jump and after I've found him, he was pretty much destroyed, but still working. So, I ordered new display with side bezels and repaired him today. At first everything seemed to be working, but now WiFi and Bluetooth won't turn on. I've took the back panel off to make sure everything is OK, and then I could turn Bluetooth on. After putting everything together again, it won't turn on. And I saw that for some short period of time, just after I assembled the phone, it had WiFi. :-/
So, now I'm confused.
Is it possible to have software issue, or could it still be hardware?
How can I, anyway, check if everything works with hardware?
Btw. I'm still on stock unrooted ROM. (Wanted to see how it is to have a stable ROM after couple of years )
Sent from my Nexus 5 using xda app-developers app
If anyone is interested how I saw the WiFi was on or how it shows now...
Here you are...
Sent from my Nexus 5 using xda app-developers app
And... For those interested in how it looks...
Shattered, new original display, assembled again
Sent from my Nexus 5 using xda app-developers app
_BluE_AngeL_ said:
Hi! Yesterday I took my Nexus 5 on a trip on top of my car and he decided to take a jump to see what will happen... Anyway, after really exciting jump and after I've found him, he was pretty much destroyed, but still working. So, I ordered new display with side bezels and repaired him today. At first everything seemed to be working, but now WiFi and Bluetooth won't turn on. I've took the back panel off to make sure everything is OK, and then I could turn Bluetooth on. After putting everything together again, it won't turn on. And I saw that for some short period of time, just after I assembled the phone, it had WiFi. :-/
So, now I'm confused.
Is it possible to have software issue, or could it still be hardware?
How can I, anyway, check if everything works with hardware?
Btw. I'm still on stock unrooted ROM. (Wanted to see how it is to have a stable ROM after couple of years )
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
i'm 99 percent sure it's hardware. software is flashed into chips so that cannot be the issue. it's hard to find out yourself wich part is broken. the best thing you can do is send it to your seller or a near phone shop.
Did the screen flicker what so ever? This happen to me because the screen was not original and I end up sending it back to the seller. Where did you get your screen from? You might have broke something when assemble.
Sent from my Nexus 5 using xda app-developers app
wow! That's what I would call a well shattered screen.
I would suggest you to take it apart again if that's not too hard to do, blow the logic board in case some particles are rolling on it and reassemble it. It could do the trick eventually. Re-flashing stock Rom shouldn't be ignored. At least on a PC, a driver can get corrupted when a laptop falls.
GUGUITOMTG4 said:
wow! That's what I would call a well shattered screen.
I would suggest you to take it apart again if that's not too hard to do, blow the logic board in case some particles are rolling on it and reassemble it. It could do the trick eventually. Re-flashing stock Rom shouldn't be ignored. At least on a PC, a driver can get corrupted when a laptop falls.
Click to expand...
Click to collapse
This was my screen lol
Sent from my Nexus 5 using xda app-developers app
I was thinking that too, but why it worked for some time then...
Maybe some of the connections are not connected well.
I'll try to see it one more time tomorrow...
Sent from my Nexus 5 using xda app-developers app
I ordered my screen from vodafone repair service in Nürnberg, Germany and it came the day after. (It costs 140€, and if you want the repair too, then it's 199€. Not very happy about the price...) My replace screen is original from LG and works perfectly. I have to say- maybe even better than the old one. No flickering whatsoever. Backlight is also a bit better because it is equally divided over the screen. Plus, the bezels had new buttons on it, and now has smaller holes on the bottom and power button doesn't rattle any more. From the outside, only the back cover now has two small scratches. everything else is great.
I'm pretty much sure that something didn't connected correctly because sometimes bluetooth works. Tomorrow I'll disassemble it again and see.
Sent from my Nexus 5 using xda app-developers app
Maybe its better to send it to lg for repairs? That's what I'm planning to do. I bought my replacement screen for 150 and it was just hell because so many issues. That's the same price for a repair by lg. Im going to sent it to lg soon but not yet because I been to lazy lol.
Sent from my Nexus 5 using xda app-developers app
The service wanted to charge me almost 60€ more for their work, plus they said that they would most probably reflash the ROM and I would lose all my data...
And I only wanted to save my data. So, for me, this is the best solution.
Sent from my Nexus 5 using xda app-developers app
Sounds like the antennas are not contacting properly. Seems it can happen to anyone upon removing the backplate.
Sent from my Nexus 5 using Tapatalk
I've just disassembled it and reassembled again. Everything looks good. All connections are good and nothing seems to be loose.
I even tried to press the back panel around the camera lens to make a better contact with the antenna, but still nothing.
Looks like this in the WiFi settings...
So, actually, I think it's a software problem and am going to root it now and flash the new ROM.
After that we'll see.
If there isn't any success after that, you all know where to find spare parts for your Nexus 5.
Sent from my Nexus 5 using xda app-developers app
_BluE_AngeL_ said:
I've just disassembled it and reassembled again. Everything looks good. All connections are good and nothing seems to be loose.
I even tried to press the back panel around the camera lens to make a better contact with the antenna, but still nothing.
Looks like this in the WiFi settings...
So, actually, I think it's a software problem and am going to root it now and flash the new ROM.
After that we'll see.
If there isn't any success after that, you all know where to find spare parts for your Nexus 5.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Hope it's just software issue, reflash stock after unlocking bootloader http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
GUGUITOMTG4 said:
Hope it's just software issue, reflash stock after unlocking bootloader http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
I just finished reflashing the stock ROM and it seems like it wasn't a software issue... after selecting the language it says "Turning Wi-Fi on..." and it doesn't do anything...
More suggestions?