Related
After flashing some different roms, the phone just keeps resetting itself. At other times, it is unresponsive whereby, the phone will be on but the screen will be locked and cannot be awoken using the power button on the side
kelvster said:
After flashing some different roms, the phone just keeps resetting itself. At other times, it is unresponsive whereby, the phone will be on but the screen will be locked and cannot be awoken using the power button on the side
Click to expand...
Click to collapse
Have you tried a hard reset/master clear, by turning the phone on holding down the power button, volume up button and camera button?
Yes, tried master clear and a hard reset. When phone is on and just in standby mode when not being used, none of the buttons would wake it up to go to the slide to unlock screen. I have since put the official toshiba rom back onto it and have not had any problems for the last half an hour since doing so
kelvster said:
Yes, tried master clear and a hard reset. When phone is on and just in standby mode when not being used, none of the buttons would wake it up to go to the slide to unlock screen. I have since put the official toshiba rom back onto it and have not had any problems for the last half an hour since doing so
Click to expand...
Click to collapse
What rom were you using, you can report any bugs you found on the correct rom's thread
Was using arag0n85 rom to start with and then flashed on the ffboy rom with both roms having the same problem
kelvster said:
Was using arag0n85 rom to start with and then flashed on the ffboy rom with both roms having the same problem
Click to expand...
Click to collapse
I tried ffboy2009's 0.9 rom without many issues, and then tried Novembre5's release 1, both are good roms, i can't say i have had so much success with Novembre5's second, still it is early days, i am still using the release 1, so that comes recommended by me
Hello
My HD2 Worked well for a long time, but now everytime I press the "sleep" key it turns off for half a second then turns back on and proudly displays the lockscreen without me pressing anything. There is no way to turn the screen off and go in standby mode anymore.
Obviously the battery drains so much faster from not being able to have the screen off and this silly problem actually makes the phone unusable
I flashed a few roms using HardSPL and now HSPL2. I'm currently running Artemis 11.0, the problem appeared may days after flashing while using Artemis ROM 9.0. A hard reset seemed to fix it but the problem reappeared. Today flashing 11.0 only solved the problem at first boot.
Anyone had that before? Not sure if it's software/rom related or not anymore. HELP
As far as Ive seen, its only you an me who have had this problem so far.
Honestly, Im relieved to see someone else with this problem.
I had exactly as you described, but using Axlor roms.
It worked fine for 1/2months, then all of a suddon the screen backlight wouldnt go off, but a reset fixed it.
But it got worse and worse.
Now nothing will work...
Ive taken everything back to stock, and i mean EVERYTHING! Not a single app installed.
And I still have this problem. I've tried it all.
I think its a warrenty job....
EDIT:
I also noticed the backlight will go off fine when the phone is charging, is that the same for you?
I just sent the phone off to Tmob today, to see if they can fix/replace it.
I'll keep you informed.
Same problem. Was running fine on stock ROM 1.66 then backlight did not dim and would not go into standby. Put into standby, screen goes off then straight back on to the lock screen. Since then have had other problems at boot, sometimes it locks on HTC white screen needing battery removal, sometimes launches straight into Navipanel and will not exit, HTC sense homescreen sometimes launches in landscape and will not go into normal portrait mode. Reflashed with different ROM's same symptoms persist so have returned to Vodafone UK under warranty, fingers crossed.
i've had this on early versions of the rom i use, the chef fixed it, making me think its the software, not your phone.
I experienced this issue when I minimised a game called virtual pool. Closing it in task manager would then allow me to permanently make the phone sleep.
samsamuel said:
i've had this on early versions of the rom i use, the chef fixed it, making me think its the software, not your phone.
Click to expand...
Click to collapse
How come Ive still got the problem after reflashing several times and taking everything back to exactly as it came from the box?
flannco said:
Same problem. Was running fine on stock ROM 1.66 then backlight did not dim and would not go into standby. Put into standby, screen goes off then straight back on to the lock screen. Since then have had other problems at boot, sometimes it locks on HTC white screen needing battery removal, sometimes launches straight into Navipanel and will not exit, HTC sense homescreen sometimes launches in landscape and will not go into normal portrait mode. Reflashed with different ROM's same symptoms persist so have returned to Vodafone UK under warranty, fingers crossed.
Click to expand...
Click to collapse
I too have had the navi panel problem.
Im praying they fix mine under warrenty
Yes the problem is exactly what you describe, hard reset and flashing to a stock rom doesn t fix it with no programm running in the background
Navipanel seems to be on randomly sometimes so can I guess it could be related.
I found a fix, after starting the phone, plugging and unplugging the usb cable to the phone WHILE THE SCREEN IS ON fixes it but only until the next restart
Considering sending it for warranty now.
Thanks for replies! If anybody knows more let us know
Update re standby problem
Got my phone back from Vodafone UK today. Was advised software corrupted and that they had reflashed and it had been fully tested and was now working fine.
On power up (even without SD card or SIM) it had exactly the same fault as before, when put into sleep mode the screen comes back on after about 1 second.
I tried the plug in and remove USB lead fix and this also works for me until the next restart so it would seem that this must be a hardware problem.
flannco said:
Got my phone back from Vodafone UK today. Was advised software corrupted and that they had reflashed and it had been fully tested and was now working fine.
On power up (even without SD card or SIM) it had exactly the same fault as before, when put into sleep mode the screen comes back on after about 1 second.
I tried the plug in and remove USB lead fix and this also works for me until the next restart so it would seem that this must be a hardware problem.
Click to expand...
Click to collapse
I have a feeling mines going to come back from tmob in the same state i sent it in...
What other options do with have if they sent it back without fixing it?
any info? I still have not had mine back.
bump... any more infos on this?
CrocMonsieur said:
bump... any more infos on this?
Click to expand...
Click to collapse
Ive noticed allot more people getting this problem. So its not only us.
Tmob are replacing mine, so Im guessing its out of our control now.
did any of you guys try performing a task 29 in between flashing roms? it may help
Audio Oblivion said:
did any of you guys try performing a task 29 in between flashing roms? it may help
Click to expand...
Click to collapse
Actually no, I overlooked it.
Probably would have been a good idea
Prehaps thats worth a try Mr Opr
CrocMonsieur said:
I found a fix, after starting the phone, plugging and unplugging the usb cable to the phone WHILE THE SCREEN IS ON fixes it but only until the next restart
Click to expand...
Click to collapse
Thanks for this workaround. Now with the urgency gone hopefully somebody finds a lasting solution without the need of sending it in..
I have same problem guys after 4 months using. ...and my HD2 is unusable with no standby. I mean battery gets weak during 2-3 hours. Whats your guess guys is it software problem. Cause Im afraid of this is hardware prob because after reset goes my device in wrong state.
Help!
Sadly I'm running into this same error with my t-mobile hd2....getting serious power drain...can anyone confirm if the task 29 helped at all? Mine won't stay off for more than 30 seconds.
** Found out the google easy sms beta app I was running had a service which was causing the app to come out of standby...uninstalling this app cured the problem.
For me, it was a sd slot problem. When i removed the sd card, phone always waked up after 0.5 seconds, and card was detected as bad.
Now the SD slot was changed (under guarranty) and it work fine, no wake up if sd slot is empty.
Any update on this? My HD2 starting doing this today as well
And I have no usb cable at work to 'trick' it. The only option is to pull the battery which I don't want to do. This is ridiculous. Am I going to have to hard-reset the damn thing to fix it?
FYI I didn't do *ANYTHING* to my phone in a couple of weeks (no new apps, etc.) and it started doing this out of the blue.
You hit the red 'end call' button and it goes black..then comes right back on.
The odd thing is it *thinks* its plugged in because the only screen setting I can get it to acknoweldge is the 'backlight level when charging'. So somehow my phone thinks its plugged in even though my only usb cable is back home.
Grrr. No registry tweaks or temp files I can delete to reset this behavior?
Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)
Have you tried the new 6.1? I'm running it and it is very smooth. I had similar issues on the att version of Shostock. I can't say whether the full wipe or the new rom fixed my issue, but it is running smoothly now.
You could also try running Greenify.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
XGhozt said:
Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)
Click to expand...
Click to collapse
Not familiar with your rom but I know any rom I have tried where idle speed is set to 182 I find the occasional freeze then pushing too many buttons causes a reboot. The rom I am using now has the min set to 384 MHz and that seems to work very well, not one wake up issue or reboot. Depends if your kernel has a tweaker tool or not. Currently using googy-max kernel which comes with a tweaker.... you would need to research if it is compatible with your rom though..... this kernel set on battery profile gives me currently 1 day 20 hrs.... screen on time 2 hrs... battery left... 44% pretty good I'd say....
Gage_Hero said:
Not familiar with your rom but I know any rom I have tried where idle speed is set to 182 I find the occasional freeze then pushing too many buttons causes a reboot. The rom I am using now has the min set to 384 MHz and that seems to work very well, not one wake up issue or reboot. Depends if your kernel has a tweaker tool or not. Currently using googy-max kernel which comes with a tweaker.... you would need to research if it is compatible with your rom though..... this kernel set on battery profile gives me currently 1 day 20 hrs.... screen on time 2 hrs... battery left... 44% pretty good I'd say....
Click to expand...
Click to collapse
I don't think I can change the clock speed with my kernel. I will try that but I'm not sure that's the issue since the phone appears to be functioning even when the screen is stuck off. You might be on the something, if I press too many buttons that's usually how I can cause it to reboot/crash.
Try using cpu spy to see what the minimum clock setting is. Shostock 6.1 appears to be 384
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Red_81 said:
Try using cpu spy to see what the minimum clock setting is. Shostock 6.1 appears to be 384
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Yes, I am on v5.0 and it's set to 384. The issue might not be the clock speed.
This ROM doesn't have support for manually changing the clockspeed anyway.
Any other ideas?
I noticed we both had 32gb. Maybe the tolerances on the chip are not quite as good as the 16gb. I did play with cpu settings because waze would cause my phone to really heat up.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I have since changed to a different kernel and I have not had the issue yet (~13 hours running).
I can only assume this is a bug with the kernel until I have the issue again. My attempts to recreate it on the new kernel have failed.
XGhozt said:
Not sure how to describe this other than sometimes the phone just doesn't turn on.
It's very odd, and I can't always recreate it, but sometimes I can.
Occasionally, if I get a notification and the screen comes on then after 10 seconds it will time out and turn off automatically (this is normal). At this point, if I press the power button to turn the screen back on within 5 minutes of it turning off then it doesn't come back on. The back and menu buttons light up, and the volume works, I can even answer a call with the home key and the phone works. The screen just doesn't come on.
If I press the button 4 or 5 times in a row, it eventually wakes up. Sometimes, I have to hold the power button to cause the power menu to come up, that will sometimes wake up the screen. This makes me think there is some system process hanging causing the screen not to display until it unfreezes, but I can't tell what that is.
This happens to me at least once a day and I can't figure it out.
I'm on android 4.4.2 with SHOstock-i v5.0 with MDL baseband.
I did some research, there are threads where other people were talking about almost the exact same issue, but a different rom and a different phone. Does this mean it's a hardware failure issue or some specific setting/app causing it? This is driving me crazy.
What I have tried:
Reflashing the ROM
Flashing ROM with full wipe
Throttling CPU (since disabled)
Alternative Kernel (although no one else is complaining of this issue)
Uninstalling random apps to see if it goes away (hard for me to run without any apps)
Click to expand...
Click to collapse
I haven't experienced this with my GS4. But with my GS2 I had this problem and it seemed to happen with custom Kernels and with the min set to 182. I seen someone else mention this too .. The fact I haven't seen this yet is probably because I cant underclock being my bootloader is locked and I cant flash a custom kernel..Have you tried a different scheduler . It seemed to be worse on my gs2 when I had it set to NOOP. Hope you get this figured out because I know how frustrating it is to have as a problem..My Gs2 almost turned into a 70 mph fastball into a brick wall numerous times EDIT .. My fault I didn't see your post about it being set to 384 already
spirodave said:
I haven't experienced this with my GS4. But with my GS2 I had this problem and it seemed to happen with custom Kernels and with the min set to 182. I seen someone else mention this too .. The fact I haven't seen this yet is probably because I cant underclock being my bootloader is locked and I cant flash a custom kernel..Have you tried a different scheduler . It seemed to be worse on my gs2 when I had it set to NOOP. Hope you get this figured out because I know how frustrating it is to have as a problem..My Gs2 almost turned into a 70 mph fastball into a brick wall numerous times EDIT .. My fault I didn't see your post about it being set to 384 already
Click to expand...
Click to collapse
This might be related, but I'm not sure. The new kernel I'm on is actually set to 189Mhz - 1998Mhz and I have yet to have the issue happen again.
XGhozt said:
This might be related, but I'm not sure. The new kernel I'm on is actually set to 189Mhz - 1998Mhz and I have yet to have the issue happen again.
Click to expand...
Click to collapse
Right on .. Sounds like a kernel issue to me also ..I ran into the problem more often when I was playing music with the screen off .. Mind you that was on my tmobile gs2..It seemed to me that when any button was pressed to turn the screen on It was like it wasn't scaling through freqs enough to power on.. Hopefully your issue is resolved ... Now I know if I run into this issue in the future ill know its kernel related
I just wanted to follow up here. I noticed the issue happen again but this time it was right after I made a change. I'm using GO TaskManager EX and there is a setting in here to "Clear when turn on screen" and "Clear when turn off screen". When either of these are enabled then it causes the device to take an extra 15 seconds to wake and/or it doesn't wake at all.
Still not 100% sure if this was the original issue, but I thought I would post it in case anyone else is using this as well. Especially since it caused a similar behavior.
Major face-palm moment.
Hi everyone!
So I just had this problem after I woke up yesterday. I googled a lot but only found similiar problems.
Let me tell you what happened chronologically:
After turning the phone on in the morning it started updating apps as if I was doing a firmware update: "updating apps 1 of 135" etc. Note that my nexus was already running on 5.1.1 and had the latest updates installed.
Now it randomly freezes the screen on whatever screen it was before it happens and it won't respond to any touch input. This can also happen when not using the phone, then it will freeze at the lockscreen (the time freezes with it so sometimes i can see at what time it froze). Also, it loses connection with Wi-Fi as i'm using Whatsapp Desktop when i'm on my laptop and it mentions me that my phone is not connected.
The only thing that "fixes" (temporarily) it is a reboot. Now sometimes, on the lockscreen, i can just hold the power button and the pop-up comes in to turn the phone of, which i can somehow just tap on an it responds by turning the phone off. But sometimes (less frequent than the latter mentioned) the pop-up doesn't come in and holding the power button for a few secs will do the trick.
I hope I informed you all enough and my end question is: does any of you know what this is? How i can fix it or what i can do to prevent it or anything as I am hopeless. (my G3 is up for reparation so this is my sisters old phone, i had a nexus 4 myself for 2 years before the G3).
Thanks in advance!!
The best way to test it is by reformat the OS.
I positively think that it will solve the problem.
Since the phone is no longer under warranty, I guess there is no harm to install custom rom on it. They are fast and stable too.
Hope this help. Good luck.
Sent from my Nexus 4
EXACT thing happened to me too. Backup your data and hard reset from recovery. This fixed it for me
Same problem here bro, but neither custom roms or factory reset helps.... Is there anyone who has successfully solved the problem ?
multimedias said:
Same problem here bro, but neither custom roms or factory reset helps.... Is there anyone who has successfully solved the problem ?
Click to expand...
Click to collapse
Then it's time to change the screen or phone. Looks like it is a hardware issue.
Nitin
nitin.chobhe said:
Then it's time to change the screen ...
Nitin
Click to expand...
Click to collapse
I agree, your screen needs to be replaced.
I recently got faulty Xperia XA2 in my hands. Everything is brand new and works perfectly, except device shuts down after short period of inactivity.
On stock ROM it shuts down if the screen is turned off for ~10 seconds, or if I do not do anything with it for ~30 seconds, but it stays on if I run video in browser or use a music player.
I managed to flash TWRP and some custom ROMs. While in recovery, device always stays on, no matter if screen is locked or anything else happens, as it should be.
Now it has Lineage 17.1 installed and it shuts down just like on stock ROM.
Another thing to mention is that it doesn't exactly shuts down in those cases: after blackout, device restarts on short press on power button (it should only wake on long press if it is turned off conventionally) and blinks with green LED indicator.
And also, it doesn't turn off while charging
I would appreciate any help with figuring out what causes shutdowns and any ways to solve this. I have a few theories I cannot confirm, but I need more data.
MilesSeventh said:
I recently got faulty Xperia XA2 in my hands. Everything is brand new and works perfectly, except device shuts down after short period of inactivity.
On stock ROM it shuts down if the screen is turned off for ~10 seconds, or if I do not do anything with it for ~30 seconds, but it stays on if I run video in browser or use a music player.
I managed to flash TWRP and some custom ROMs. While in recovery, device always stays on, no matter if screen is locked or anything else happens, as it should be.
Now it has Lineage 17.1 installed and it shuts down just like on stock ROM.
Another thing to mention is that it doesn't exactly shuts down in those cases: after blackout, device restarts on short press on power button (it should only wake on long press if it is turned off conventionally) and blinks with green LED indicator.
I would appreciate any help with figuring out what causes shutdowns and any ways to solve this. I have a few theories I cannot confirm, but I need more data.
Click to expand...
Click to collapse
Change the phone ...
cojocar.andrei said:
Change the phone ...
Click to expand...
Click to collapse
Although I appreciate such straightforward solutions, sadly, it's not an option for me
MilesSeventh said:
Although I appreciate such straightforward solutions, sadly, it's not an option for me
Click to expand...
Click to collapse
From what you're describing probably this is the only solution if this happens with stock rom ...
Well, I sent it to service, actually. I tried to check logs via adb logcat, but there were no clues, they just stop going without any pattern. Then I gone lower and checked kernel logs, but they were clear, too, so I suggested it is related to power supply so I stopped and contacted repair service.
MilesSeventh said:
Well, I sent it to service, actually. I tried to check logs via adb logcat, but there were no clues, they just stop going without any pattern. Then I gone lower and checked kernel logs, but they were clear, too, so I suggested it is related to power supply so I stopped and contacted repair service.
Click to expand...
Click to collapse
If you don't mind, could you tell how the service has treated you?
aeolist said:
If you don't mind, could you tell how the service has treated you?
Click to expand...
Click to collapse
Well, they decided to change the mainboard (still in progress though, guys are working like morons). I think they would have it covered by warranty, if I had any.