Database Develop

[Q] Touch buttons dont work after call

Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks

coola71 said:
Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks
Click to expand...
Click to collapse
Same problem here! I don't need to take out battery, just reboot device
Any idea? Root? What ROM?

This thing has too many troubles for users. Just got mine but haven't used it yet. Samsung hasn't made a good phone so far. Problems left to right. Note could be my last Samsung phone.

i have noticed the same thing too, but i am running Sheep Rom, it seems intermittent. what rom are you running?

coola71 said:
Hi everyone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
Click to expand...
Click to collapse
I used to have issues with my prior android phone if I got dirt or whatever over the proximity sensor.
Android phones disable the touchscreen/buttons during a phone call so your cheek doesn't hang up the phone.
If your phone is dirty, however, it gets confused, and keeps things disabled after the call.
This happened to me fairly often when I had a case/screen collector that tended to collect pocket lint.
- Frank
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
CyberGhos said:
This thing has too many troubles for users. Just got mine but haven't used it yet. Samsung hasn't made a good phone so far. Problems left to right. Note could be my last Samsung phone.
Click to expand...
Click to collapse
You can't be bleeding edge without some bleeding.
The GNote ain't perfect and it's a bit rough on the edges, but there's no way I would trade it for any other phone.
- Frank

ChodTheWacko said:
I used to have issues with my prior android phone if I got dirt or whatever over the proximity sensor.
Android phones disable the touchscreen/buttons during a phone call so your cheek doesn't hang up the phone.
If your phone is dirty, however, it gets confused, and keeps things disabled after the call.
This happened to me fairly often when I had a case/screen collector that tended to collect pocket lint.
- Frank
---------- Post added at 01:32 PM ---------- Previous post was at 01:31 PM ----------
You can't be bleeding edge without some bleeding.
The GNote ain't perfect and it's a bit rough on the edges, but there's no way I would trade it for any other phone.
- Frank
Click to expand...
Click to collapse
This. You shouldn't go Samsung or Android if you don't want to do some finetuning. If you want an out of the box solution take buy an iPhone. Then you can wait for Apple to release updates instead of being able to fix it yourself the same day.

i agree, its not even a hardware problem, its a software problem. i can accept small glitches as long as i can fix them, unfortunately you cant fix a hardware malfunction with software, unless of course the patch your applying is going directly over the antenna like a certain iGadget4

coola71 said:
Hi everyone
A issue I have noticed on mine and brothers phone
Basically, after a phone call, the touch bottoms (menu and back buttons) dont work sometimes, they just freeze and dont work.
It doesnt happen all the time, maybe 1 or 2 times a day. It requires a restart of the phone by taking the battery out
Just wandering if anyone has experienced this problem on there note and whether it is a software or hardware problem. Buttons work fine at all other times, but sometimes after a call they just freeze.
Thanks
Click to expand...
Click to collapse
Hi
Even i am facing the same issue n need to know what is the sol. If it is a hardware issue should i get my phone replaced. I bought it only yesterday.
For me too it happens occassionally and requires restart of the phone.
Please help someone.
Just a guess - if all users r not facing it is it a hardware issue

I had this happen once after about 4weeks of using sgn. I don't know if i had made a call prior or what, just before it happened. A reboot made the problem go away for an hour or so. It came back.
I had installed an app a few hours earlier (dell store mobile app). I removed it - not really expecting to fix it. . . It didn't.
After some futzing, I rebooted into cwm recovery: flushed dalvic cache and fix permissions and rebooted. .. it has been working ever since.
This has happened only once, a few days ago. I'd wager it is a software issue.
Sent from my GT-N7000 using xda premium

Even I am also facing the same issue on Sheep ROM
Is this a ROM specific issue or Kernel ?

Same problem here !
I have been using the SGN for the past 4 days. I had this problem in the Stock ROM and it remains even after rooting the phone.
This phone/tablet seems to be a premature release with loads of small problems here and there. I guess they plan to remove these errors directly in ICS.

