Hey, I permarooted and enabled s-off on my G2 about a week ago and so far only 2 things have happend: My phone shut off once when I hit the power button to turn the screen on. Sometimes when I hit the power button the screen wont turn on but the soft buttons will light up, this has been happening for a few weeks before I perma rooted and flashed baconbits. The other incident is last night when I went to watch a youtube video I noticed my volume was completely nonfunctional. I tried muting, unmuting, enabling silent mode, etc. but the only way I got my volume back was to restart my phone. The specific kernel version im using is 2.6.32.21-cyanogenmod.
It seems your issues are due to bugs in the cyanogen release.
You may look here to find out more:
http://forum.xda-developers.com/showthread.php?t=841275
As soon as I got home today my G2 crashed and wouldn't start back up until I removed the battery. Should I flash another kernel?
Related
Hey guys, i have some problems that i hope somebody can help with. My phone isnt rooted, basically out of the box stock, but ive had it since the day it came out. So shes got some time on her.
It was working perfectly till about a day ago. Then all of a sudden the screen would not stay off for more than a second. I would push the lock button and it would turn off, but the lighted buttons (home, back, etc) would stay lit. Then the screen would turn back on a second later. But i found that if i push the lock button and immediately push it again, the lighted buttons will also turn off and the screen will stay off. If i hold the lock button it will just flash the menu with the options to power off options (airplane mode, silent mode, etc..), but immediately disappear. But if i hold the lock button till just before that menu would pop up, it wont always disappear.
Also sometimes when i try to open any app it will close automatically, popping up with a recent apps menu that ive never actually seen before. I can push back and the menu will go away and i can try to open the app again. Usually successful the second time.
And last my battery life has gone down the drain. It went from fully charged to empty in about 7 hours. It used to last much longer. The screen might be on in my pocked, so that could be the problem, but i try to check it often to see if its on.
Just hoping that someone will know if this is a hardware or software problem. The phone was perfect in the morning, and a few hours later the problems started.
I have android version 2.2.1, froyo i believe.
Any help will be really appreciated. Sorry for the long post, just trying to be specific.
Hi guys.
So i managed to get my desire wet/damp and whilst it still works it has developed 3 issues:
1) The weirdest of all - the phone wont go into standby, as soon as you press the power button or let it timeout the screen goes off and they instantly turns back on to the lock screen. If i leave it, it will timeout again on lockscreen and come back on, it does this forever. I have done factory resets etc, all the same. Weird right
2) Volume keys do not work - think means i had issues getting into recovery. Finally found a widget to do it and then....
3) Trackpad does not work in recovery so i cannot re-flash or try any new rom to see if that fixed (1)
Proper catch 22
Any suggestions appreciated.
Thanks
Brisgstfer
UPDATE
OK I HAVE AN UPDATE:
The plot thickens but i have managed to S-OFF my Desire and eventually install Clockworkmod Touch which obviously doesn't require me to use the trackpad button so I was able to use Recovery. I wiped the phone and tried reflashing the ROM i had been using (Insertcoin) but this made no difference, the phone still keeps waking up immediately that it goes to sleep (either with power button or by sleeping timeout).
So i decided to install a completely different ROM (CM10_VJ_4.1.2_v3.0) and this installed fine. Now the phone will go to sleep and stay asleep if I press the power button. Problem solved I thought!
Now when the phone is asleep 50% of the time, trying to wake it with the power button will cause it to reset immediately and goto the white HTC screen. When it restarted it sits on the unlock screen and keeps timing out, screen goes off, then immediately on again - weird. If i unlock and lock with power button it will behave. For some reason the Search key will wake the phone every time no issues. Only the power key to unlock causes it to reset. Phone is sleeping according to Battery info.
Any other suggestions for what I could try. Could this possibly be something hardware related now? If there a way i can log the key presses or reason it wakes/resets?
Any help really appreciated, the phone is pretty unusable with this reset issue now.
THanks
Bridgstfer
bridgstfer said:
Any other suggestions for what I could try. Could this possibly be something hardware related now? If there a way i can log the key presses or reason it wakes/resets?
THanks
Bridgstfer
Click to expand...
Click to collapse
May be a hardware issue. But try installing a lighter ROM like dGB or MildWild and see if the issue persists.
Sent from my HTC Desire using xda app-developers app
dvsk69 said:
May be a hardware issue. But try installing a lighter ROM like dGB or MildWild and see if the issue persists.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
Thanks mate. So i tried this and installed CM7 today and have discovered something. As i said above the volume down button doesn't work and the volume up only works with some persuasion. Once i installed CM7 the problem where I lock phone with power key and it instantly wakes up now persists (on the JB rom it at least stayed asleep but reset if power button was pressed again).
However whe i changed the display timeout to 15seconds i watched as it timed out and instantly woke then noticed the volume would increment down one notch each it woke up again. This leads me to think that rather then the volume down not working at all it is actually stuck down permanently and could be causing the issue here. Is there any way I can find out if this is the case and disable the volume keys through software or do i need to open up the phone and disconnect it?
Thanks for any help - i think we are getting there!
Bridgstfer
bridgstfer said:
Thanks mate. So i tried this and installed CM7 today and have discovered something. As i said above the volume down button doesn't work and the volume up only works with some persuasion. Once i installed CM7 the problem where I lock phone with power key and it instantly wakes up now persists (on the JB rom it at least stayed asleep but reset if power button was pressed again).
However whe i changed the display timeout to 15seconds i watched as it timed out and instantly woke then noticed the volume would increment down one notch each it woke up again. This leads me to think that rather then the volume down not working at all it is actually stuck down permanently and could be causing the issue here. Is there any way I can find out if this is the case and disable the volume keys through software or do i need to open up the phone and disconnect it?
Thanks for any help - i think we are getting there!
Bridgstfer
Click to expand...
Click to collapse
Flash a ROM which can be unlocked via trackpad and volume can be adjusted from the phone settings without touching volume keys and the power button on the top.
I recommend MildWild5.8 based on CM7. When I was on it, I totally forgot about volume and power keys because all the phone operations can be done without them.
Thanks thats a great suggestion. I actually worked out that the trackpad is being pressed down constantly too because on CM7 when i disable trackpad to wake the phone actually stays asleep.
Is there any way to disable both volume and trackpad buttons at the kernal/system level?
Hi guys.
So i managed to get my desire wet/damp and whilst it still works it has developed 3 issues:
1) The weirdest of all - the phone wont go into standby, as soon as you press the power button or let it timeout the screen goes off and they instantly turns back on to the lock screen. If i leave it, it will timeout again on lockscreen and come back on, it does this forever. I have done factory resets etc, all the same. Weird right. As i result i would like to reflash the mod and see if that fixed it as assuming its software related (somehow).
2) Volume keys do not work - think means i had issues getting into recovery. Finally found a widget to do it and then....
3) Trackpad does not work in recovery so i cannot re-flash or try any new rom to see if that fixed (1)
Proper catch 22
Any suggestions appreciated.
Thanks
Bridgstfer
Install 4ext touch recovery.
Update after installing touch recovery
OK I HAVE AN UPDATE:
The plot thickens but i have managed to S-OFF my Desire and eventually install Clockworkmod Touch which obviously doesn't require me to use the trackpad button so I was able to use Recovery. I wiped the phone and tried reflashing the ROM i had been using (Insertcoin) but this made no difference, the phone still keeps waking up immediately that it goes to sleep (either with power button or by sleeping timeout).
So i decided to install a completely different ROM (CM10_VJ_4.1.2_v3.0) and this installed fine. Now the phone will go to sleep and stay asleep if I press the power button. Problem solved I thought!
Now when the phone is asleep 50% of the time, trying to wake it with the power button will cause it to reset immediately and goto the white HTC screen. When it restarted it sits on the unlock screen and keeps timing out, screen goes off, then immediately on again - weird. If i unlock and lock with power button it will behave. For some reason the Search key will wake the phone every time no issues. Only the power key to unlock causes it to reset. Phone is sleeping according to Battery info.
Any other suggestions for what I could try. Could this possibly be something hardware related now? If there a way i can log the key presses or reason it wakes/resets?
Any help really appreciated, the phone is pretty unusable with this reset issue now.
THanks
Bridgstfer
theres a few videos on youtube, if it was me i would take the phone apart and clean all round the buttons. mite solve it. But as it got wet, the water could of damaged something in around the trackpad r power button, hense always waking the phone.
Sent from my HTC Desire
Thanks mate. So i tried this and installed CM7 today and have discovered something. As i said above the volume down button doesn't work and the volume up only works with some persuasion. Once i installed CM7 the problem where I lock phone with power key and it instantly wakes up now persists (on the JB rom it at least stayed asleep but reset if power button was pressed again).
However whe i changed the display timeout to 15seconds i watched as it timed out and instantly woke then noticed the volume would increment down one notch each it woke up again. This leads me to think that rather then the volume down not working at all it is actually stuck down permanently and could be causing the issue here. Is there any way I can find out if this is the case and disable the volume keys through software or do i need to open up the phone and disconnect it?
Thanks for any help - i think we are getting there!
Bridgstfer
I actually worked out that the trackpad is being pressed down constantly too because on CM7 when i disable trackpad to wake the phone actually stays asleep. Stil the phone resets if i try to wake with power button though, must be something to do with the button combo being held down.
Is there any way to disable both volume and trackpad buttons at the kernal/system level?
Tried button remapper but does not allow to remap the trackpad press.
With a file explorer, go to
system>usr>keylayout and modify bravo-keypad.kl.
I'm just back from holiday where my Desire had a ten-minute swim in sea water!
Naturally it was stone dead when I remembered it was in my pocket as I waded across an inlet which was supposed to be ankle- deep but was over 1.5 metres in places
I thought there was no point in drying it out without first removing all salt so (minus battery and cards) held it under a tap for several minutes then left it to soak in tap water in the sink for 30 minutes.
I then dried it over gentle heat for a few days then tried the battery. The vibrator ran continually and the white LED flashed randomly but nothing else. After another two days drying it booted - but only into Fastboot and the vol switch didn't move the cursor. But after another two days - it worked almost perfectly! The vibrator is dead and the screen a bit streaky, but all the other sensors work just fine and it's quite useable.
I had been logging the hike using My Tracks and it actually shows the course going a short way into the sea.
do you have an assurance or warranty?
if yes-->change phone.
abaaaabbbb63 said:
With a file explorer, go to
system>usr>keylayout and modify bravo-keypad.kl.
Click to expand...
Click to collapse
Thanks for this. I actually got an app that let you remap the keys but it does not let you do anything to the trackpad click button (which is now the one stuck down). See photo of whats in my bravo-keypad.kl file here:
http://dl.dropbox.com/u/64089332/20130106_194659.jpg
Any other way i can disable the trackpad completely. Perhaps at the kernel level?
Thanks
ok so here is the rundown
Device: HTC one on vzw
Rom: Slimbean 2.x
Gapps: Slim AIO gapps
had a weird problem with the display today if anyone has had this or know someone who has i would greatly appreciate the help. I just flashed Slimbean 2.x last night and all was good. no problems what so ever, got everything setup and was working fine. this morning around 10am i opened snapchat to view a video. i clicked on the video and as soon as it started the screen went blank and would not turn on. i tried holding the power button down for at least a minute and nothing. also tried power and volume down, power and both volume buttons, power and volume up and still nothing seems to work. when i plug it into the wall charger the red LED light does not turn on and screen does not wake. when i plug it into the computer the computer does not ever read the device and noting pops up letting me browse the files on the phone. i have no clue why this happened it has been working fine for the 3 months that i've had it. took it to verizon about an hour ago and they didn't know either but they are sending me a replacement htc one. all i really want now are my photos that i have on the phone.
does anyone have any ideas about what i could do?
thanks
I had something similar and think it was conflict related. After installing the "advanced power menu" with xposed, I had an issue when trying to use it to boot into recovery. Basically it had timed out and then went away without rebooting. The next time I tried it locked up and my screen went black. My keys would light up if I clicked on the power button (it was dark in the room so the sensor was still working), but nothing else. Nothing I did would make the screen turn on at all and holding down the power key to reboot did not work. I just planned on letting the battery die out. After about 45 minutes, the phone just rebooted and everything was back to normal. I really think it locked up due to a conflict similar to what a PC might do.
My VS985 has 2 problems, which may be related to each other. The first is that, when the phone is fully turned off, turning it back on again is difficult. When I press the power button, the phone just vibrates at me and then refuses to turn on. Screen doesn't light up or anything. Pressing the power button again does nothing at that point. What I have to do, sometimes up to 7-8 times before it turns on, is remove the battery, wait a few seconds, put it back in, then press the power button again. It'll vibrate every time, and eventually one of those times it will turn on and boot up.
The second issue is that I've found it impossible to get into recovery mode using the buttons. I can get in just fine using the quick boot app, but that's not much use if I ever end up in a state where I can't boot into the OS. Apparently it's supposed to work by turning the phone off, then pressing and holding the power + volume down buttons and waiting for the LG logo to show up. I've tried this many times, it never works, possibly because of the first problem.
I bought this phone used, immediately used ODIN to downgrade it to the original stock OS, then towel rooted it and installed CM (LOS 14.1 now), so I've no idea if this phone has always had this problem or if I caused it. It's not a big deal since I always keep my phone on but makes trying new ROMs scary. Has anyone heard of this before, or have any idea how to fix it?