Related
I have an AT&T unlocked Nexus One that I recently flashed to CM-7.0.3-N1 . I have had a problem unlocking the device with the power button both when I was running stock Gingerbread and now that I have installed CM7.
When the screen is off and my N1 is in standby, I push the power button and the screen turns on and then back off almost immediately. Sometimes there is a half second delay before the screen turns on and then off. This usually goes on 2 or 3 times until the screen will stay on and I can unlock my phone.
Has anyone seen or heard of this problem, and maybe knows of a fix? It could be hardware related, but the button definitely sends a signal to the phone and it works fine to shutdown or turn on the device from completely off. Thanks.
ummm the power button on the nexus one has an incredibly high failure rate, all over the forum here. its a design defect from the factory. that's why it has always been recommended to root the device immediately, and use trackball wake, so you avoid using the power button as much as possible. you have to send the device to HTC for repair, that's your only option...
Thanks for the information. I will have to look into repairs.
You are already running a rooted rom with track all wake. Use it. To reboot the the phone use quickboot. At this stage you really don't need the power button on your phone.
pcflet01 said:
... now that I have installed CM7.
I push the power button and the screen turns on and then back off almost immediate
Click to expand...
Click to collapse
This is a problem with CM7. Most advise turning off the screen off animation if it becomes a big problem for you. Make sure you are using the newest nightly and hope for a fix. I don't know if the RC's have this problem, but I would bet it appears on the 7.0.3 release.
At first glance that seems to have helped. Thanks for the advice!
No problem.
Also you can use widget locker to lock the screen then the trackball to wake, with that and quickboot I don't even touch my power button anymore. Although your problem doesn't sound like a broken power button so in your position I would switch ROMs and see what happens.
pcflet01 said:
I have an AT&T unlocked Nexus One that I recently flashed to CM-7.0.3-N1 . I have had a problem unlocking the device with the power button both when I was running stock Gingerbread and now that I have installed CM7.
When the screen is off and my N1 is in standby, I push the power button and the screen turns on and then back off almost immediately. Sometimes there is a half second delay before the screen turns on and then off. This usually goes on 2 or 3 times until the screen will stay on and I can unlock my phone.
Has anyone seen or heard of this problem, and maybe knows of a fix? It could be hardware related, but the button definitely sends a signal to the phone and it works fine to shutdown or turn on the device from completely off. Thanks.
Click to expand...
Click to collapse
I'm experiencing exactly this too on the latest RC. It doesn't seem to be complete button failure but it's acting like I've pressed it twice sometimes. Disabling the screen-on animation does seem to prevent it from popping back on. But it still sometimes goes on-then-off when I wake it with the power button. So now I'm using trackball wake too.
As others have mentioned, this does not sound like a powerbutton issue, because the powerbutton still turns on the screen. The problem is that the screen turns off immediately after it turns on.
When you flashed 7.0.3, did you come from a previous CM verison? From stock? My first suggestion would probably be to wipe the /system partition (in CWM, it is under mounts and storage -- with Amon_RA, you need to find a flashable zip to do it) and reinstall CM and gapps. This will not cause any data loss. Sometimes, if you install a new ROM over an old one, the upgrade script in CM can get confused and carry over files that aren't supposed to be carried over. The system wipe fixes that.
I've been using this RC since it came out in late June. Only this week did it start flipping out on me.
Sent from my Nook Color!
It still can't hurt anything to do a system wipe, just in case something got screwed up (these things can be so temperamental at times). And, like I said, you won't lose any of your data.
bassmadrigal said:
It still can't hurt anything to do a system wipe, just in case something got screwed up (these things can be so temperamental at times). And, like I said, you won't lose any of your data.
Click to expand...
Click to collapse
I'm currently using S2E for apps2ext and some data2ext. How would a system wipe and reinstall interact with that? I'm a bit nervous on that front.
A system wipe shouldn't change any of that. It is one benefit of using S2E as it is a standard app that is stored in the /data partition without any changes to the /system partition.
Anyway, to be safe, it is a good idea to do a nandroid backup anytime you are doing something that involves the majority of the features in recovery.
It's a hardware problem for me. Failed completely as of today.
Sent from my Nexus One using Tapatalk
CM7 7.1.0
My power button seems to be in the process of completely failing. The new CM7 update to 7.1.0 has made it possible for me to lock the screen without using the power button using the "Notification power widget" -> "Go to sleep". Now the only times I have to use the power button are to shut the phone down or wake it up, which seems to be easier when the phone is plugged in to a wall charger. Are there any simple apps for shutting the phone down and maybe waking it up at a set time?
The only reliable trick I found to turn it back on was to plug into the wall and take the battery out/in a few times till it vibrated.
I ended up getting a replacement phone and then I sent the Nexus to HTC. They quoted a $55 repair cost off warranty which my credit card insurance would've covered, but when I asked for an invoice they offered to just waive the charges. Finally over a month later it came back fixed.
The app Easy Reboot can shut the phone down.
Sent from my Nook Color!
I also use an app called Lock Screen, which just locks the screen. I have it stored in my dock, because I don't like the space being used in the notification widget.
CM7 has an option for one of the items in the notification tray widget to be a lock screen button.
cmstlist said:
I'm experiencing exactly this too on the latest RC. It doesn't seem to be complete button failure but it's acting like I've pressed it twice sometimes. Disabling the screen-on animation does seem to prevent it from popping back on. But it still sometimes goes on-then-off when I wake it with the power button. So now I'm using trackball wake too.
Click to expand...
Click to collapse
THANK YOU!!!! This has been driving me crazy. Turning off the screen-off animations did nothing, but turning off the screen-on animation seems to have fixed the issue. My power button is toast (my new power button ribbon cable just arrived... time for surgery), and I've been using the trackball to wake my phone. Before the power button died, it did the same thing. I'm using CM7.2. I installed it after rooting and went straight to cm7.2 from stock, so obviously the cyanogemnod crew haven't fixed the issue since 7.0.3 when this thread started.
I rooted my phone with a stock rooted Rom last week, and have just yesterday flashed [AbyssNote][v4.2 Final] to my device.
Because it comes with CWM recovery on it, and it seems the best option for safe restoring etc...
(as i am not able to post a reply to the direct thread of the AbyssNote][v4.2 Final] post)
However my problem is this ...
... when I press power+volume up+home i get the CWM screen showing the version and the options, however i cant press any buttons. Nothing happens except the screen blinks and shows the same screen.
When i press volume down to select a different option, the highlight bar moves, but then the screen blinks black, and comes back up with the initial CWM screen. Any button is the same. Home button doesn't select the option it also makes the screen go black, then the CWM screen flashes back up.
I tried flashing the Kernel again, but same problem.
Another problem is that if i game for an hour the temperature gets to 45 degrees and the device freezes... I can underclock it and that helps but temps still get quite high..
If nothing can be done to solve these issues, can someone recommend a different Kernel to flash?
hamdogg said:
I rooted my phone with a stock rooted Rom last week, and have just yesterday flashed [AbyssNote][v4.2 Final] to my device.
Because it comes with CWM recovery on it, and it seems the best option for safe restoring etc...
(as i am not able to post a reply to the direct thread of the AbyssNote][v4.2 Final] post)
However my problem is this ...
... when I press power+volume up+home i get the CWM screen showing the version and the options, however i cant press any buttons. Nothing happens except the screen blinks and shows the same screen.
When i press volume down to select a different option, the highlight bar moves, but then the screen blinks black, and comes back up with the initial CWM screen. Any button is the same. Home button doesn't select the option it also makes the screen go black, then the CWM screen flashes back up.
I tried flashing the Kernel again, but same problem.
Another problem is that if i game for an hour the temperature gets to 45 degrees and the device freezes... I can underclock it and that helps but temps still get quite high..
If nothing can be done to solve these issues, can someone recommend a different Kernel to flash?
Click to expand...
Click to collapse
Abyss 4.2 kernel has touch recovery. Pressing buttons wont help. You have to touch the buttons given on the screen bottom. Back arrow , Up, Down and enter/select.
The touch button calibration are little off meaning if you touch directly over the enter/select key it still takes the command of down....so touch a little towards the right side of enter key and it will work the function as desired.
Hope this helps!
Thanks...
Well... that made me feel like a dork!
Thanks for the reply. It certainly solved my CWM issue. Making a backup now...
- Is the temperature supposed to get high on this Kernel? I keep putting it in the fridge just before i charge it, as i dont want anything above 38 degrees/ 100 degrees FH
hamdogg said:
Well... that made me feel like a dork!
Thanks for the reply. It certainly solved my CWM issue. Making a backup now...
- Is the temperature supposed to get high on this Kernel? I keep putting it in the fridge just before i charge it, as i dont want anything above 38 degrees/ 100 degrees FH
Click to expand...
Click to collapse
No problem mate!! Everyone is learning here
Also this is generic with Note. While charging or while playing games or while watching some movie the note will get heated. Nothing can be done apart from not doing the said activities. but mine doesn't freeze up as you stated. And also i would say don't keep in fridge......might do more harm then doing good. Let it cool by itself. Heating and rapidly cooling might crack open some connections and then you will have to run for the service center!!
Different Kernel??
Phone froze again a few mins ago, and kept freezing immediately after 20 seconds of booting. Left phone as the back felt real hot! After 10 mins booted fine, but was 32 degrees.
I think im going to have to go to a different kernel. Any recommendations?
I want to overclock to 1700mhz (ish) so... anything that could do that and is stable?
Thanks man.
** Edit: My radio(modem) keeps turning itself off also. Get a crossed out circle where the signal should be. I really need to change the Kernel. What should i go to? and if you could provide a link would love it!
Have you overclocked your Note? i think you have and you have "Set on boot" ticked in setCPU.
if you have ... then i hope you have made some "Profiles" like "during Charging" and "Screen off"
if yes then
Connect your note to the charger and open setCPU and reset the clock back to 1.4ghz .
Thanks for the reply.
Yes I am over clocking. Cranked it down to 1664mhz and is fine for normal day use. Gaming it crashes, so I'm guessing its too hot.
I have it set on boot, 'lagfree' and have two profiles with a max mhz of 500. ('charging' and 'temp>' with a warning at 38 degrees C)
When i run a stability test it is fine. When i run a benchmark it freezes every time.
Ideas?
Crank it down to 1500mhz? might as well not overclock at all if thats the case
Just crashed again when i was using it, and temp. was only 22 degrees. With a max cpu of 1400mhz.... Interesting.
Yeah keep playing with the figures till you find the sweet spot.
I purchased a NEXUS 6 six months ago and since the 5.1 update and have a problem with volume bar , namely: the bar volume goes in to vibrate mode without doing anything and so remains , trying to lift up to a certain volume control level bar all at that point remains . If you had gender issues .... how to solve? I
Thank you
comunicator2009 said:
I purchased a NEXUS 6 six months ago and since the 5.1 update and have a problem with volume bar , namely: the bar volume goes in to vibrate mode without doing anything and so remains , trying to lift up to a certain volume control level bar all at that point remains . If you had gender issues .... how to solve? I
Thank you
Click to expand...
Click to collapse
Check this thread:
http://forum.xda-developers.com/showthread.php?t=2965410
I'm not 100% clear on your question but my best guess was that you're dealing with the volume rocker sticking. ???
That's why I linked you to the other thread with a, albeit a bit silly, simple solution.
As for gender issues, that's a bit out of my area of expertise.
You see in the screen shot: I can`t move the bar to raise the volume. I have to reset my phone
comunicator2009 said:
You see in the screen shot: I can`t move the bar to raise the volume. I have to reset my phone
Click to expand...
Click to collapse
The volume buttons on the side of the phone do not work?
yes they work. i think is a bug
Evolution_Freak said:
The volume buttons on the side of the phone do not work?
Click to expand...
Click to collapse
comunicator2009 said:
yes they work. i think is a bug
Click to expand...
Click to collapse
I'm sorry for my confusion, which is why I'm asking so many questions. So, if you raise the volume, with the volume keys, the volume lowers again without touching the buttons? Are you keeping the phone in your pocket? Or does it lower again immediately after raising it?
it dosen`t move at all with my finger and the side buttons. i have to restart the device for the volume to work. not all the time, like 5 or six time a day . I will make a video and post here
comunicator2009 said:
it dosen`t move at all with my finger and the side buttons. i have to restart the device for the volume to work. not all the time, like 5 or six time a day . I will make a video and post here
Click to expand...
Click to collapse
How did you get the 5.1 update? OTA, sideload or factory image? I would suggest backing up your data, unlocking the bootloader, and flashing the factory image. If the problem persists after flashing the factory image, then it's probably a hardware issue. At that point, you could return for warranty service.
I had the same issue yesterday with my new one day old nexus 6 that was updated to 5.1 with OTA. The volume slider is stuck and will not move. I know the volume rockers work as if I push vol up or down the on screen volume slider appears...it just doesn't move. A quick reboot of the phone fixed it for me and I haven't seen it since. But please note I literally only had this phone for less than 24hours
i get the update from google official. can you be more specific what shall I do?
thanks
comunicator2009 said:
i get the update from google official. can you be more specific what shall I do?
thanks
Click to expand...
Click to collapse
Based on the other user that commented, I'd say this is a bug. You can flash a factory image, which will probably fix it.
I think is a bug in the android with this volume bar. Mine to, I have to reboot the device but still
comunicator2009 said:
I think is a bug in the android with this volume bar. Mine to, I have to reboot the device but still
Click to expand...
Click to collapse
Flash system.img and userdata.img (or data factory reset in recovery) in fastboot and reboot, that should fix it. If not, then its a hardware issue.
Hi everyone I've got a big problem with my wife's Mi 5. After some minutes/hours of usage the touchscreen stops working and the only solution the make it work again is to reboot the phone (by keeping the power off button pressed).
I've tried some rom (MIUI stable, MIUI dev, Paranoid Android 7.3.0) but all of them have the same problem, someone has got the same issue?
I think it's not only an hardware problem because the touchscreen works most of the time... Any ideas?
I'm having the exact same problem with my wife's Mi5 too. I thought she was talking rubbish until I started using the phone full time over the past few weeks.
Symptoms:
Screen switches on and accepts one touch event.
Screen is then unresponsive to touch events.
All other buttons (home, power, volume) all work OK.
All functions work OK (calling, SMS, etc) via remote control (MyPhoneExplorer)
Screen then becomes responsive again after reboot
Tried so far:
Clearing dalvik/cache
Clean flash - using MiFlash and China dev ROM
Opened phone, cleaned all ZIF connections and reconnected.
It almost feels like something in the touch firmware or driver crashes and does not reconnect - as the phone is clearly usable save for the touch panel.
I'm going to ask Bruno/bgcngm and see if there's anything I can do to try and diagnose the issue.
kylemd said:
I'm having the exact same problem with my wife's Mi5 too. I thought she was talking rubbish until I started using the phone full time over the past few weeks.
Symptoms:
Screen switches on and accepts one touch event.
Screen is then unresponsive to touch events.
All other buttons (home, power, volume) all work OK.
All functions work OK (calling, SMS, etc) via remote control (MyPhoneExplorer)
Screen then becomes responsive again after reboot
Click to expand...
Click to collapse
In my case unresponsive screen to touch events, all phisical button works and the only option to make it works again is to reboot. I didn't try to use it with some "remote" control.
kylemd said:
Tried so far:
Clearing dalvik/cache
Clean flash - using MiFlash and China dev ROM
Opened phone, cleaned all ZIF connections and reconnected.
Click to expand...
Click to collapse
I didn't try to open the phone, but I installed all roms with TWRP and format data/wipe cache/dalvik before.
kylemd said:
It almost feels like something in the touch firmware or driver crashes and does not reconnect - as the phone is clearly usable save for the touch panel.
Click to expand...
Click to collapse
I also think that it's related with a software issue...
kylemd said:
I'm going to ask Bruno/bgcngm and see if there's anything I can do to try and diagnose the issue.
Click to expand...
Click to collapse
I don't know who is Bruno/bgcngm but I hope he/she'll find a solution.
If you need some other information or help I'll give you as much as I can.
Well on my old mi4c i had similar problem. I mean sometimes when i pressed power button and tried to unlock it screen didn't work. For me solution was simply to press power button again to turn off screen and then turn IT on. Maybe this will help u. Have u try that ?
Wysłane z mojego MI 5 przy użyciu Tapatalka
kylemd said:
It almost feels like something in the touch firmware or driver crashes and does not reconnect - as the phone is clearly usable save for the touch panel.
Click to expand...
Click to collapse
Do you think it's something related with Doze or standby? I think so because today (and yesterday and so on...) I wasn't able to turn off the wake up alarm (the phone was in standby with the screen off all night) with "the screen" but I have to force restart the phone with the button... and it's very annoying.
Maybe we can try with some Marshmallow ROM instead Nougat one.
Alberto
uremytoy said:
I mean sometimes when i pressed power button and tried to unlock it screen didn't work. For me solution was simply to press power button again to turn off screen and then turn IT on. Maybe this will help u. Have u try that ?
Click to expand...
Click to collapse
Yes I tried it, it's the first test that I did... but It doesn't work. I tried also to double tap home button and power button but nothing happend.
Alberto
I'm facing same issue.I've changed my display panels but it doesn't solve my problem.it is quite painfull.i don't know what should i do.
any update sir?
My MI 5 has a different issue. There is no response if I place the phone on the table, but it is fine if I held it. It seems the touch panel is only responsive when the sort of sensors that a human is holding the phone. I have no idea why it starts to happen in these weeks. This symptom happens even in TWRP, so I don't think it is related some particular ROM. Tried firmware 7.7.6 ~ 7.9.22 with no luck.
skip lock screen
Hi
I know I am late to the party, but just faced the same issue yesterday. To bypass the issue, follow the following steps
1. Restart your phone .
2. Enable developer options from about section in settings. (google enable developer options for specifics)
3. In developer options, there is an option to skip screen lock. Enable that.
4. Voila!!
Hope it will help other mi5 users..
Hi,
I had the same problem. I found this video and I tried to fix it. It worked pretty well. Bye
In a situation that I can't do any service for my Mi5 as of now - is this really loose cable thing ?
Can more folks confirm that this cable solution from above video works ?
exactly same symtoms :
Random screen freeze - only option is to reboot phone or phone goes rebooting randomly itself.
Hi all,
Now I am facing an annoying issue, the phone usually does not wake up after pressing the power button, however, the phone still active while the screen is black (i.e. long press on the power button makes a vibration because of the power menu which should be appeared, when I press volume buttons I hear the volume change sound ... etc.). It may wake up after a while, and sometimes I have to restart the phone in order to make a call, for instance.
After months of using Neo's Resurrection Remix, which was working smoothly until a week ago, I have installed Lineage 15.1 yesterday freshly, and still facing this issue. Moreover, I don't use any kind of screen protectors or covers.
Anyone have faced it before? Should I try a custom kernal? Or go back to the stock ROM? Or it is a hardware issue (I wish it is not :crying?
Thanks in advance guys,
Regards.
Loose internal cable, I think? Yep, probably hardware issue. Did you drop it recently?
Lite2012 said:
Hi all,
Now I am facing an annoying issue, the phone usually does not wake up after pressing the power button, however, the phone still active while the screen is black (i.e. long press on the power button makes a vibration because of the power menu which should be appeared, when I press volume buttons I hear the volume change sound ... etc.). It may wake up after a while, and sometimes I have to restart the phone in order to make a call, for instance.
After months of using Neo's Resurrection Remix, which was working smoothly until a week ago, I have installed Lineage 15.1 yesterday freshly, and still facing this issue. Moreover, I don't use any kind of screen protectors or covers.
Anyone have faced it before? Should I try a custom kernal? Or go back to the stock ROM? Or it is a hardware issue (I wish it is not :crying?
Thanks in advance guys,
Regards.
Click to expand...
Click to collapse
Disable expanded desktop
rushier.ivan said:
Loose internal cable, I think? Yep, probably hardware issue. Did you drop it recently?
Click to expand...
Click to collapse
No I didn't. I think it is a software one.
Elektroschmock said:
Disable expanded desktop
Click to expand...
Click to collapse
I have enabled it recently, It might be the reason!
I have just disabled it and giving it a try, hope it is the solution. Thanks for your help :good: