Hello I have a 9100 international version, and this is not your usual 1-2 seconds lag on wake. My phone (well, my friend's) takes around 10 seconds to wake. Not exactly wake but for the display to show, because when I press the home key or power key, the soft keys light up and the phone vibrates to the touch, the screen is also responsive to touch while the screen is off.
All this started after I flashed paranoid android into it, but after trying multiple roms, the issue is exactly the same. I also flashed a pit file to repartition the phone to have more storage for apps and it worked. I mean the phone works flawlessly except for this particular issue of the screen not turning on fast enough, even though the touchscreen seems to be responsive.
Ill flash stock back to it and give it a try. In the meanwhile, any one else have had this issue?
Try Neatrom 6.4 is a stock based with more feautures and battery friendly. Yeah i faced this issue one time, in neatrom 6.4 i never have this issue.
Related
Weirdest issue I've ever come across.
Phone is less than 2 weeks old and was working fine. No hard drops, no water damage. I was running CM 10.1 (3.1.10 Blade Kernal) without issues until today. All of the sudden the capacitive buttons stopped responding. The backlight still comes on.
I flash a recovery to Paranoid Android which I tried out before, still doesn't work. Pie controls work, but on screen navigation buttons don't respond.
In TeamWin Recovery the on screen navigation buttons also don't respond, which is super annoying since I can only do one task, and then have to hard reset my phone.
I did a factory reset and they still don't work. Any idea what's going on here?
chrriiiss said:
Weirdest issue I've ever come across.
Phone is less than 2 weeks old and was working fine. No hard drops, no water damage. I was running CM 10.1 (3.1.10 Blade Kernal) without issues until today. All of the sudden the capacitive buttons stopped responding. The backlight still comes on.
I flash a recovery to Paranoid Android which I tried out before, still doesn't work. Pie controls work, but on screen navigation buttons don't respond.
In TeamWin Recovery the on screen navigation buttons also don't respond, which is super annoying since I can only do one task, and then have to hard reset my phone.
I did a factory reset and they still don't work. Any idea what's going on here?
Click to expand...
Click to collapse
As per more experienced developers and contributors - parandroid is a mess (I am not sure whatever that means , since I have so far only tried CM 10.1 & Slimbean... )
Addicted2xda said:
As per more experienced developers and contributors - parandroid is a mess (I am not sure whatever that means , since I have so far only tried CM 10.1 & Slimbean... )
Click to expand...
Click to collapse
Well I first experienced the issue running CM 10.1.
Since then I've relocked it and loaded the stock RUU where things got REALLY weird. The navigation keys still didn't work and soon nothing was really responsive. I can't even get past the unlock screen. The ring bounces when I touch it but it won't drag and unlock. So it's still detecting something, but it's not really responding at all. I can't even turn the thing off now as holding the power button down restarts the phone. what is this i don't even....
bump!
I need help with this and after extensive searching, I haven't found anyone else with this sort of problem.
I'm trying to install a ROM via TWRP but my capacitive and on screen navigation buttons don't do anything, so I'm stuck without a ROM at the moment.
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...
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.
The Capactive Touch buttons on Galaxy S2 does NOT dim or goes out automatically & rather radiates a strong touch screen light,even after the "Touch Key Light duration is altered to various intervals (1.5 sec or 6sec)" . The two Touch light only goes off with the Phone's Screen timeout or manually (pressing the power button) .
It was never like this till last week when the Octa-LCD inside my SGS2 broke & today when i changed the complete display assembly of the SGS2, i got to take note of this peculiar & harassing problem only now..which is eating up my mind.What's happening &why? Was the Screen replacement Not correctly carried out (done at my Authorised Samsung Service Centre) HARDWARE problem or is it due to any Software issues? (Samsung Service Centre did say that they did no software job,only just a screen replacement i.e a Hardware job on my SGS2)
i'm Rooted, on JB 4.1.2, Stock Rom with Siyah Kernel !
Though Samsung have offered me to replace my screen for a second time in a few days ( they dont have any more stock of the SGS2 scrren at this branch), but i myself NOT Sure..what's causing the problem ? (Everything in my SGS2 is running fine except this stressful quirk which was Not there before).
.'m at a fix ,please Help me with your advices ASAP !!!!
Have you tried flashing a different kernel like Apolo kernel 4.15b or try an older version of siyah kernel 6.0beta4.
I don't really think it is software problem if it was working perfectly fine before.
HELP my SGS2 !
Thanks @gsstudios for the good advice !
...but is there any app/mod for the SGS2 that can control the capacitive buttons light settings, other than the system settings for the SGS2 like the one> Galaxy Button Lights https://play.google.com/store/apps/details?id=com.notquiteinsane.galaxybuttonlights&hl=en (works for SGS6 but not in SGS2)
I'm Not quite a Flashholic,neither do i get much time to tinker around ..so any other quicker way,except flashing a different rom, to control the light settings?
* 1 important thing Maybe ...when my Phone with the "New" screen was booted for the first time, the "developer options" & "adb debugging" were left enabled by me ( to backup my contacts , messages,etc) Could this have any detrimental effect on the capactive button light settings? I have thereafter disabled/enabled those options & rebooted the phone many times but nothing simply changes !
Btw, if all other functions of the phone is Ok ( i checked the phone's sensors with CPU-Z & everything was running fine) & the Screen touch response seems perfectly ok ,then also can this capactive button quirk be the result of Hardware manfunctioning /defect arising from the very New replaced Samsung Octa LCD itself? // I did not install any new apps, nor me,nor "Samsung Service Center" did anything on the Software part of my SGS2 recently //
Currently, only two options for those Capacitive button key lights work :1) always on & 2) always off & i have opted for choice 2 to save the distraction from the glaring/disturbing light of the capactive buttons & mainly to save some battery power !
So,if any body else have a great idea to fix the light quick , i would be immensely thankful to all !
i think u should reflash stock firmware and see if that fixes it.
yeah, Zyfloss, as you said it & i also similarly thought...i reckon the problem has been solved as of now with thë flashing of the SGS2 official Stock JB 4.1.2 Rom,the capacitive lights now seems to be working normal,timing out automatically after 1.5 sec or 6 sec as i want it ! Anyway, Thanks to Everyone who saw my post, tried to help & replied ! :good:
Help me
I am Japanese and I am not good at English.
Because it translates and writes, it may not be correct English.
I can not unlock after sleep.
The screen lights up with the power button.
But swiping the screen does not react.
In this case it is OK.
case 1
In Recovery Mode (TWRP), I can swipe the screen to unlock even after sleep.
Case 2
I can use it without problems until you sleep or lock after powering on from power off.
However, after locking with sleep or power button, the screen lights, but you can not swipe.
Initialization already done
Reinstalled ROM (Officiak MIUI, CM12 etc)
But it does not fix it
Well, this can be one of two issues:
1. Hardware issue, and a very weird one. Almost one-of-a-kind.
2. What MIUI version have you tried? 8.5.10 MIUI 8? You can also try MIUI 7 or the MIUI 9 beta. Try all of them and see if any of them works.
I tried these ROMs
I have not tried MIUI 7, but have any good signs to try?
miui official HMNote2Global_V8.5.1.0.LHMMIED
xiaomi.eu_multi_HMNote2_7.9.21_v9-5.0.zip
Thank you.
I tried these ROMs
I have not tried MIUI 7, but have any good signs to try?
miui official HMNote2Global_V8.5.1.0.LHMMIED
xiaomi.eu_multi_HMNote2_7.9.21_v9-5.0.zip
Thank you.
My Redmi Note 2 has the MIUI 8 8.5.1.0 and no problems here. For MIUI 7 you can try 7.3.3.0 and for MIUI 9 have you tried 7.9.15? If not try these ROM versions and report back.
I tried, but the result was Ng.
7.3.3.0 and 7.9.15
Since it is not a software problem (apparently), since when has this issue started appearing? I am suspecting this is a hardware issue. Say everything you know, I will try and understand.
Since returning from sleep in TWRP mode is no problem, I think that it is not a hardware problem.
Since returning from sleep in TWRP mode is no problem, I think that it is not a hardware problem.
The problem is that the screen stops responding after sleeping normally after starting normally.
You can use it without problems until the screen goes to sleep.
give up.
(´；ω；`)ｳｩｩ
same case like me
I have flashing rr 6.0 and cm 13.0 and so on based Android 6.0. But except dinolek lineage worked, other's lock screen touch not work sometimes. It's wired. I don't think it's hardware's issue
Exact same problemfor me too. It's not Touch panel problem. I ordered new Touch panel + LCD + frame replacement. After replace still same issue.
If the device goes to sleep -wake up, touch panel stop working.
After reboot phone works perfectly until it sleeps again.