Hi there,
I'm experiencing massive issues with the Nexus 5 of my wife. Everything is basically broken
It started 2 days ago, the phone start rebooting without reason and heating a lot. Applications sometimes hang for a long time, or the screen stays black with only the notification bar displayed.
Wifi is never able to connect, even though the welcome screen is able to display available wifi. On the welcome screen after a fresh flash, nothing happen when I enter the WIFI password and try to connect. Only the "ignore" button is available, as if I have done nothing.
LTE connectivity seems to work, but I have removed the SIM card for further testing, so it's hard to say.
Parameters screen sometimes works, sometimes won't. Battery consumption screen never works.
The phone is never able to shutdown properly, it hangs forever on the shutdown loading circle; I always have to hard-reboot.
I changed the battery (I had a spare one ordered few days before the problem occurs just to see if it improves the battery life), with no luck.
When I opened the phone to change the battery, it is clear the heat come from the CPU.
I tried (I wiped everything each time in between):
- factory reset
- flash a stock rom from Google website (MMB29K)
- flash latest Cyanogenmod rom (ZNH0EAO2NM)
I have the same issues with any of those 3 roms. I captured some logs while running MMB29K and ZNH0EAO2NM:
Stock (MMB29K) logs: https://drive.google.com/open?id=0B-CDc3nzF3e3M28tM2xjTmJKa28
Cyanogenmod (ZNH0EAO2NM) logs: https://drive.google.com/open?id=0B-CDc3nzF3e3TVUtTmExZDBLUms
The only state where the phone is stable is when TWRP is booted, which is not so useful...
I'm thinking of a hardware issue, but is there anything else I can try? What do you think?
Thanks a lot!
Nobody?
I said the same thing in another post. The fact that flashing different ROMs with the same issues kinda point to hardware problem. I'd guess something fried on the motherboard and it's causing weird behavior. Funny thing, the other post also reported wifi not connecting issues, so I'm thinking there is something that breaks in older Nexus 5 phones that cause wifi issues along with other random reboot problems.
Related
Received this phone (THL W8S) 5 days ago, and straight out of the box it has had a serious issue where the phone will lock up, the screen will fade slowly to black, and then reboot itself. The problem occurs both after factory resetting AND in safe mode.
The phone is unrooted and running the stock ROM.
Basically during use, the screen suddenly becomes unresponsive to touch and the physical buttons (home, volume, power) all stop functioning. As soon as the phone locks up this way, the screen slowly fades to black over about 60 seconds, at which point I have to leave it to fade completely before it reboots itself.
It happens most frequently when using any browser (stock, or otherwise) taking from less than 5 seconds to around 5min before the random lock up occurs) but also happens when scrolling through messages; scrolling through emails in either of the stock apps; using a compass app which came pre-installed (very quickly).
Initially I thought it might have to do with WiFi, but problem also cropped up with WiFi off, using 2/3G. Then in troubleshooting also managed to get it to happen using the camera (lot of motion, and repeatedly taking snaps).
Also odd is that the batteries I received in the box were generic black ones, not the official stamped/logo'ed THL ones I've seen on every website and every unboxing of this particular phone. So while there's a possibility this may be a battery issue, the fact that the phone hasn't done this while using a more battery draining app (Beach Buggy Blitz; Rayman Jungle Run) makes me think this is a deeper hardware fault related to , although I don't know enough about voltages and such to rule it out completely.
I have a couple videos showing the problem, but unfortunately I'm not allowed to put the links here. Should both be easily found by searching:
THL W8S issue Kostas P
if interested.
Any thoughts/views would be greatly appreciated!
kostako said:
Received this phone (THL W8S) 5 days ago, and straight out of the box it has had a serious issue where the phone will lock up, the screen will fade slowly to black, and then reboot itself. The problem occurs both after factory resetting AND in safe mode.
The phone is unrooted and running the stock ROM.
Basically during use, the screen suddenly becomes unresponsive to touch and the physical buttons (home, volume, power) all stop functioning. As soon as the phone locks up this way, the screen slowly fades to black over about 60 seconds, at which point I have to leave it to fade completely before it reboots itself.
It happens most frequently when using any browser (stock, or otherwise) taking from less than 5 seconds to around 5min before the random lock up occurs) but also happens when scrolling through messages; scrolling through emails in either of the stock apps; using a compass app which came pre-installed (very quickly).
Initially I thought it might have to do with WiFi, but problem also cropped up with WiFi off, using 2/3G. Then in troubleshooting also managed to get it to happen using the camera (lot of motion, and repeatedly taking snaps).
Also odd is that the batteries I received in the box were generic black ones, not the official stamped/logo'ed THL ones I've seen on every website and every unboxing of this particular phone. So while there's a possibility this may be a battery issue, the fact that the phone hasn't done this while using a more battery draining app (Beach Buggy Blitz; Rayman Jungle Run) makes me think this is a deeper hardware fault related to , although I don't know enough about voltages and such to rule it out completely.
I have a couple videos showing the problem, but unfortunately I'm not allowed to put the links here. Should both be easily found by searching:
THL W8S issue Kostas P
if interested.
Any thoughts/views would be greatly appreciated!
Click to expand...
Click to collapse
Hi, I also have the same problem described by kostako. Please look for your feedback as soon as possible.
thank you very much
Best regards.
san_tony said:
Hi, I also have the same problem described by kostako. Please look for your feedback as soon as possible.
thank you very much
Best regards.
Click to expand...
Click to collapse
Hello, I wanted to inform you that lately the reboot occur concurrently with application updates.
They are like your impressions.
Best regards
THL W8S the screen fade and reboot too!!
Hello!
I received the phone on 12 September. The screen faded from the first minutes of use. Yesterday I came three times. In "THL mobile store" recommend updating the firmware. But the update I have not found anywhere.
any suggestions
Thank you very much in advance.
Hi there,
someone has problems that the touchscreen is not responding?
Have CM11 - current nightly, Fournace kernel 1.0.2 and OPO lockscreen flashed ....,Only the lower right corner is responsive to inputs.
I had the problems also 2 times with the CM11S-ROM.
Has anyone else this problem?
Sun_Dancer said:
Hi there,
someone has problems that the touchscreen is not responding?
Have CM11 - current nightly, Fournace kernel 1.0.2 and OPO lockscreen flashed ....,Only the lower right corner is responsive to inputs.
I had the problems also 2 times with the CM11S-ROM.
Has anyone else this problem?
Click to expand...
Click to collapse
I have the same problem. It's intermittent and goes away after a while but it comes back often enough to make my device unusable when needed. I literally can't answer calls or log into my device because of this. Is no one else having this problem? The issue persists into recovery so it might be hardware.
Franco r13 has new touch drivers implemented. Try it.
OP you say it as if your screen is never responsive, only in the bottom of the screen. That sounds like a RMA.
I will look into Franco r13 tonight. In the meantime, here is how my problem happens:
- Most of the time touch screen is working as expected
- Sometimes the touch screen becomes unresponsive to many areas on the screen, but some small areas still work
- When the above issue occurs, it is only temporary. If I let the phone sit for a few minutes it usually comes back.
- Restarting does not fix the problem, and the problem persists into recovery mode (I forget which recovery I have, but it has touch screen input)
- The problem started with phone being 100% stock, although only after the OTA update a few days ago
notten said:
I will look into Franco r13 tonight. In the meantime, here is how my problem happens:
- Most of the time touch screen is working as expected
- Sometimes the touch screen becomes unresponsive to many areas on the screen, but some small areas still work
- When the above issue occurs, it is only temporary. If I let the phone sit for a few minutes it usually comes back.
- Restarting does not fix the problem, and the problem persists into recovery mode (I forget which recovery I have, but it has touch screen input)
- The problem started with phone being 100% stock, although only after the OTA update a few days ago
Click to expand...
Click to collapse
Yeah, try Franco then. Mine feels better now. It wasn't too responsive before either.
Hello people,
I have been experiencing a weird issue lately with my OPO. It seems that for no apparent reason, my accelerometer's X-axis gets stuck in 0.000m/s² value, resulting in the inability to rotate the screen to landscape mode. And, again for no apparent reason, it starts working correctly... until the time it breaks again!
It's really crazy. Last night for example it was broken, I was browsing xda from chrome just to find a possible solution, and suddenly it started working, device just turned from portrait to landscape! When I woke up it was not working again. Sometime around the afternoon it started working again -without me doing anything-, not even handling the phone, it was flat on my desk! After 8 hours of working, it got stuck again right as I was writing this post...
Even when it's stuck however, If I try to shake the device very hard (to the point that it almost flies off my hands) I get a very small reading, around ~0,050m/s² to ~0.200m/s².
(readings were taken with Sensors app)
A reboot does not fix this. I have tried lots of configurations, it's not app/xposed related since it also happens after a full wipe and after flashing the 44S fastboot image. It's not kernel related (I think...) since it happens both with Stock and Franco. So it's either hardware, or related to the ROM.
I believe (and really hope) it's not hardware related since it started a while after flashing 44S, before that the accelerometer worked flawlessly. Also, I may be ignorant here, but if it was hardware it would break down once and for all, it wouldn't work intermittently, right? Either way, the device of course was never dropped or hit so as to damage the sensor in any way.
I've also read one report of the exact same problem on the OPO forum, but could not contact the poster, and several other reports of the accelerometer breaking down (and later being fixed) but in CM nightlies.
I have already tried to calibrate/reset through several apps but without any success. Is there anything else I can try to, erm, "un-stick" it? Maybe there's a configuration file I need to delete or something or a specific way to reset/calibrate it in CM. Or even tapping the device in a specific place? (lol I'm reaching here, but I can't think of anything else).
I have already reported the issue to Jira, if someone is experiencing the same please provide your input here.
After installing Lollipop, everything became unbearably slow. I've tried flashing multiple ROMs, both Lollipop and Kitkat, but everything remains so slow: the actual boot-up process and the ROM itself. Does anybody have any ideas about what can be done about this? In fastboot I see hammerhead D820(H) 32GB; HW version rev_11; Bootloader version HHZ12d, Baseband M8974A-2.0.50.2.22. Lock state is unlocked. Any suggestions will be highly appreciated!
Wipe cache and see if that helps and disable Chrome's integration into the app switcher. Also get rid of Facebook and FB Messenger.
Sent from my Nexus 5 using XDA Free mobile app
Instead of Lollypop try some LSD
Thanks. But it is that slow even before any of these apps are loaded (e.g. after I do a factory reset and flash a new rom). Is it possible that Lollipop did sthg to the hardware? If so, how could I find out? Just to give you an idea about how slow exactly it is: when I am typing 5 letters at normal speed, it takes until the fifth letter before the first letter actually displays on the screen. I should also note that when the screen goes off, I can no longer get it on again without a reboot...
I'm still trying to figure out what this might be. I first thought my problems were similar to those that others have described, but I now think they be different. Here are some of the issues I'm encountering:
when I boot up the phone (whether in kitkat or lollipop), the initial android (animation sequence is already incredibly slow
there are all sorts of strange things happening with my screen. When it goes to sleep in Android, I can not wake it up anymore. When it goes to sleep in recovery, and I push the power button, the screen goes (again after some time) from pitch dark to a slightly 'lit' dark, but it never displays anything, and I have to reboot again to get the info on the screen. Also, the screen is even slow in twrp - when I swipe to do a factory reset, for instance, there is also a noticeable lag.
I have tried with various ROMs (both stock and not); with ART and Dalvik, etc. but none of these changes seem to affect the slow screen issues
Does anybody have any ideas about what the problem might be? I should also add that we had the screen replaced a few months ago - could that have something to do with it?
sdspieg said:
I'm still trying to figure out what this might be. I first thought my problems were similar to those that others have described, but I now think they be different. Here are some of the issues I'm encountering:
when I boot up the phone (whether in kitkat or lollipop), the initial android (animation sequence is already incredibly slow
there are all sorts of strange things happening with my screen. When it goes to sleep in Android, I can not wake it up anymore. When it goes to sleep in recovery, and I push the power button, the screen goes (again after some time) from pitch dark to a slightly 'lit' dark, but it never displays anything, and I have to reboot again to get the info on the screen. Also, the screen is even slow in twrp - when I swipe to do a factory reset, for instance, there is also a noticeable lag.
I have tried with various ROMs (both stock and not); with ART and Dalvik, etc. but none of these changes seem to affect the slow screen issues
Does anybody have any ideas about what the problem might be? I should also add that we had the screen replaced a few months ago - could that have something to do with it?
Click to expand...
Click to collapse
Probably the replacement screen has been reconnected poorly. There's nothing you can do on software side, for me, it's more like a hardware problem.
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
pesche80 said:
Hello,
can anybody recommend an alternative kernel (for SLIM 7 rom), that allows me to increase the minimum CPU frequency.
I remember by doing that on a HP touchpad, I could avoid SoD.
Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
pesche80 said:
Hello everybody,
I've got a problem with a Oneplus One.
First a brief history of the device. I got it on ebay with a shattered display about 1 1/2 years ago and replaced the display. Since then my girlfriend managed to shatter the display 3 times more. So I'm quite used to replace the display on this device.
Since the last display replacement (the 4th) the device developed a partial Screen-of-Death problematic.
Sometimes the display just stays blank, while the backlight is clearly working (you can see the blueish light in dark environments). Also the device reacts to touch and button inputs, like e.g. double-tap-power to start camera. Or double-tap-screen to wake up (you can feel the vibration or display input sounds).
I "just" have to wait about 10-20 seconds, try again and the display turns on without any problems. In other cases I have to try this a couple of times to wake the screen.
A hard reset is not necessary, the device will wake up sooner or later. In this aspect it differs from all SoD descriptions I found online!
An other strange thing is, after the screen replacement the device forgot all wifi networks. The wpa_supplicant.conf was empty. Strangely enough all other apps were OK, I didn't noticed any irregular acting applications.
As the device was sill running on CM13 I decided to give it a fresh nougat installation and assumed the SoD symptomatic would vanish.
Now after flashing back and forth different factory images and custom-rom's the SoD is still there and renders the device almost unusable.
I tried the latest CM13 snapshot and sultans CM13, which I have been using on another OPO without problems for a long time.
I also tried to install different original factory images.
cm-13.1.2-ZNH2KAS3P0-bacon-signed-fastboot_64GB.zip
and also another one I got long time ago from Oneplus to fix an annoying Wifi-Reboot-Problem. It contained additional image files like persist.img and reserve4.img.
I tried to turn on and off the setting for the proximity sensor that could interfere with the activation of the screen.
I tried different radio firmware's, as I could remember that there had been some problems in the past with incompatible firmwares, android versions and the proximity sensor.
I enabled and disabled all off-screen-gestures, although they are always working regardless if the display stays blank or not.
Unfortunately I've got no luck.
Literally every single android version I tried suffered from SoD. The only problem free thing is TWRP. Running the latest 3.1.1-0 I never got a blank/black screen on powering up the display.
So now I'm out of ideas and would be happy to hear any additional guesses to fix this problem.
I was also wondering if anybody knows more about the SoD. I couldn't find any information's regarding the causes of this problem. Is it hardware related or software?
thanks!
p.s. another strange thing I noticed now on the latest Slim7 rom (20170526). If I try to take a screenshot with power+vol-down, the screenshot animation happens. But a status bar notification from Android-System tells me, there is not enough free space to save the screenshot. But there is at least 40GB of free space.
I'm not sure if this is related to my problem or just to Slim7. And I'm also a little tired to reflash the device just to test this issue...
Maybe there is a problem with permissions or the flash memory?
p.p.s here a logcat. I couldn't find anything helpful.. https://pastebin.com/UWfwc1VX
Click to expand...
Click to collapse
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/orig-development/cm-lightning-kernel-v1-t3273308
Only this kernel is fully compatible with AOSP-based roms like Slim7.
---------- Post added at 08:37 AM ---------- Previous post was at 08:34 AM ----------
I've had this issue before,it is due to faulty display only.I changed the display and it started working normal.
Ps-Better change your gf.
Click to expand...
Click to collapse
Thanks!
I'm going to consider a new display... but not a new gf
pesche80 said:
Thanks!
I'm going to consider a new display... but not a new gf
Click to expand...
Click to collapse
Don't forget to invite me to your wedding.