I believe the problem is on the kernel, try to get some that is stable.
If you are on original stick with it, if you have it rooted try to get the newest kernel.
What happen is that the proximity sensor closes the phone screen, and lower the speed of the cpu, in some times the cpu have some collapses and forget, what you need is to control the cpu or turn off the proximitor sensor, something like that.
I dont have that problem, with both official rom and rooted phone with abyssnote.
I hope this help.

It happened with me too, 2-3 times. Few hours ago I was checking a pdf document and I received a call and the other party couldnt hear me well. While he was calling me again everything froze. Neither touch buttons nor the screen was working. I had to take the battery out, since I couldnt turn it off because of the unresponsive screen. This is really bugging me off.

I've had this occur to me twice, first time I was fidgeting with some app I can't even remember which, second time just a while ago (and that's why I went in here searching), right after making a call.
Using the S-Pen to swype-gesture back and menu they work though, it's just the buttons themselves that are dead.
Wouldn't think the proximity has anything to do with it (nice idea anyway) because then the whole screen should be unresponsive to touchm, wouldn't it?
BTW I am using xlite rom now, and maybe I could go for the cache wiping.
EDIT: I had cleared cache partition and dalvik cache this morning, ths afternoon the note has been sitting idle on the desk, 2mA drain according to battery monitor widget estimates, and without any calls the buttons stopped working again...

xinato91 said:
I believe the problem is on the kernel, try to get some that is stable.
If you are on original stick with it, if you have it rooted try to get the newest kernel.
What happen is that the proximity sensor closes the phone screen, and lower the speed of the cpu, in some times the cpu have some collapses and forget, what you need is to control the cpu or turn off the proximitor sensor, something like that.
I dont have that problem, with both official rom and rooted phone with abyssnote.
I hope this help.
Click to expand...
Click to collapse
+1 I'm using Abyssnote kernel too - no problems with soft buttons yet.

anyone find a fix for this yet? i have to reboot my phone after pretty much every call to get the buttons working again. starting to get really annoying
forgot to mention im on stock rom unrooted

Reset and Root - CFKernel and AbyssNote worked for me
n0thingr3mains said:
anyone find a fix for this yet? i have to reboot my phone after pretty much every call to get the buttons working again. starting to get really annoying
forgot to mention im on stock rom unrooted
Click to expand...
Click to collapse
I had rooted and applied CF Kernel to my rom and had faced a few problems. But after wiping and applying CFRoot (latest) again I did not face any problems.
I have had no problems in the past 24 hours.
You can use the guide by Chainfire to root and apply CF Kernel (the best guide ever) and test for a day or two. then try moving to AbyssNote1.4 (I moved because I wanted to test OC)
Before you root and flash kernel, I will recommend factory resetting(since you are unrooted at the moment) and do not install any apps - because that is what actually worked for me.
UPDATE :
I havr started facing button issue on 1.4 AbyssNote as well.

Same problem here not woking :-( :-( :-(
---------- Post added at 06:17 PM ---------- Previous post was at 06:16 PM ----------
How to fix this bug???

So, some news. I've been fighting with a nasty battery drain due to the phone being unable to keep the deep sleep status. In the process I've tried flashing AbyssNote kernel 1.2 (people were saying 1.4 suffered from high drains, and I haven't seen this problem since then... but it's been just a few, so it may be too soon.

ephestione said:
So, some news. I've been fighting with a nasty battery drain due to the phone being unable to keep the deep sleep status. In the process I've tried flashing AbyssNote kernel 1.2 (people were saying 1.4 suffered from high drains, and I haven't seen this problem since then... but it's been just a few, so it may be too soon.
Click to expand...
Click to collapse
I can confirm high battery drains with Abyss 1.4 (revert back to 1.2). But it is the only kernel which don´t suffer "touch buttons bug"

[Q] Tried Everything - Touchpad Screen Unresponsive (CM9)

Hi
Looked for this issue on the forum and can find instances of it happening occasioinally, but not with the frequency that i have. Symptomns are that the screen will stop responding to input. I.e the screen stays painted but does not respond to my pokes or pros. Flicking the screen on and off for a split second fixes it. I believe its related to software or resource usage -sometimes i can go for ages without issues, however in the last half an hour this has happened around ten times. please help!
I have tried isolating it down to a particular app with no success, and also changed the CPU governance settings, asgin unsuccessfully. I have no such issues in WebOS.
Thanks.
ps running CM9 alpha 2, but had same issue on 0.6

flash the latest nightly.

screen unresponsive281]flash the latest nightly.[/QUOTE]
Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...
Thanks

the latest nightly offers quite a few fixes.....
including vibration from sleep and tons of other stuff. not much can go wrong.

Andysan said:
Thanks for the reply. I may consider doing that, guess that with a Android backup I don't have much to lose. Would like to avoid it if possible as not being as widespread they aren't as proven and I've ironed out all other issues in alpha 2 such as wifi etc ...
Thanks
Click to expand...
Click to collapse
There has been loads of improvements in CM9 wifi has been fixed sound distortion when the screen off is fixed many speed fixes we now have themes working
Do a nandroid backup in CWM then copy that to your pc for safety then wipe system partition DO NOT FACTORY RESET OR WIPE DATA or you will lose you data, then flash latest nightly and latest gapps then wipe dalvik cache/cache partition's then in advanced fix permission's and reboot system

Well.... I dip my hat to you guys.
Went ahead and installed the latest nightly - even if it doesn't fix my issue, I was suprised by how polished it felt compared with Alpha 2. Typically with bleeding edge stuff I'd have expected to have more issues, but alls I had to do was reinstall YouTUbe and flash the gapps-fixer zip for my Calender sync, plus I see lots of lovely new settings to play with.
Will report back if the screen hangs again, here's hoping...

Frustratingly this issue has started happening for me again running 31 May nightly - touch screen has become unresponsive half a dozen times in the last ten minutes.

Maybe trying wiping it and doing a brand new flash from the latest nightly. (I know it sucks to reinstall stuff, but maybe there are some leftover codes that is causing trouble.. )

i agree either to wiping data or up your min cpu speed as it might the amount of apps you have installed that auto start/resume when turn on the screen..

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A

I only had that problem once. Rebooted by holding home and power never had it again.
Sent from my YP-GI1 using XDA

Had this issue yesterday for the first time since installing cm9 6(?) months ago.
Tried a nightly build as suggested, but given the rarity in the first place, can't be sure it's fixed

This happens to me all the time across all ROMs I have tested.
This happens in OaT's and turning the screen off/on, fixes it temporarily.
This happens in Butta, but turning the screen off/on does nothing. I have to reboot using power/home.
I have also been unable to find a specific app that causes it, but it does seem to occur more often in graphic intensive games.
I can go for days without it happening, then BAM, it stops responding to touch, from that point forward, no about of reboots or full shutdowns seems to fix it for several hours. I'll reboot and sometimes it'll be immediately, sometimes it will be 3-5 minutes, but it will happen again.
Then a few hours later it'll stop happening and I'm good for a few more days.
Do those of you using CM9 find that screen off/on fixes it, or do you need a full reboot?

I am running the night lies and have to say that the only time I experienced this was with the may nightlies. I have not experienced any issues with the 7/04 nightly.
Sent from my cm_tenderloin using Tapatalk 2

Interestingly enough I think I found out what causes the screen to stop responding. When the TouchPad is locked in landscape and then I turn it portrait while its still locked, then the screen becomes unresponsive. Does that make sense?
Sent from my Touchpad using xda app-developers app

I take it back. The screen became unresponsive even in landscape mode. There goes my well formed and thoroughly investigated theory.
Sent from my Touchpad using xda app-developers app
---------- Post added at 07:54 PM ---------- Previous post was at 07:22 PM ----------
I've been using Nova Launcher ... I switched back to Trebuchet and it appears to be working normally. Of course I may be spouting this half-cocked like I did before. What launcher are you using?

I run SPB 3D launcher and do not experience any response issues with the latest nightlies. I use my touchpad constantly as a laptop replacement so mine gets a workout every day. To my knowledge, no one was ever able to find any one app that was responsable for this behaviour but it was noted in earlier builds.
,
Sent from my cm_tenderloin using Tapatalk 2

I too still have this issue - as per others, fine for days, then it will occur consistently and I keep having to screen off/on and eventually it stops of its own accord. Am sure its a software issue, but someone here says they also had it in WebOS and HP provided a replacement.
http://rootzwiki.com/topic/20740-screen-unresponsive-in-cm9/
For me as simply flapping the screen on/off fixes it and I've never had the issue within WebOS, it has to be software - this started as soon as I first installled CM9.

Bump - still no fix identified for this by anyone with this issue please?

To anyone still following on, followed nevertells advise and completely started again from scratch and it happened after about twenty mins of using the stock browser. I think i've tried not using that app before so am just going to assume that this is either a software bug or a hardware issue that only manifests itaelf within Android

[Still bugged, need help] Clock freezes while in deep sleep.

I´m having quite a frustrating problem. Tried to search the net for hours, only finding a handful of people with the same issue but no solution. So, I wondered if anyone can help me out here? The problem is that my clock is not updating while screen is off. Naturally, this affects all alarms and notifications as well.
20:15 -> I adjust alarm to 20:30 and put the screen off. I press power right after the screen has gone off, and see the lockscreen.
Lockscreen informs it´s 20:15 and the alarm is set at 20:30.
20:30 -> Nothing happens.
20:45 -> I press power. Clock says 20:15 for a second. After one second, it shows 20:45, and the alarm starts ringing.
So the problem is quite easy to identify- the clock doesn´t get updated when screen is off. The moment I switch it on -seeing the lockscreen- it gets updated and acts accordingly if any alarms or notifications were to ring at the period it was not updating. However, it´s much less easy to find out what´s behind it. Could anyone spare me a hint here?
I´m running a rooted P7300 with CM10, 30/10 build. Using Tasker to underclock while the screen is off in order to preserve battery life. I thought that caused the problem, but while leaving the CPU untouched....
01:00 -> Switching tablet off, putting alarm at 9:00
09:10 -> Wife wakes me up instead of the alarm. I press power.
Clock says 8:48 for a second. After that second, it gets updated, shows 9:10, and the alarm starts ringing.
I´m getting a little clueless here, so any help would be appreciated.
Running rooted P7300 with CM10 (30/10 build).
Cheers, Henu.
EDIT: Ok, I´ve come to the conclusion that this freezing happens when entering Deep Sleep. If that could give anyone any clues?

Works on CM10 version 11-11
Hi,
I can confirm that it works correctly in CM10 from 11-11.
I only have one weird problem left: the device drains more power when turned of than in standby.

I have been running the 11_11 build since it was released and had not had clock issues until today. I am not overly technical and have no clue why it is happening again. But for as smooth as this rom is I will live with it.
When mine gets confused on time it will not reset itself once i wake the tablet up, it stays messed up until I manually fix it.
Sent from my GT-P7310 using Tapatalk 2

Launcher ?
Do you use the stock launcer? Mine did strange things when using the apex launcher. No problems with stock launcher from cm10.

I am using the stock launcher but have installed nova and thinking about giving it a try
Sent from my GT-P7310 using Tapatalk 2

You could try the clock sync app from the play store. It worked on my phone when it had clock sync issues with a rom. Unfortunately, i'm new to xda, so I can't post the link, but just go to the play store and search for clock sync. It's by Sergey Barinov.

Thanks, but unfortunately none of this methods helped- I´m still having the same issue even with the 11/11- build, running Clock Sync as well. Anyone could shed any light here? I wish I wouldn´t have to go back to some (yuck) stock version.

I don't know if this will help but I just resolved this issue for myself. I did a factory reset. And also wiped all caches and system before flash. Then immediately after flash before rebooting system I wiped everything again except system. And then I started up and there was no issue with the clock. I'm running cm 10. I hope this helps.
Sent from my HTC One X using xda app-developers app

Sounds like voodoo but I´m all in for trying even that. I will post the results tomorrow.
To confirm:
1) Basic superwipe procedure (factory reset/ system, cache, dalvik)
2) flash OS -> don´t boot yet up to OS like normally
3) wipe cache & dalvik
4) THEN reboot -> to OS?

Voodoo, baby.
It worked. Seriously, what the hell. My wild guess is that some file(s) might be corrupted in the actual package- and when the system notices they are missing at the first boot, it will replace them with working ones. Then again, I´m no Android/ Linux expert.
With a clean install, I ran alarm after 8 hours. Worked. Then I added Apex Launcher, waited 2 hours. Alarm went on. Installed everything again with Titanium Backup, put alarm after an hour. Still worked. So I can confirm that it´s not app- dependant but OS- dependant. However, it worked, so thanks a goddamn zillion!!!

Congratulations. Just happy to help.
Sent from my HTC One X using xda app-developers app

I´m going to snap this piece of junk into half soon.
The problems came back, no reason why. I´m now trying one more thing, which is completely disabling Tasker, as it´s basically the only thing running while the screen is off. If that doesn´t help, i´m clueless.
EDIT: What a surprise, it didn´t help. So, it´s either non- functioning CM10 or stock ICS. I could had settled with CM9 easily, but that gave me the battery bug after two weeks. Seriously, this whole me- buying- a- tablet- and- getting- it- to- work has been a living joke. I just would love to have a stripped down OS with a Kernel supporting "all sorts of stuff" like processor speed, running app restriction, tweakable backlight etc.

Ok, so I wiped cache and dalvik and it worked for a couple of hours. Then last night the clock froze again. And this was quite interesting..
Alarm set at 10:30
I wake up 11:15 (hey, it was New Year´s Eve )
I press power and the clock says 11:15 and next alarm is set "tuesday 10:30".
Two seconds later the alarm hops into "wednesday 10:30".
Two hours later I press power, and the clock is 11:15 for a second and jumps to real time. So it´s definitely broken again.
I was just wondering- maybe I could try replacing the clock with another kernel´s version, would that be possible? Any help would be much appreciated.
EDIT: I also tried -once again- without automatic time& date (as my connectivity is set to cut off while the screen is off) and it still didn´t alarm me until I manually pressed the screen on.
EDIT2: Ran A1 kernel, no effect, still bugged.
EDIT3: Ran Tracid´s official ICS. Worked for a day, then bugged. Same thing with A1 kernel. I also had some serious issues with MTP connection and bootloader, so I restored stock and brought it back to the store where I got it for warranty repair. They think it´s a faulty MoBo.

I´m shamelessly bumping this. I ran the stock firmware with Odin and took it to the repair, as I wrote earlier.
Got the tab from warranty repair, seems that the only thing they had performed was "software update" . Very useful for someone who is constantly switching ROMs etc... like I hadn´t tried that before.
After returning to stock and all, I installed CM10 again. And "surprisingly", the problems started again. With or without apps, launchers, cachewipes, younameit. I´m now giving this a test with the stock ROM for a couple of days. I actually hope it doesn´t work, because that would be the only reasonable thing now. If it works with the stock ROM, I´m getting clueless. Does that mean I have some sort of issue which happens only in flashed ROMs instead of the stock one? That would be just....awkward.

[Q] Need to wait a while for the screen to turn on

Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you

Pawelss said:
Hey,
So my dad isnt exactly satisfied with the custom ROM I flashed on his device, he needs to wait about 4 - 5 seconds (!) when theres an incoming call for the screen to turn on. The ringtone will keep on going off during that few seconds, but the screen will be black.
So I tested it on my Nexus 4, and no such issue has been spotted by me. Although, on his device, no matter how many times I tried, the issue was never gone and I had to wait a couple of seconds for the screen to turn on so I could see who's calling.
I'm not sure whether it is a kitkat issue or not, I tried 2 different roms, first BeanStalk, and now CyanFox, both had the same issue.
I also tried to flash CM10.1, but the keyboard kept on crashing after a fresh flash, wipes didnt help (maybe someone could give me a hand here?).
Another question is, where can I find some good call recording app? the ones from the play store aren't good, they only record one side of the call, never both
tl;dr:
is there some setting that I should change for the screen to turn on quicker when theres an incoming call on kitkat?
what to do if I want to downgrade from kitkat to jellybean?
is there some GOOD call recorder app around?
thank you
Click to expand...
Click to collapse
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really

tuncay_93 said:
If you still on cm10.1 then download keyboard from market and you are good to go Also stock 4.1.2 has this lag issue when incoming call its pretty annoying really
Click to expand...
Click to collapse
hey, thanks for your reply
actually no, STOCK 4.1.2 didnt have this issue, it started to show when I flashed 4.4.2 on it, is there some sort of fix for this or do I have to downgrade to JB? I'd rather stick to KK as I prefer it more.
on the other hand my dad hated google hangouts and he wants the stock messaging app back, I guess I can only go with CM
also I cant install a keyboard from the market, because I cant even log in to my google account, I cant get through the setup without a few things crashing over and over again, every second or so. the keyboard doesnt even show up

delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?

Rudjgaard said:
delete the latinIme.apk from the zip file you are trying to flash and substitute it with one from the other roms you tried flashing.
I know how to control the delay with which the ringer starts but not screen :s
These commands I think only help when call ends but it doesn't hurt to try, add them (or check the values if already present)
to build.prop in zipfile before you flash it
Code:
ro.lge.proximity.delay=5
mot.proximity.delay=5
I am on kitkat right now and have no lag issue...have you tried changing kernel?
Click to expand...
Click to collapse
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!

Pawelss said:
hey, thanks for your reply
I flashed Nameless ROM and surprisingly the lag issue is gone, and due to stripped gapps I flashed, I got the old messaging app back, which is quite the perfect combo, now the only thing I am missing is a good call recording app, is there a chance you can suggest one to me?
thanks again!
Click to expand...
Click to collapse
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good

tuncay_93 said:
Still havent tried nameless but i did red the thread about it. Seems everyone likes it. It should be good
Click to expand...
Click to collapse
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?

I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.

LGaljo said:
I want to tell you my experience about custom roms.
I don't know if you tried this combo: CM11 + kicos kernel (modified iodak's kernel) + minimal PA gapps
I works for me very well.
Click to expand...
Click to collapse
yeah, but shouldnt all the 4.4.2 ROMs be quite snappy? doesn't kitkat reduce the hardware requirements? why would JB work fine (or so I think, I'll go back to stock in a few mins and see) and KK be laggy as hell?
I've got a theory, I'm not a hardware guy and I dont know if I'm right or not, but:
could be that one of the cores is damaged and the system tries to switch some tasks to the damaged core (if android handles different cores the way I think) and that core doesnt really work the way it should, causing the entire system to work like a granny?

