In two different AOKP roms (AOCP, PACman), I have a problem where if I'm on a call and forcefully turn the screen off by pressing the power button (as opposed to by the prox sensor or by timeout), the phone reboots. Interesting, if there's audio on the call, it will continue to play as the shutdown animation is playing.
I have the accessibility setting to end calls with the power button turned OFF. I can't think of any other settings which would affect this.
I tried searching on this symptom, but didn't find anyone with this issue. I clean installed both ROMs, but AOKP seems to be a common denominator. Anyone have advice for me?
Does it ever reboot at other times after you've pressed the power button, or is it only while in a call? I recently had a problem where the phone would reboot after I turned it on. I was on CM and went to SHOStock and it still did the same! I figured, hell, after two different ROMs and it still acting the same, maybe it was hardware. Ended up taking the phone apart and there was some gunk around the inside part of the power button keeping it held in too far and triggering the reboot after a few seconds. After removing the button and carefully cleaning it (it's very small), I now no longer have a reboot problem on either CM or SHOStock.
sbrown23 said:
Does it ever reboot at other times after you've pressed the power button, or is it only while in a call? I recently had a problem where the phone would reboot after I turned it on. I was on CM and went to SHOStock and it still did the same! I figured, hell, after two different ROMs and it still acting the same, maybe it was hardware. Ended up taking the phone apart and there was some gunk around the inside part of the power button keeping it held in too far and triggering the reboot after a few seconds. After removing the button and carefully cleaning it (it's very small), I now no longer have a reboot problem on either CM or SHOStock.
Click to expand...
Click to collapse
I've only had it happen so far when turning the screen back on during a call. If I don't force the screen off in the first place, the phone will happily turn the screen on and off due to prox sensor. It will also time out and let me turn it back on without the power button with no issue. Because of this, I don't believe it's a mechanical issue. I didn't have this problem until trying AOKP ROMs, the timing is too coincidental.
Based on what I'm seeing with the boot animation, it isn't a full reboot (I don't see the SGS II logo, for example). I didn't even know that rebooting only the OS was possible.
I assume there are logs I can check to help figure out what's going on, but I don't know where to find them.
I found a string of posts in the Carbon thread: http://forum.xda-developers.com/showthread.php?p=46998058&highlight=just+carbon+reboots#post47133798. Same symptom, but different trigger. I tried, I can rotate the camera just fine. I'm currently running the 10/31 nightly of PACman, guess I'll update past 11/2 later today and see what happens.
11/6 was a bust (lots of FCs after a clean install), so now I'm trying 11/10, 11/4, or 11/5.
Initial results with 11/10 show that the problem is fixed; gonna restore my old ROM, go through the TiBu dance, and see what happens when I finish setting up 11/10 completely. Maybe it's something I'm doing.
OK, 11/10 fixed my primary issue. Further, I used to have pretty nasty screen-on lag that I couldn't fix even after messing with the CPU and I/O profiles. Hurray!
Based on my experience this may affect other AOKP based ROMs (like Carbon or AOCP), but it might have been present in pure CM (CyanogenMod) - hard to tell. Hope this helps someone else.
****, it's back. Must be something I'm doing. The quest continues...
Related
When I do a soft reset, my phone is fine and everything works okay. However, after the first time the screen cuts off to standby, when it resumes the buttons on the bottom panel (Home, Back, Call, End, Select) no longer function. I can confirm that they all function perfectly prior to standby, and after the fact, none of them.
I'm wondering if this is a known issue, and if there's anything I can do to patch it or look it up. I've tried a few different roms, and it's a constant issue. Even after a full wipe with Task29 and a reflash with two separate roms, the behavior sticks. As soon as the phone comes back from standby mode the buttons just fail.
If it's at all relevant this is a Sprint Touch Pro. If no one can help me and there's no alternative I ask for help finding a way to disable standby entirely. Sure keeping the LCD on constantly will drain the battery, but being able to use the answer and hang up buttons, and the camera FAR outweighs that.
Well, I haven't been able to find anyone with a solution, but I've worked around the issue a bit by installing Keepawake 1.1 and setting it to run when manilla is running. Now my phone never sleeps, and the face buttons work. I'm currently looking for a small piece of metal I can mount over the power button to prevent accidentally triggering standby mode. Then my phone will be mostly usable again. Hopefully someone can shed some insight as to the cause of it all, but for now at least I may have found a way to work around it. We'll see how it affects my battery life.
edit:
Most helpful recommendation (aside from a solution to the root of the problem): could anyone recommend a way to disable the power button, or possibly remap it to launch task manger or something useful?
edit2: Remapped the power button to lock the phone using RaphKeyboardConfig. Works okay for now. Between this and keepalive, my phone won't go into standby if left on it's own.
After multiple fails with MTD based ROMs (sdcard issues), I've settled in to TSM resurrection 1.0 (EI20). One thing I can't find mentioned in the ROM thread is a problem I'm having where the screen will randomly turn itself on from sleep. Usually when this happens and I try to push the power button to turn the screen back off, it won't turn off, but instead takes a screenshot. Has anybody else encountered this issue or know what to do with it?
I'm running TSM resurrection with the base kernel from PWGB, no other mods (XIX, heap size, etc). I don't know if this is related, but my battery usage also shows that the email app has been awake for 18m. Could there be a problem with that app that is causing the screen on issues?
I had the exact same issue as you which sadly made me revert back to PWGB with GeeWiz kernel. The screen capture happened all the time for me (it was the worst in the car dock). From my troubleshooting I was not able to fix it (tried different kernels, task killers, etc.). The closest thing I could pin point was it had to do with the soft key back button. The phone thought I was holding down the back button and I would hit the lock button which would cause the screen shot. As far as the screen coming on, I have had that issue with multiple ROMs, but it never really caused problems for me. Hopefully this helps a little.
I'm not sure where off the top of my head, but there is a screenshot.apk you have to delete to stop the phone from taking screenshots. It's been discussed a few times on xda where. Maybe search for it?
"better to be safe than to be odining" -me
Odd. That was happening for awhile, but not since I wiped data, reflashed, and installed the most recent TKSGB kernel.
When it does happen, push the back button. It should stop the screenshots.
I've had this problem on my GSII (SGH-i777) since playing around with ICS roms, in both AOKP and CMD.
What happens is, after locking it, or a program is supposed to wake it from a blank screen, nothing happens when pressing the power button. The phone is still on and the buttons on the bottom still light up and I can feel vibrations and sounds, but I cannot get the screen to come back on without rebooting.
I'm not sure what causes this and it seems to feel semi random, but I suspect it may be connected to the locking animation in some way introduced in ICS (the emulation of turning off a CRT monitor).
I'm wondering if anyone else has run into this problem and knows a good fix to avoid it (other than going back to stock firmware).
What app are you using that is supposed to wake your phone? Just my opinion but it sounds like an issue with the app.
PS. Crt off animation was introduced well before ics.
ThomasBags said:
I've had this problem on my GSII (SGH-i777) since playing around with ICS roms, in both AOKP and CMD.
What happens is, after locking it, or a program is supposed to wake it from a blank screen, nothing happens when pressing the power button. The phone is still on and the buttons on the bottom still light up and I can feel vibrations and sounds, but I cannot get the screen to come back on without rebooting.
I'm not sure what causes this and it seems to feel semi random, but I suspect it may be connected to the locking animation in some way introduced in ICS (the emulation of turning off a CRT monitor).
I'm wondering if anyone else has run into this problem and knows a good fix to avoid it (other than going back to stock firmware).
Click to expand...
Click to collapse
Try turning off CRT in system setting / ROM Control / General UI / uncheck CRT off animation. I have it off and never have a problem in AOKP
This guy probably didn't wipe everything before posting. Yes this includes your data.
Sent from my MB860 using Tapatalk 2
I am unable to wake the phone during a call. As soon as I answer a call, or press the call button my screen turns off. I can not wake it with proximity sensor, double tap or power button. There is literally no way to turn on the screen once a call has started. It was random when it started. I had been using Vanir for a while and then one day it started on my phone, and never left. I have even flashed my OG nandroid stock and the issue was present there after flashing to that.
I have swapped ROMs, AOSP x4, BarRin, Stock, you name it, but to no avail. I have cleared everything off my internal, wiped the internal memory, sideloaded a ROM back from scratch and booted up plain jane... same issue.
I am attaching a link to a logcat incase anybody has any ideas. I'm simply lost with this, and it is a major issue considering every time I make a call I have to be ready to take the case off so that I have faster access to pop the back off and battery pull. This is not a way to live.
PLEASE if someone has any ideas on how/where to go about fixing this, I will be grateful.
Not sure if it matters, but after a call ends, I need to wait about 5 or secs before the power button will be recognized. After it's first press it seems to first power off the screen, as though it is awake the whole time, but black and inoperable. After the screen thinks it's off, the second press turns it back on. I have also tried other dialers too, but it totally seems like an integrated OS/Firmware issue at this point.
Are you by chance running Greenify? I was having some issues when sleeping system apps. What Xposed modules are you currently running?
No battery apps installed whatsoever. No battery saving modes enabled.
Mods- App Settings
DarkTube
GravityBox [KK]
Pandora Patcher
Youtube AdAway
Sorry a bit tired. I just noticed you stated it still happens after you nandroid back to your previous backup. Do you have a screen protector or anything on it?
Try going to Settings/Call and disable the proximity sensor and see if you have the same results
It's not the sensor though b/c it has 0 results with the double tap to wake and also the power hardware button itself. Holding the button, pressing it quickly, tap it multiple times in a row. Additionally, I do not have a screen protector.
For a week or two now,* I have been having some funny things happen with my Redmi Note 4 (Qualcomm, Global) phone.
Before that it had gotten water in it and basically shut down entirely, but they fixed it and got it up and running. When I picked it up they showed me watermarks on the screen, saying that the screen had frozen only once but that it may just be lagging.
Since then I have had a few symptoms of an issues, perhaps hardware issues, but potentially something that I can fix without paying more for parts.
Here are the things that happen:
- Music stops suddenly (screen on or off) and the music app has to be reopened (DoubleTwist, Miuiu's Music app, etc); Somes while in Doubletwist, if I click to visit home screen (square button) than the music stops. (this is the first issue that I noticed).
- 1-2 seconds of white screen before already-open apps appear after selected; Sometimes problems with apps loading or screen goes black when loading
- When closing apps or returning to home screen, it looks like the desktop(?) background comes up and then a second after is is re-populated with icons as if system is refreshing the home screen
- Once any of these issues begins, it usually worsens and the cell phone gets slower, behaving more and more strangely until not even useful to me; Reboot clears it right up for an hour or two or whenever this wierd stuff starts to happen again
-It seems like if I make a point of using the phone modestly, slowly, I can avoid these issues from starting up
- Sometimes reboot rometimes hangs on initial black loading screen
- Sometimes if I hit the power button to turn off the display, I can not turn it back on with that button (neither does the battery-dead orange light flash), so I have to reboot.
-When I turn the phone screen off while it has been working fine, I come back later, turn on the screen to find that it is now on the boot logo screen and it stays until I hard-reset the phone.
So, these are potential issues I have guessed at:
* Screen damaged? So far, other than watermarking at the top and some backlight bleed, sensistivity is perfect on the phone, and symptoms involving screen always seem to be triggered more by apps or pressing buttons.
* Apps or Android corrupted/internal memory damaged? I backed up via Settings and did a Hard/Factory Reset, then restored from backup. I still have the problems.
* RAM partially damaged? I test RAM with two apps and none of them showed issues. Namely my available RAM and used RAM reported always add up to the 4GB my phone has.
*Other Hardware Components failing? I used 3 apps to check all of the hardware devices and sensors that I could think of. Vibration is the only thing that does not work, and honestly, I don't care much about vibration.
Today I have suspected that settings may being at fault, and/or battery savers turning off my audio. Battery savers often identify my music apps as using "excessive amounts of power," perhaps because the speakers at involved, but it does make me think... I removed any battery-related and security apps, then turned off all battery saver options in settings earlier today. In 2 hours of music listening after that, I have not had any shutdowns, but I am not convinced I have solved the problems. In the weeks after this, the issue is back and the audio issue is always followed by the phone operating very sluggishly.
I have done a factory reset and restore, and the issue persists. Do you think there's any point in trying to do a clean reflashing of MIUI? Could it be a software issue or definitely hardware?
What advice can you give me?
Thank you for reading.
You can try booting in safe mode and then check if the problems still persist. Other than that, I suggest you to get advice from senior members of the forum.
Lazy_Pickachu said:
You can try booting in safe mode and then check if the problems still persist. Other than that, I suggest you to get advice from senior members of the forum.
Click to expand...
Click to collapse
Miui 9 does not have safe mode to boot in.