Just read "purpose of this forum", and definitely questioning myself, so please feel free to delete or redirect as appropriate. This is mainly a question, but probably cross-device, (Sony)...
Ever since Omni 5.1, (unofficial), was built for Z1c, and now with all 4 MM ROMs I've tried, I've had an issue where the traditional 'power+volume up' force power-off doesn't work like it used to, (hold 3 seconds, get 3 vibrations, phone shuts down). Instead, I eventually discovered that I now have to hold the buttons for 8 seconds, and there's no vibration, but it does shut down, (others reported the same - http://forum.xda-developers.com/showpost.php?p=66376361&postcount=214). Once I figured it out, I didn't really think about it again, since, as long as I could shut down if I had to, I didn't care how, but just figured it was some kernel thing I didn't understand. I just became curious today about it, when someone else who's using the same AOSP MM ROM as me said that they don't have the problem, and the old-fashioned 3-second-with-vibration method works fine, (http://forum.xda-developers.com/showpost.php?p=66376361&postcount=214). So I just thought it would be good to put it out there and see what insight/experiences people are having with this, and figure out if it means anything dev-wise.
Note: old-fashioned-3-second-vibration still works normally if I use any >6.0 ROM besides Omni.
Related
Is anyone else having this problem? I'm using one of Sleuth255's ROMs -- and hoping I don't need to reinstall, but if nobody else is having this problem I guess I'll spend the afternoon and upgrade.
When I push the button, the phone turns on, but no backlight, it prompty turns back off. The second time I push it, there is the usual 2 second delay and on she comes like usual.
I've had this problem w/ many rom
I think i've got the same problem. I have over the past two days flashed many ROM to get the right fit.
But with all of them i'll have this problem. I didn't really think it was a ROM thing b/c i'm getting it w/ the official rOM's and cooked ROM's i think it's just part of the hardware..
please do let me know if u find something.
Hi guys/gals.
Got a bit of a problem, and not sure whether it's the actual phone at fault, or the software...
Had the phone for about 4 months now, and have noticed this to get worse and worse... I'm pretty sure it's happened before on the stock rom, but can't remember whether it happened before I unlocked the phone to be able to install custom roms (not security/sim unlock, just a standard unlock to allow custom roms).
Anyway, this is basically how my phone's life has been: I got phone, used standard htc rom. Then, the spl unlocker came out, and I installed that about 2 weeks after it came out (waited just to check people had no probs ). Then, I installed one of the energy roms as my first rom. Installed a few other roms in between, then an updated energy rom etc. Then, I installed the official wwe 6.5 rom. Then, I went back to the energy rom. Currently, I'm using the 26th October (iirc) rom. As I said, not sure whether it happened when I had the official 6.1 rom on (spl locked), but I'm quite sure it happened while I had the official 6.5 rom on (spl unlocked). It has happened tho with all different custom rom images I've used...
Basically, what I've noticed, is that sometimes I'm replying to a text message or email, click reply, pull out keyboard, and it seems to cause the phone to power off. Pressing the power button starts it again. Sometimes, I've not been doing anything, and it's turned itself off. Sometimes, I've dropped the phone (even only a slight drop of about 1cm), and it's caused it to power off.
I've also had times where it's turned itself off, and nothing's allowed it to come back on, other than taking the battery out the back of the phone and re-adding the battery. Then, pressing the power button powers the phone on.
Is this a problem with the roms, a problem with the spl unlocker, or a problem with my phone itself? Am I best contacting htc?
Any advice welcome, as it's very annoying coming to use the phone, and finding it's turned itself off, or when I go to reply, I open the keyboard, and then have to wait for it to load up and power it on to reply!!!
Many thanks in advance
Hi.
It's very anoying for you..
I suppose you should try to (re)install the latest Hard SPL, and to install the latest Radio too. After it, make a hard reset. Next, flash with your favorite ROM And come back here to say us what happens.
See you, and good luck for these manips.
lovelldr said:
Hi guys/gals.
Basically, what I've noticed, is that sometimes I'm replying to a text message or email, click reply, pull out keyboard, and it seems to cause the phone to power off. Pressing the power button starts it again. Sometimes, I've not been doing anything, and it's turned itself off. Sometimes, I've dropped the phone (even only a slight drop of about 1cm), and it's caused it to power off.
Click to expand...
Click to collapse
I've had this same trouble. It would happen to me when I would finish typing a text message and hit the send key and slide the keyboard close at the same time. I only really noticed it when I was running the energyroms, however I can not say for sure that they are the root cause of it, as I have waited till the message was sent before closing my keyboard ever since.
Well, since I wrote this message this morning, it's happened at least twice. Both times whilst the phone has been in my pocket...
I will try installing the latest hard spl. Think the radio I have is the latest already. Will also try a different ROM just in case it is energy roms which is causing it (but am pretty sure it happened with other roms).
Thanks for those suggestions, will let you know any outcomes
try Valkyrie. ^^
Well, I went through and installed the new hardspl (altho not sure if any different to the one I had, how would I tell?!). I then installed the image from josh, which had the latest radio and rphone.dll (or whatever the file is called) matched to it. However, doesn't appear to have made any difference. Still doing it...
Does anyone else suffer much with it, and it's just a design fault? Or should I contact htc? As surely it should just turn off when in your pocket?!
No-one else? I'm just the only person. Guess I best drop htc an email then...
my att Rhodium /tilt2 does it too
Ive been dealing with this for awhile now also.... , also return my phone for new one but this one does the same thing my radio is 4.47.25.24 and i have 1.6beta rom by josh build 21882.5.073 .
Hello!
Lately I've had this problem at three or four different, seemingly random times. The Vol Down button seems to activate all by itself and is being "kept" pressed down. I can raise the volume by pressing Vol Up but the moment I let it go it goes down to mute again very fast (I can see the volume slider when this happens). As a result I can't use the Power button and all I can do is either wait a bit and hope it goes away or use a program (say, xposed installer) to reboot the phone. The problem may persist after reboot, though if I manage to turn the phone off and then back on it seems to go away.
It has happened too few times to do conclusive testing, but that's all the data I have... My M8 (Int'l, rooted) is running Android Revolution. Do you guys think this might be a software or a hardware issue?
Thanks for listening...
You should try a different custom rom just in case if it is a software issue. If it happens again after that, it's a possible hardware issue. Do you have any cases on it?
No case - sometimes I use the included plastic one but this happened only when the phone was naked.
Worth saying the device is in perfect shape, has had a couple of very minor and soft (on my leg) drops but that's all.
I'll try a clean install and also another ROM - an ask in the ROM's thread if anyone else has had the symptom, though I did search before posting here and found nothing...
Thanks for your input!
Just an update; it must have been a hardware issue after all.
One day that the problem was very apparent, I knocked it lightly on its side on a piece of soft wood, and haven't had the problem ever since. Whether it was a piece of dust on the contact or the rocker itself was stuck or dislodged somehow, this seems to have fixed it and haven't had the issue again in several days now...
Hey there guys , I've been searching through the forum topics about my issue but so far I've found nothing close to my scenario.
A few months ago I bought my first HTC phone (M8). Its a great device for sure , despite the fact that I had to return it back twice.
First time it was a faulty microphone , so they sent me back a brand new device. Great isn't it ?
However recently I've noticed a few .... let me call them 'glitches' .
Let me give you some details on what I've experienced with the device:
Despite the issues that i'm going through ... the phone works great, but...
Sometimes the screen wont turn on when I'm receiving incoming calls (same goes for the alarm clock) but the phone is able to recognize touches - i've managed to pick up the call when I swiped the screen in the area where the "green" answer button appears .
The above issue doesnt happen so often but the thing that bothers me is the unlocking issue.
At first I thought that it was stuck or faulty power button.
When the phone is idle for some time and I pick it up and press the unlock button ... nothing seems to happen I've tried pressing it hard ... i've tried pressing it gently ... i've tried pressing it multiple times until the screen wakes up .
Same goes for motion launch unlocking .
When I use motion launch to unlock it the phone only gives me a vibration feedback ... and thats it until I try harder to bring the screen back to ''life'' .
(I can also press my security pattern buttons while the screen is dead and feel the phone vibrating , BUT NOT ALWAYS , sometimes is just .. dead )
I already sent the phone back describing the same problems and they just flashed the firmware , which did not fix any of the issues.
Stock Rom android 5.0.1 , not rooted
Soo what do you guys think? What can I do next .. is it android bug or a faulty unit ?
is it possible to be a sensor problem (proximity , accelerometer)
Already tried factory reset and dalvik cache wipe.
Any advice would be useful.
Thanks for taking your time .
Cheerz
I have the same issue. There are times it takes me hitting the power button 20 times for it to finally light up but I can press buttons with it black. The weird thing is it does it on every single ROM but I havent noticed it on Stock...maybe I'm not using stock enough to see. I'll probably throw stock on there today and take it into sprint and let them replace it.
I have the same problem whether it's on stock or custom ROM (KK or L). I am pretty sure this is a hardware problem. Unfortunately, my m8 is out of warranty so HTC won't fix it for free. I read it some where that it could be a faulty proximity switch so shining a light beam to the top part of the phone may wake up the screen. I haven't tried it yet because every time it happens, I don't have a flash light handy. It is an annoying problem to say the least.
When this happens, I pushed the power button, the volume up button, and swiping the screens. Eventually the screen would wake up and every thing works fine... until the next time.
Its a ****ing pain in the ass.
however none of the sensor reading apps report a faulty/stuck sensor.
the wors thing... I've already sent my phone for repair, describing the problems in details. .. and it took them a whole f*cking month to bring it back to me with no results.
I don't think they will replace it because its a problem that takes time to be experienced...and no one is going to wait for it to happen. ...
Any other ideas?
Should I wait for android 6.0 or should I try a custom rom too see if these problems presist.
Fml I love the phone but this is frustrating.
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Ozger said:
I have the same problem I think. I just bought an M8 on Ebay. I am S-off, unlocked and rooted, using the Viper Rom currently. I have also tried AICP, the stock Tmobile Rom and a few others. Same issue.
If I double tap, I feel the screen vibrate, but nothing comes on. Then, I keep pushing power button a few times. Sometimes it comes on and sometimes I am too impatient to wait, so I just hold power and volume up.
I also know that the phone internals come on, because after that vibration, I swipe up and push the screen a few times. Then, when I am fiddling with the power button and it does come on, I do see that there is an app already on the screen.
I think this is a rare issue, as I haven't even been able to find many posts regarding this. I may have to get a new one if this keeps going on so bad.
Click to expand...
Click to collapse
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Soulink said:
I am experiencing the exact same issue with my M8. I have seen a lot of people stating it may be a hardware fault related to heat and internals but something about how it reacts seems software related.
I really hope someone who has fixed or uncovered the reason comes forward. At this rate I may be switching back to a S4 LTE-A.
Click to expand...
Click to collapse
I think it IS hardware related. I was able to return that one and got another M8. No problems at all.
Hi,
some weeks, maybe even 2 or 3 months ago, I tried to root my Z1C because I wanted to be able to use tcpdump. I didn't want to use KingRoot because of some warnings I had read about it, so I decided to flash a new image onto the device. I could kick myself for doing this in quite a busy time but I somehow hurried through it.
After that I rebooted the device and it didn't come back. The only thing I saw after booting was the Sony logo which just stayed forever. Even worse, I recognized I wasn't able to turn it off anymore by holding the power key!
Having done that for my job (app developer) and needing a device for testing I bought another phone for about 100 €, and thought of the Sony as a permanent loss. Because there was much stress in my job at that time I didn't immediately try to fix this, but now, after some time has passed, I wonder if I can do anything to resurrect the device. If not, I won't need to bother anymore. The situation right now is unsatisfying, I have it lying around because there might still be hope, on the other hand, I have no clue what to try.
I can only turn it off by draining the battery, which is relatively easy. The screen stays on all the time showing the Sony logo, and the battery drain is high in this mode. I'm not really able to press any buttons on boot because I only have one try at the exact moment the device starts up after leaving it connected to the charger for some time. After that, I have to drain the battery again to reboot it.
This might be a question of the perfect timing, but I'm not sure. For me, the fact that the power button doesn't turn it off sounds like it has been hard bricked by installing a kernel that didn't match. In this case, holding any of the other buttons at boot time won't do anything, too. Unfortunately, I can't remember what thread I followed, so I can't tell for sure if it was a kernel mismatch... Any ideas? Or should I just dump it and forget about it?
Thanks in advance for any advice
Oliver
olik79 said:
Hi,
some weeks, maybe even 2 or 3 months ago, I tried to root my Z1C because I wanted to be able to use tcpdump. I didn't want to use KingRoot because of some warnings I had read about it, so I decided to flash a new image onto the device. I could kick myself for doing this in quite a busy time but I somehow hurried through it.
After that I rebooted the device and it didn't come back. The only thing I saw after booting was the Sony logo which just stayed forever. Even worse, I recognized I wasn't able to turn it off anymore by holding the power key!
Having done that for my job (app developer) and needing a device for testing I bought another phone for about 100 €, and thought of the Sony as a permanent loss. Because there was much stress in my job at that time I didn't immediately try to fix this, but now, after some time has passed, I wonder if I can do anything to resurrect the device. If not, I won't need to bother anymore. The situation right now is unsatisfying, I have it lying around because there might still be hope, on the other hand, I have no clue what to try.
I can only turn it off by draining the battery, which is relatively easy. The screen stays on all the time showing the Sony logo, and the battery drain is high in this mode. I'm not really able to press any buttons on boot because I only have one try at the exact moment the device starts up after leaving it connected to the charger for some time. After that, I have to drain the battery again to reboot it.
This might be a question of the perfect timing, but I'm not sure. For me, the fact that the power button doesn't turn it off sounds like it has been hard bricked by installing a kernel that didn't match. In this case, holding any of the other buttons at boot time won't do anything, too. Unfortunately, I can't remember what thread I followed, so I can't tell for sure if it was a kernel mismatch... Any ideas? Or should I just dump it and forget about it?
Thanks in advance for any advice
Oliver
Click to expand...
Click to collapse
It used to be that holding vol up and power for 2 or 3 seconds would power off. I'm not sure why, but with certain AOSP toms starting with LP 5.1, you would have to hold the buttons for 8 - 10 seconds, then it would power off, and without the usual 3 vibrations. Try that out. I would be surprised if it was really hard-bricked just from a bad flash. Try fastboot with a custom kernel and recovery IMG, and see if you can get into recovery.
levone1 said:
It used to be that holding vol up and power for 2 or 3 seconds would power off. I'm not sure why, but with certain AOSP toms starting with LP 5.1, you would have to hold the buttons for 8 - 10 seconds, then it would power off, and without the usual 3 vibrations. Try that out. I would be surprised if it was really hard-bricked just from a bad flash. Try fastboot with a custom kernel and recovery IMG, and see if you can get into recovery.
Click to expand...
Click to collapse
Thank you SO much! I wasn't really able to boot using power and volume up, BUT after your encouraging words and the idea that I might just be using wrong keys, I researched some more and found out about this little red button within the sim card slot! It allowed me to reboot, get into fastboot, install recovery and cyanogenmod afterwards! I'm happy again