Pawelss said:
well I tried it out, the rom is nice and all, but my phone is extremely slow, the lag issue with phone calls is back, sometimes turning the screen off is impossible, or takes up to 2 minutes (!). turning it back on isnt much better either, I dont know what the problem is, the same thing happened on the BeanStalk ROM so I assume it isnt a software issue, but a hardware one, do you have any ideas what could be the problem and how can I solve it?
Click to expand...
Click to collapse
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.

tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
That still the best sollution for him - optimized kernel with stable ROM. He probably isn't techno freak?

tuncay_93 said:
This is probably some wake/lock problem with software. Also on my o2x i've noticed strange lag when i press the power key it has lag until the screen comes on buttons below the screen light and after a couple of seconds the screen. It has 4.3 CM rom there if your father is using this phone i would suggest you some stock based rom with custom kernel. They should not have problems like these.
Click to expand...
Click to collapse
could be, however, it isnt only for the power button, when the screen is off and a call is coming, it needs a few seconds for the screen to turn on, after the call is done, the system is all choppy and laggy. Turning the screen off after that is also nearly impossible, due to power button malfunction. I went back to stock for now and I'll see if the lag is gone, if it isnt, then its probably a hardware issue.
edit:
yeah, I'm on stock 4.1.2 and the issue isnt gone.
crap.

