Related
I recently got a strange touchscreen issue.
When the device comes out of deep sleep (turn on the screen with power button) my touchscreen behaves weird. Normally, when I touch the unlock slider, it follows my finger. But not now....it's like long press is not recognized. I am able to unlock the screen by wiping my finger to unlock. But the slider is not following my finger. The strange thing is, after about 10 seconds, the issue is gone, and the slider follows my finger....
Also long press on the homescreen is not working during the first 10 seconds.
What I tried to solve:
I completely wiped the phone and reinstalled .42 firmware. Then updated tot ICS using Sony Update Service and also completely wiped my phone. The problem still there...then I flashed a custom ROM (shardur_seth spacious...and also his firmware) but the problem stille there.
Anyone else experienced this? Or any solutions I could try? It was there suddenly....could it be a hardware problem? But why is it gone after 10 seconds?
Thnx for your help
it happens for me sometimes, but most of the time when someone calling me i cannot at slide to answer. what im doing is i just press power button ones and it will silence and press the home key and it will work the slide key...
any solution for this also?
mavado said:
I recently got a strange touchscreen issue.
When the device comes out of deep sleep (turn on the screen with power button) my touchscreen behaves weird. Normally, when I touch the unlock slider, it follows my finger. But not now....it's like long press is not recognized. I am able to unlock the screen by wiping my finger to unlock. But the slider is not following my finger. The strange thing is, after about 10 seconds, the issue is gone, and the slider follows my finger....
Also long press on the homescreen is not working during the first 10 seconds.
What I tried to solve:
I completely wiped the phone and reinstalled .42 firmware. Then updated tot ICS using Sony Update Service and also completely wiped my phone. The problem still there...then I flashed a custom ROM (shardur_seth spacious...and also his firmware) but the problem stille there.
Anyone else experienced this? Or any solutions I could try? It was there suddenly....could it be a hardware problem? But why is it gone after 10 seconds?
Thnx for your help
Click to expand...
Click to collapse
i face the same problem
my phone is in service center for repair
see the video below and check if ur problem is the same
Sounds like your phone is just sluggish, you're probably running too much in the background/have too much installed on the phone and it takes a while for the RAM to optimally load everything you need again after having cleared some of it whilst the phone was in sleep mode.
SCHUMI_4EVER said:
Sounds like your phone is just sluggish, you're probably running too much in the background/have too much installed on the phone and it takes a while for the RAM to optimally load everything you need again after having cleared some of it whilst the phone was in sleep mode.
Click to expand...
Click to collapse
i repaired my phone via SEUS but the problem usa still there
went to service centre ,they downgraded it to Gb the problem was still there!!!!
dhwanik said:
i face the same problem
my phone is in service center for repair
see the video below and check if ur problem is the same
Click to expand...
Click to collapse
Yes, that's exactly the problem.....I also have the problem that I cannot longpress the home screen...U have the same issue? After 10 seconds or after tapping the screen multiple times, the issue is gone until the phone goes to sleep.
I too had this issue and narrowed it down to the sluggishness due to deep sleep.
What I did was,
1) Flash nightelf kernel
2) Installed Set CPU
3) Make profiles for Screen Off
4) Whenever I have the governor as "performance" I never had the issue
5) After lot of permutation combination, I fixed a screen off profile as 460max and 134 Min with conservative as governor.
6) Also added a new profile for "In Call" with "performance" governor.
The problem was gone. Yes, it happens once in a while but much better than the situation before.
mavado said:
Yes, that's exactly the problem.....I also have the problem that I cannot longpress the home screen...U have the same issue? After 10 seconds or after tapping the screen multiple times, the issue is gone until the phone goes to sleep.
Click to expand...
Click to collapse
yes i have the same issue we are not the only users who face this problem
there are many users who face this problem
arunsankar said:
I too had this issue and narrowed it down to the sluggishness due to deep sleep.
What I did was,
1) Flash nightelf kernel
2) Installed Set CPU
3) Make profiles for Screen Off
4) Whenever I have the governor as "performance" I never had the issue
5) After lot of permutation combination, I fixed a screen off profile as 460max and 134 Min with conservative as governor.
6) Also added a new profile for "In Call" with "performance" governor.
The problem was gone. Yes, it happens once in a while but much better than the situation before.
Click to expand...
Click to collapse
i am on locked boot-loader so can't flash kernel
arunsankar said:
I too had this issue and narrowed it down to the sluggishness due to deep sleep.
What I did was,
1) Flash nightelf kernel
2) Installed Set CPU
3) Make profiles for Screen Off
4) Whenever I have the governor as "performance" I never had the issue
5) After lot of permutation combination, I fixed a screen off profile as 460max and 134 Min with conservative as governor.
6) Also added a new profile for "In Call" with "performance" governor.
The problem was gone. Yes, it happens once in a while but much better than the situation before.
Click to expand...
Click to collapse
Tried using your settings..first I had governor set to performance...but the problem still persists. Wheneven I turn on the screen I have the issue. It is possible to unlock the screen if I wipe fast enough....but it really is strange...why is the issue gone after a couple of wipes or some touchscreen pressess..
Could it be a hardware error....a sensor not getting ready or something? But why is the problem gone when the screen is on for a while.....
mavado said:
Tried using your settings..first I had governor set to performance...but the problem still persists. Wheneven I turn on the screen I have the issue. It is possible to unlock the screen if I wipe fast enough....but it really is strange...why is the issue gone after a couple of wipes or some touchscreen pressess..
Could it be a hardware error....a sensor not getting ready or something? But why is the problem gone when the screen is on for a while.....
Click to expand...
Click to collapse
I have the same problem. Is there any solution?
Thank you for help.
same problem
Feri8850 said:
I have the same problem. Is there any solution?
Thank you for help.
Click to expand...
Click to collapse
me also having same problem and touch is awesome but when the lock is open then this problem will occur and it will open after 2 to 3 attempts..
what's this i think this is not an hardware problem this is only the software ??//??
i have the same problem too. i think there is a problem with cpu.
I had these sometimes with certain combinations of kernel and ROM. Actually it's gone... (Alliance V1/JJs Hybrid ROM 3.1)
I suppose it's a combination of hardware and software configuration...
Anyone tried to higher the minimum CPU speed?
Nachttier73 said:
I had these sometimes with certain combinations of kernel and ROM. Actually it's gone... (Alliance V1/JJs Hybrid ROM 3.1)
I suppose it's a combination of hardware and software configuration...
Anyone tried to higher the minimum CPU speed?
Click to expand...
Click to collapse
i tried. also i tried to set governor to different versions. and i tried nightelf rc5 kernel. nothing changed. problem still there.
today i realized that's not about only touchscreen. sometimes phone freezing.
problem with neo (mt15i) touch screen
use alliance night-elf v1.1 kernel.I had this problem but when I flash this kernel to my neo my touch screen works good same as the first day...
Well....for me suddenly the problem is solved!!!!
I'm very glad that my display is working again! It has been for about 3 months since I was facing the problem.
Unfortunately I do not have a clear solution to this, but I can explain what I did that day, and hopefully the solution is in there. But I can not garantee it.
What I did that day
1. I tried to get beats audio working, so I had installed a numerous of Beats libs. (see xda-developers for some of those libs). The last one I tried was Walkman port by ThilinaC. Not sure how this can be related to the display issue
2. I flashed a new rom. But this time I formatted /system and /data in CWM. Normally I just did a factory reset and installed the new rom. (but guess factory reset also formats /system and /data)
Still....guess this has nothing to do with the display
3. I did a offline charge. When my phone was empty I wanted to charge it fast. So I switched off my phone, and then connected the charger to offline charge the phone.
Really not sure how the above points could be a solution to de display failure, but guess if it was the digitizer that was the problem, it's strange that it is fixed out of knowhere....but the above actions are what I did that day....so maybe it's helpful and is the solution in there...maybe.
I'm glad the problem is gone
Yes, I am facing this exact problem, I am going to take my mobile to the service center !!!.
Hi, don't now if this is the right section for this question but I installed Jelly King Cm10 the other day and it's a great rom, had no FC or anthing apart from when i go to sleep around 11ish and phone is in deep sleep i wake up aroung 6ish and go to wake the phone up it's turned it self off so i have to use the power button to switch it on. I'm sure I saw something about when to mae the idle like, day, night etc but can't find it or was that on another rom i'd been using, great rom but can someone please help on this issue, thanks:good:
erasure1969 said:
Hi, don't now if this is the right section for this question but I installed Jelly King Cm10 the other day and it's a great rom, had no FC or anthing apart from when i go to sleep around 11ish and phone is in deep sleep i wake up aroung 6ish and go to wake the phone up it's turned it self off so i have to use the power button to switch it on. I'm sure I saw something about when to mae the idle like, day, night etc but can't find it or was that on another rom i'd been using, great rom but can someone please help on this issue, thanks:good:
Click to expand...
Click to collapse
what ur experiencing is SOD(sleep of Death), u can change ur kernel to Siyah v4.1.2 and see
I had similar problem on CM10 experimental (20120825). When I woke up the phone was turned off, but I couldn't turn it on. I found that the battery discharged to 0%. >.<
Now, I'm on stock.
erasure1969 said:
Hi, don't now if this is the right section for this question but I installed Jelly King Cm10 the other day and it's a great rom, had no FC or anthing apart from when i go to sleep around 11ish and phone is in deep sleep i wake up aroung 6ish and go to wake the phone up it's turned it self off so i have to use the power button to switch it on. I'm sure I saw something about when to mae the idle like, day, night etc but can't find it or was that on another rom i'd been using, great rom but can someone please help on this issue, thanks:good:
Click to expand...
Click to collapse
that's Sleep of Death bro. Flash another kernel, and don't mess what you don't understand
Swyped from Samsung Galaxy SII
Sleep of death!
I was on siyah 4.0.1 and it happened using that now i'm on Dorimanx v5.70 and the same this moring, Extweaks = default cpu governor: lulzactiveq, Deep-sleep cpu governor = ondemand.
I now it's not a real problem and the roms fine but just thinking it's the sgs2!
Thanks guys
erasure1969 said:
I was on siyah 4.0.1 and it happened using that now i'm on Dorimanx v5.70 and the same this moring, Extweaks = default cpu governor: lulzactiveq, Deep-sleep cpu governor = ondemand.
I now it's not a real problem and the roms fine but just thinking it's the sgs2!
Thanks guys
Click to expand...
Click to collapse
Luzactive as default governer unless tweaked properly might cause issue's, try the default "pegasusq' governer by resetting the extweak profile once and see
Sun90 said:
Luzactive as default governer unless tweaked properly might cause issue's, try the default "pegasusq' governer by resetting the extweak profile once and see
Click to expand...
Click to collapse
Ok Sun90 done that thanks, but the first time it happened using siyah that battery was dead in the morning and using Dorimanx the juice was 100% but phone was off, didn't have to take the battery out just used the power buttong to get it on
change kernel and restore default option for exTweaks using clokworkmod
vitalianoleone said:
change kernel and restore default option for exTweaks using clokworkmod
Click to expand...
Click to collapse
I've reset Extweaks in clockwork, cleared cache etc, Governor = HYPER and Deep-sleep, ondemand
no problems with jelly king 1.5
Hello Everybody.
So this is one of rare place where i can post to tell everyone who use this ROM that it's works like a charm in my S2 with Siyah 4.1.4 Modem XXLPX.
sources i use to :
http://forum.xda-developers.com/showpost.php?p=31218484&postcount=436
Extweaks from
http://forum.xda-developers.com/showthread.php?t=1875573
and
http://forum.xda-developers.com/showpost.php?p=31202456&postcount=1752
have a look for services.jar optimized :
http://forum.xda-developers.com/showthread.php?t=1869663
and
http://forum.xda-developers.com/showthread.php?t=1617219
I only want to share my experience ans perhaps help....
Hope this help too.
les fautes ? i'm French . c'est pour ça.
Whoaaaa V 1.6.2 is just MAGNIFIQUE !
http://imageshack.us/a/img24/9696/jellykingv162.jpg
Let me first apologize for not posting in the correct dev thread, for that I do not have permissions to do so. Also like to thank all the devs for their hardwork, time, & commitment to helping others.
I have recently flashed my LGOG E970 to SnowJB's (Team Carbon) CarbonRom. However, I notice extreme battery drain (~1% every 2-3minutes) using the default Kernel. I tried to adjust the performance control settings to lower the min setting from 1026 to 384 but the settings will not save /stick.
I ended up flashing to Houcha's geeb kernel based on someone's post of a similiar battery drain problem. However, unlike that user I am still experiencing major battery drains. Once again i tried to adjust the Performance Control settings and still have the problem of it not "sticking".
Any ideas on how to get the settings to stick or resolve this crazy battery drain issue?
FYI: LGNPST to JB 4.1.2 -> Rooted -> Unlocked -> Flashed CarbonRom with CWM v6 per OP directions
Thanks in advance
Disable performance control with titanium backup. Download trickster mod app or similar and use that. I had the best battery performance using houstonn's modded 192 mhz kernel.
Sent from my LG-E970 using xda app-developers app
thank you
Thank you kind Sir for the tip. I ended up freezing the performance controller with mybackup pro. It sort of fix the issue for now, but it still does not save the settings with a reboot. I just have to remind myself to reconfigure trickster every time I power off
bamboochimp81 said:
Thank you kind Sir for the tip. I ended up freezing the performance controller with mybackup pro. It sort of fix the issue for now, but it still does not save the settings with a reboot. I just have to remind myself to reconfigure trickster every time I power off
Click to expand...
Click to collapse
I too experience this, however as mentioned above with houstonn's 192mhz kernel, the settings will stick; verified working on my CarbomROM LGOG.
I'll try it out
croozah said:
I too experience this, however as mentioned above with houstonn's 192mhz kernel, the settings will stick; verified working on my CarbomROM LGOG.
Click to expand...
Click to collapse
I will flash the 192mhz ROM and let you know if it resolves my issue the same as it resolved yours. ty
bamboochimp81 said:
Thank you kind Sir for the tip. I ended up freezing the performance controller with mybackup pro. It sort of fix the issue for now, but it still does not save the settings with a reboot. I just have to remind myself to reconfigure trickster every time I power off
Click to expand...
Click to collapse
If you find your settings to be stable after continuous use, in Trickster if you hit menu, there's a set on boot option. Just enable it, and I think you can also ask for a notification from Trickster when it does start.
So after i recieve a call, upon ending it, the back led remains on(sometimes flashing - like when u are recieveing a call)
If i do a reboot, the led turns off. When the phone boots, the led stays off also, only after a call, the led stays on.
I`m using some xposed framework modules like :
DS battery saver
G2 Skin tweaks
SB Icon Hider
stock ROM with dorimanx kernel.
Any ideas what could it be?
Using tricker mod? I think you can change the values with most kernel tuners to remain on and flash for various reasons.
Cheers, J.
J said:
Using tricker mod? I think you can change the values with most kernel tuners to remain on and flash for various reasons.
Cheers, J.
Click to expand...
Click to collapse
what do you mean by tricker mod exactly?
Its a kernel settings modifier. That question kinda confirms an answer. Perhaps something in the aftermarket kernel your running.
Cheers, J.
J said:
Its a kernel settings modifier. That question kinda confirms an answer. Perhaps something in the aftermarket kernel your running.
Cheers, J.
Click to expand...
Click to collapse
I tried searching for anything related to the lock button led in this tweaks windows of the kernel.. but i can;'t find anything related..
I also disabled all xposed modules, but the issue persists. Upon recieving call * doesn't matter if answering or not* the led keeps flashing untill i reboot the phone.
Try going back to stock kernel and see if issue goes away?
Cheers, J.
well this is odd.. even with the stock kernel 3.4.0, the issue is present. hm..
I also flashed the 380 dpi from here but i doubt is has anything related..
Try a clean install and see what happens.
Cheers, J.
I actually installed the G3 ROM from optimus, and the issue was solved. I always wanted to try a G3 rom so i jsut did that.
Strange issue tho.. as changing back to stock kernel and disabling xposed the issue was still present.
Thanks for the help and ideas.
I'm facing an issue with screen wake up with my kenzo in Nougat 7.1.x roms. The screen takes more than a second to wake up, and the issue occurs both while using the fingerprint scanner as well as using the power button to wake. On succesful scan/power button press, the button backlights come on immediately, but the screen comes on only after a second, and sometimes even more.
This issue was also present till MIUI 8.0.6.0, but was resolved in the MIUI 8.1.1.0 update. I also tried Xiaomi EU rom and it did not exhibit the issue at all.
I know a mere one second delay is not something to rant about, but still it gives the perception of a cheap underpowered phone, despite having one of the most powerful SOCs around. The fingerprint scanner is really quick and this issue doesn't do justice to it.
What can I do to speed up the screen wake up in custom ROMs?
P.S: I use Radon kernel in all the custom ROMs that I flash. Anything to do with that? And, please DON'T suggest me to go and stick with MIUI!!
Regarding Radon. Which version did you use? I think it was 3.7 were they changed something that slowed down the wake up. It should be fixed now in 3.8
If you're using 3.8, let the developer know they may be able to sort it out.
theoneofgod said:
Regarding Radon. Which version did you use?
Click to expand...
Click to collapse
I've been using Radon right from version 3.7.4, and am now on 3.8. I have tried wakeup boost as well, and noticed no real difference.
jayaram95 said:
I've been using Radon right from version 3.7.4, and am now on 3.8. I have tried wakeup boost as well, and noticed no real difference.
Click to expand...
Click to collapse
Wake up boost doesn't do anything for me either. Have you adjusted any other settings, like minimum frequency? It could be that too. I'd reflash the kernel, set balanced profile and don't touch anything in KA (maybe disable it to prevent changes) and see how that goes.
theoneofgod said:
Wake up boost doesn't do anything for me either. Have you adjusted any other settings, like minimum frequency? It could be that too. I'd reflash the kernel, set balanced profile and don't touch anything in KA (maybe disable it to prevent changes) and see how that goes.
Click to expand...
Click to collapse
I do the same as well. I flash Radon with balanced profile and don't touch anything in it except the sound settings.
Post something in the kernels thread here at XDA, see what they have to say. It could be something they can fix.
theoneofgod said:
Post something in the kernels thread here at XDA, see what they have to say. It could be something they can fix.
Click to expand...
Click to collapse
Is it really related to the kernel? Or does it have anything to do with the ROM?
jayaram95 said:
Is it really related to the kernel? Or does it have anything to do with the ROM?
Click to expand...
Click to collapse
The reason I think it could be the kernel because of earlier changes/reverts they did that slowed down the wake up. It could be entirely the ROM's fault. Does it happen with the stock kernel?
theoneofgod said:
The reason I think it could be the kernel because of earlier changes/reverts they did that slowed down the wake up. It could be entirely the ROM's fault. Does it happen with the stock kernel?
Click to expand...
Click to collapse
Need to check. I've never used stock kernel of any custom ROM.
jayaram95 said:
Need to check. I've never used stock kernel of any custom ROM.
Click to expand...
Click to collapse
Did u uncheck d2tw while install8ng radon??
Androbots said:
Did u uncheck d2tw while install8ng radon??
Click to expand...
Click to collapse
Yes. I don't need dt2w at all. I've even turned off Ambient Display.
Cant solve this issue .... Present in 7.1.1 , checked in resurrection remix 5.8.1 ( on many Nightlies) and AOSP Extended 3.1 . Issue present on both stock and Radon kernel.