Related
Hi all,
I tried doing a search on this before posting this thread. No luck. I just got my TP2 on sunday. I let it charge and flashed HardSPL and a few roms. I noticed my phone would turn completely off when I open and close the screen. At first, I thought it was the display turning off to save power, but the phone is actually turning completely off and I need to hit the power button and boot it back up again. Is this a setting I need to change? Or could there be something wrong with my phone? I also tried going back to the stock rom to eliminate that as a cause and the same thing happens.
Any help is appreciated.
I have posted an almost similar question here with no reply.
http://forum.xda-developers.com/showthread.php?t=553378
Not sure what the problem is. In my case the solution is not to close the keyboard when OneNote Mobile is still open!
My colleague is having the same prob, from what he is experiencing, i would suggest a hardware fault, probably just a loose ribbon cable... but best send it back to HTC to avoid voiding your warranty
palatkik said:
I have posted an almost similar question here with no reply.
http://forum.xda-developers.com/showthread.php?t=553378
Not sure what the problem is. In my case the solution is not to close the keyboard when OneNote Mobile is still open!
Click to expand...
Click to collapse
I don't OneNote is my problem. Since I don't use it.
rosebud said:
My colleague is having the same prob, from what he is experiencing, i would suggest a hardware fault, probably just a loose ribbon cable... but best send it back to HTC to avoid voiding your warranty
Click to expand...
Click to collapse
I guess it's time to give TMO a call. Just need to flash everything back to stock.
Thanks for the suggestions guys. I was hoping to avoid having to send it back, but i might as well.
Albaholic said:
Hi all,
I tried doing a search on this before posting this thread. No luck. I just got my TP2 on sunday. I let it charge and flashed HardSPL and a few roms. I noticed my phone would turn completely off when I open and close the screen. At first, I thought it was the display turning off to save power, but the phone is actually turning completely off and I need to hit the power button and boot it back up again. Is this a setting I need to change? Or could there be something wrong with my phone? I also tried going back to the stock rom to eliminate that as a cause and the same thing happens.
Any help is appreciated.
Click to expand...
Click to collapse
Hi,
I had this issue to and send the phone in for repair. The said that it was a problem with the mainboard - replaced it and send it back. It now works perfect.
REMEMBER!!! If you want to send the TP2 in for repair you must reflash the SPL back to the original one, I think it is 0.79.0000 (see http://forum.xda-developers.com/showthread.php?t=550131 for how to restore to the original HardSPL)
discoverd the same issue, happened to me about a week ago for a few times, when i slide in/out the keyboard. It just habbend about 4 times, but didn't happend again since this time ... i will have a eye on it...
Same here. The screen turns off completely but the phone actually works and I can receive or place calls. Called the HTC support and they advised to try if a hard reset will fix it before sending the phone in. The tricky part here is that this issue can not be recreated easy in their service as it happens randomly with me (sometimes it works fine for days). I am still trying to find out what causes this issue on first place. I think it started right after I installed IGO 8 and changed some power settings in the ini file but it kept doing this after I removed it. I also tried to disable the light sensor (the one that turns the screen off when you place the handset to your ear during a call) because it looks exactly like this - screen turns off but the phone works. So, I will give it another week and I will try the hard reset.
What roms do you guys have this issue with? I am using the stock T-Mobile US with HardSPL.
wejergang said:
Hi,
I had this issue to and send the phone in for repair. The said that it was a problem with the mainboard - replaced it and send it back. It now works perfect.
REMEMBER!!! If you want to send the TP2 in for repair you must reflash the SPL back to the original one, I think it is 0.79.0000 (see http://forum.xda-developers.com/showthread.php?t=550131 for how to restore to the original HardSPL)
Click to expand...
Click to collapse
Did they replace the entire phone or just the mainboard?
ma6inista said:
Same here. The screen turns off completely but the phone actually works and I can receive or place calls. Called the HTC support and they advised to try if a hard reset will fix it before sending the phone in. The tricky part here is that this issue can not be recreated easy in their service as it happens randomly with me (sometimes it works fine for days). I am still trying to find out what causes this issue on first place. I think it started right after I installed IGO 8 and changed some power settings in the ini file but it kept doing this after I removed it. I also tried to disable the light sensor (the one that turns the screen off when you place the handset to your ear during a call) because it looks exactly like this - screen turns off but the phone works. So, I will give it another week and I will try the hard reset.
What roms do you guys have this issue with? I am using the stock T-Mobile US with HardSPL.
Click to expand...
Click to collapse
Did you ever resolve your issue? i ask because I am having he same problem on a Sprint Touch Pro 2
coppertop24 said:
Did you ever resolve your issue? i ask because I am having he same problem on a Sprint Touch Pro 2
Click to expand...
Click to collapse
Sorry, forgot to update this thread. I ended up getting a replacement from TMO. I am much happier now that my phone doesn't turn off whenever I close the screen. Get a replacement while you can and ask them nicely if they can overnight it to you. I did.
Actually, this was a software problem in my case - I did the hard reset 2 weeks ago and since then I have not experienced the issue. I am going to start installing my previous programs one by one to find out what caused the problem.
Same
I have the same problem,
The hard reset solve the problem?
please heeeeelp
Hi, I'm new to this forum.
Some days ago my DZ started to turn on the screen randomly when it was locked. The phone is rooted, so i tried to wipe all data and install an updated version of my rom (virtuous), but it did not help. And now the screen also turns on/off (flashes for a couple of seconds) when I use it.
Does anyone has had this kind of trouble before? I hope it's not some hardware that are broken :/
Thanks for helping!
How's your phone now? My G2 was doing what sounds like yours was doing too, and then just died completely (the screen that is everything else works).
I bought a new LCD replacement hoping it would fix the issue. Followed a Youtube bit on replacing it, and successfully reconnected everything, but its not working. I'm going to be taking it apart again tomorrow to see if I possibly missed a connection but I don't think the screen replacement is going to work.
Could be a software issue perhaps. What are your thoughts?
When I try to turn on bluetooth, the icon and text indicates that the system is trying to turn it on. However, it never actually turns on and after a few minutes reverts to indicating that BT is shut off. This problem used to occur sporadically and sometimes seemed to be cured by rebooting. However it is now at the point that it just won't turn on no matter what. I did the requisite googling and found nothing very definitive. It looks like I may have to do an exchange on the unit but I would rather not go to the effort of unrooting this unit and rooting the replacement.
Any suggestions of things to try beyond what I have indicated above?
TomSilverSpring said:
When I try to turn on bluetooth, the icon and text indicates that the system is trying to turn it on. However, it never actually turns on and after a few minutes reverts to indicating that BT is shut off. This problem used to occur sporadically and sometimes seemed to be cured by rebooting. However it is now at the point that it just won't turn on no matter what. I did the requisite googling and found nothing very definitive. It looks like I may have to do an exchange on the unit but I would rather not go to the effort of unrooting this unit and rooting the replacement.
Any suggestions of things to try beyond what I have indicated above?
Click to expand...
Click to collapse
Are you using an experimental ROM or stock rooted?
Jedi Mind Trick XI (although the problem has been growing worse and has happened across the last several JMT versions). I will give a stock rooted ICS a try.
I just tried a stock rom and the problem persisted.
I have the same problem
I have scoured the net looking for an answer, any answer, to this problem. It seems that a few people are having the same issue. But before it is ever answered, some dip$#!t always jumps in and says "I have the same problem, my phone won't connect to my car." Then the conversation goes off into other people that can't connect their bluetooth to their car or their headset- or their cat... That is not the same problem!!!
I cannot turn my bluetooth on unless I soft reset the phone. Even after I've gotten the bluetooth working, if I restart my phone the bluetooth turns off and when you try to turn it on, it says "Turning on Bluetooth..." It cycles for about a minute and a half and then goes back to "To see devices, turn on Bluetooth."
I bought this phone on Amazon for what appeared (at the time) to be a reasonable price. Since then, I believe that I have read at least one of the seller's post about bluetooth not coming on (no proof, just an educated guess). The seller probably got rid of the phone because noone could or would give an answer to this problem. Heck, it's possible that every post that I've read so far is by someone who owned this phone at one point or another. :silly:
I am sending this post to XDA because even the adminstrators on android forums say that you guys are the smartest and most responsive forum available. (Okay, they didn't say smartest- it was implied). Please help me resolve this issue.
I rooted this phone the moment that I pulled it out of the box. In other words, I don't know if the bluetooth issue is caused by the root, or if the previous owner didn't root the phone and also couldn't get the bluetooth to work. I believe that, because the phone is rooted, I should be able to remove and reinstall the app that bluetooth is based upon.
I am not a techie, the only reason I know anything about root is because I was complaining to someone about my old phone and how all of the bloatware that seems to constantly run eventually kills my battery. He told me about rooting, and it was easy enough - the rest is history. In other words, if you ask me for more information- I promise that I can give it to you. Yet, have patience with me if I ask you a question that you believe that any person that has rooted their phone should know.
I really hope that you guys can help me without bricking my phone. I truly appreciate any suggestions or thoughts on this matter.
jzxpw6;34880517I cannot turn my bluetooth on unless I soft reset the phone. [/QUOTE said:
I may have figured out what is going on, although I can't understand why it is (maybe someone more versed with processes can help me figure this out).
Using Titanium Backup, I first froze the two bluetooth items (Bluetooth Share and Bluetooth Test). Of course, that didn't remove anything, but I wanted to make sure that I could. Then I wanted to see how Bluetooth Share would react without Bluetooth Test. I unfroze Bluetooth Share.
I was then able to turn on and off Bluetooth fine. I restarted the phone and Bluetooth came in just like it did on my old phone. I guess I want to know:
1) Is the Bluetooth Test the cause of my problem?
2) Why is it there?
3) If I uninstalled it, would I experience a major hiccup?
There is still the possibility that this was simply a fluke, and very soon I will go back to the old bluetooth soft reset problem.
There is, however, one distinct difference between this phone and the last and may be the "drop out" that everyone else seems to be having. I have a Chevy Malibu with bluetooth in the stereo. On my old phone, when I started the car and got going, the word "Bluetooth" would appear on the digital display for about 10 seconds, which means that the vehicle detected and connected the bluetooth pairing. Yesterday, as I was driving in the car, every 5 minutes or so, "Bluetooth" would appear on the digital display.
This leads me to the conclusion that Bluetooth is dropping out and being picked up continuously by my vehicle. Does anyone have any thoughts on this? I'm okay with that as long as when I am talking to someone for more than 5 minutes I don't have to keep calling them back. I simply want to know what you guys think about this issue.
Click to expand...
Click to collapse
I am beginning to think that the problems I have had are related to the condition of the battery contacts.I have several third party batteries with contacts that are somewhat damaged from the pins on an external charger that came with them. I seem to experience a variety of problems when I try to use them.my original factory battery seems to work most of the time. I have several new Samsung batteries on order and will post again if they seem to solve the problem.
Sent from my SGH-T989 using Tapatalk 2
i had the same problem and it started with JMT so I switched roms countless times and the problem kept coming back. It would work for a little bit but when i turned it off it would not turn back on. I decided to go back to stock to see if the problem was still there and it was gone. Since then I have rerooted and once again flashing diff. rom every other day and bluetooth works just fine.
Well it seems no answer was found. I'm having the same issue as stated above. In my case, my bluetooth (custom ROM) keeps trying to turn on with the message "Turning On Bluetooth" until I soft reset the phone, after that it works fine.
enveous said:
Well it seems no answer was found. I'm having the same issue as stated above. In my case, my bluetooth (custom ROM) keeps trying to turn on with the message "Turning On Bluetooth" until I soft reset the phone, after that it works fine.
Click to expand...
Click to collapse
Was having bluetooth crashes for months using CM 10.1 on a T989 (no custom kernels)
Would crash anytime I tried to connect to car BT audio, or would simply not start up.
Flashed this yesterday.... and no crashes!
http://forum.xda-developers.com/showthread.php?t=2174100
For flash: Wiped dalvik/cache, flashed, fix permissions, reboot, start BT, deleted all devices, re-add.
No BT crashing of any sort for 36 hours now.
aaronchili said:
Was having bluetooth crashes for months using CM 10.1 on a T989 (no custom kernels)
Would crash anytime I tried to connect to car BT audio, or would simply not start up.
Flashed this yesterday.... and no crashes!
http://forum.xda-developers.com/showthread.php?t=2174100
For flash: Wiped dalvik/cache, flashed, fix permissions, reboot, start BT, deleted all devices, re-add.
No BT crashing of any sort for 36 hours now.
Click to expand...
Click to collapse
Hey thanks! I switched to JMT JB4 and it's not happening (much) now, I'll try to flash it and see if it fixes something :good:
Hi everyone,
I'm having serious problems with my Wi-Fi on my Samsung Galaxy Note 3 Neo (SM-N7505). Whenever I click the button to activate the Wi-Fi, the icon goes from grey to a dull green (darker than the bright green which signals that a function is turned on), as it does when it's trying to turn itself on. Problem is, instead of turning on, it just stays in that state for a few minutes before reverting to grey. This has gone on for a while, and I've already tried several possible solutions which I found after online searches. I don't think it's a hardware issue (see point 1 for the reason), and I really hope it isn't, because my warranty has been voided due to rooting, so I can't have my phone replaced or repaired unless I pay for it (which I can't at the moment). So, I'm basically ignoring the possibility of hardware failure and trying every possible software solution, hoping one of them will work, otherwise I'm just stuck with no Wi-Fi. These are the fixes I've tried:
1) Take out the battery while the phone is on, wait a few seconds, then put it back in and boot the phone up. This used to work when the problem first presented itself a few months ago (which is why I don't think it's a hardware issue), and I've been since using this method to fix it whenever it happened again. But a few days ago, this method stopped working for whatever reason, so I was back to square one.
2) I tried renaming the data/misc/wifi/wpa_supplicant.conf file, which seems to have worked for some people, but not for me.
3) I tried updating the version from Kitkat to the recent Lollipop, hoping that would fix it, but nope.
4) I tried deleting practically every single app one by one, hoping that one of them was interfering with the Wi-Fi somehow, but nope.
5) As a last resort, I tried a factory reset, but not even that worked.
This is basically the long and short of what I've tried to fix this... I might've skipped a few of the simpler fixes I tried (for example, I just remember I tried disabling "Smart Network Switch", which seemed to do it for some people), but the big stuff is all there.
I'd really like to get my Wi-Fi back, so if anyone could help me fix this thing I'd be really grateful!
Thanks in advance to anyone who will bother to reply.
same problem dude
Same problem...wifi and bluetooth not working...pls help us
Same Problem for me, Initally it works fine even after updating Official Lollipop update (OTA), but after few months now wifi & bluetooth are not working for me. And finally faced battery drain issue for past few days. Battery goes down upto 20% per hour even in idle condition. Then i rooted & installed Note Rom & even after i face the same problem. Is there any way to fix?
I'm having the following issues with my OnePlus 3 (stock recovery, no root):
15 November: last known date without any issues
16-18 November: when I played games I noticed that screen won't rotate even when auto rotate was ON
19 November: I wanted to click some pictures when the camera app just stopped working
Tried rebooting and clearing cache, but didn't work
Thought a software update might fix these problems
20-27 November: when I answered calls the screen won't turn off. That's when I realized that all the sensors on the phone had stopped working (no lift up display, motion sensors,etc). Read online that I could get the official Oreo update just by changing my VPN to Germany/Canada. So I did the same and upgraded to Oreo
Still the issues were there and battery drain was significant. The phone would reboot on its own.
On contacting OnePlus support they asked me to do a hard reset which seemed to work only for 3-4 days
28-29 November: the sensors stopped working again & again and I did a hard reset every time
In the end the phone switched off and the white notification light was on continuously. Pressing or holding the power button didn't work. Contacted support
2 December: through a remote session the OnePlus support installed Oreo again and on rebooting I got DM-VERITY error. So the support asked me to visit a Service Centre
3 December: I visited the SC where they concluded it was a hardware issue (motherboard: 17000/-) so I asked them to just roll back to OOS 4.5.1. Worked fine for 10-11 days
14 December: started rebooting randomly. Noticed that the phone would hang and reboot when using the camera (in WhatsApp, CamScanner and stock camera), maybe I'm wrong.
So now there's minimal usage of a phone with such high capabilities knowing that I'll have to do a hard reset once a week.
How can it be a hardware issue if the phone works fine for 4-5 days after a hard reset before breaking down again? What does that white notification light mean? Any help would be greatly appreciated
"3 December: I visited the SC where they concluded it was a hardware issue (motherboard: 17000/-) so I asked them to just roll back to OOS 4.5.1. Worked fine for 10-11 days"
There is your answer, there is a problem with you motherboard, you need to get it replaced, we cant diagnose a hardware problem here!
How come it works normally for a week or more if there's a problem with the motherboard?
And a hard reset seems to return the phone to its normal state.
Shmt_18 said:
How come it works normally for a week or more if there's a problem with the motherboard?
And a hard reset seems to return the phone to its normal state.
Click to expand...
Click to collapse
That just means that it is faulty and will fail after some time. This most likely means there is a bad memory sector on the board. As suggested. Get it replaced or you will keep having these issues.
Okay. Thanks for clarifying.
May I know what may be the causes for the motherboard damage? How common is it that a motherboard malfunctions?
Because there was no physical damage at all. Thanks again!
Shmt_18 said:
Okay. Thanks for clarifying.
May I know what may be the causes for the motherboard damage? How common is it that a motherboard malfunctions?
Because there was no physical damage at all. Thanks again!
Click to expand...
Click to collapse
See that is the thing. China has no real quality control standards. So it could just have been a bad board. If you look around you will see that a range of random issues seem to pop up over a short time. Yet some are just fine. Like mine. It had a faulty USB port from day one to the point that I knew it was gonna fail. (expected) So I am replacing it.