sounds like a problem in the timing the processor uses for scaling frequencies...
hav no idea what could be causing it unless you have some kernel tweak app and set wrong values

Have you tried clean flashing the Roms you installed? Have you Factory-Reset, Cleared cache, cleared Dalvik cache, and maybe did a system partition format before flashing?
Inviato dal mio GT-P3110 utilizzando Tapatalk

[Q] Fresh install of Slimkat lags terribly, what can I do?

Third Android phone and also 3rd older phone I've upgraded to 4.x. I basically went from stock, rooted, switched to new BL and fixed internal storage all using the O2X AIO tool, and finally flashed Slimkat (this http://forum.xda-developers.com/showthread.php?t=2551925).
It was great for about 30 minutes but then started to slow down badly so I froze a bunch of packages I don't use and have frozen on other devices without issue (using performance control tools). Speed went back up. But 30 minutes later it's back in the crapper. We're talking 30 seconds from power button to lock screen showing up. Stock camera takes a good 2 minutes to be ready to take a picture. Just now I was trying to set something in GPS Test and literally the statusbar clock was at 11:00 until at least 11:03 before I was like ok battery pull.
Anyone have any suggestions? Did I miss a step? I've been through all the related posts and everyone seems to love Slimkat. I'm coming from phones even older than this so I'm used to slow but come on...
Really appreciate any advice! Thanks!
Edit: I should mention I have installed FB Messenger with some modified permissions, Gmail, Now Browser, Root Browser, and Touchpal keyboard... That's all.

Hi. You should try to change to dalvik. ART is terrible for our phone!

Dalvik is default in the latest build

leekohlbradley said:
Dalvik is default in the latest build
Click to expand...
Click to collapse
I think that the memory is maybe running full, FB Messenger isn't always the best on memory usage/Battery usage and about the other apps I dont know, But There are apps which are resyncing, rerunning and which stay in background so it doesn't completely closes even if you do so.

Thanks for your reply! Actually afterward I switched OOM to aggressive (or something more aggressive, can't remember). Seems to be a lot better. I don't care about battery, I just want speeeeeeeed Oddly enough I still need to "double tap" the power button (!) to get it to wake. Weirdest thing.

If you're finding Slimkat at all slow then stop suffering and flash CM11 here http://forum.xda-developers.com/showthread.php?t=2769730
So much better! I used the 7/16 M1 version. Brilliant so far. GPS (my no.1 need) is also very fast.

But the date of you post ...
Sent from my LG-P990 using XDA Free mobile app

leekohlbradley said:
If you're finding Slimkat at all slow then stop suffering and flash CM11 here http://forum.xda-developers.com/showthread.php?t=2769730
So much better! I used the 7/16 M1 version. Brilliant so far. GPS (my no.1 need) is also very fast.
Click to expand...
Click to collapse
Sure ? Do u think that latest builds are fast ?

I haven't tried anything later than the June release by TonyP... There are other ppl putting out weeklies or something but honestly I'm looking for stable not bleeding edge
But the date of my post?

leekohlbradley said:
But the date of my post?
Click to expand...
Click to collapse
When I red first time, it was wrong (some day in 2007); now is right.
---------- Post added at 10:57 AM ---------- Previous post was at 10:50 AM ----------
leekohlbradley said:
Third Android phone and also 3rd older phone I've upgraded to 4.x. I basically went from stock, rooted, switched to new BL and fixed internal storage all using the O2X AIO tool, and finally flashed Slimkat (this http://forum.xda-developers.com/showthread.php?t=2551925).
It was great for about 30 minutes but then started to slow down badly so I froze a bunch of packages I don't use and have frozen on other devices without issue (using performance control tools). Speed went back up. But 30 minutes later it's back in the crapper. We're talking 30 seconds from power button to lock screen showing up. Stock camera takes a good 2 minutes to be ready to take a picture. Just now I was trying to set something in GPS Test and literally the statusbar clock was at 11:00 until at least 11:03 before I was like ok battery pull.
Anyone have any suggestions? Did I miss a step? I've been through all the related posts and everyone seems to love Slimkat. I'm coming from phones even older than this so I'm used to slow but come on...
Really appreciate any advice! Thanks!
Edit: I should mention I have installed FB Messenger with some modified permissions, Gmail, Now Browser, Root Browser, and Touchpal keyboard... That's all.
Click to expand...
Click to collapse
I had the same problem, so I had to uninstall it.:crying: