Related
My 2.1 powered Hero is having a few speed problems, and one of them is that when my phone is ringing, the vibrator continues shortly after I've picked up. Quite annoying for both me and the caller. One time it didn't stop, not even after I hung up again, I had to shut down then phone completely!
So does anyone have suggestions how to fix this? I guess its a lag problem because the phone feels slow other times aswell, for example now when typing.
The problem is my phone's not even filled up with Apps etc, and I use an appkiller. Also the problem is there almost right after I reboot the phone.
I use the original HTC Rom running android 2.1. Have replaced sense with launcherpro though regarding the homecreens and appdrawer.
Sent from my HTC Hero using XDA App
bjoernbertelsen said:
My 2.1 powered Hero is having a few speed problems, and one of them is that when my phone is ringing, the vibrator continues shortly after I've picked up. Quite annoying for both me and the caller. One time it didn't stop, not even after I hung up again, I had to shut down then phone completely!
So does anyone have suggestions how to fix this? I guess its a lag problem because the phone feels slow other times aswell, for example now when typing.
The problem is my phone's not even filled up with Apps etc, and I use an appkiller. Also the problem is there almost right after I reboot the phone.
I use the original HTC Rom running android 2.1. Have replaced sense with launcherpro though regarding the homecreens and appdrawer.
Click to expand...
Click to collapse
It sounds like a typical Sense UI issue...very laggy. Easiest solution is to root your phone, and install another ROM. CM6 is great, and it will get you up to FroYo (2.2). The lag will be gone, and your phone will work much better.
I was kind of hoping that wasn't necessary, but maybe I'll give it a try. Any link to the easiest way to install a custom rom? Don't know how to although I've read a lot of confusing guides a while ago.
Sent from my HTC Hero using XDA App
BTW is there a way to remove/disable sense on my hero and go so stock android with launcher Pro, WITHOUT rooting and flashing a custom rom? So its easy to go back to sense if I think stock android is too ugly?
Sent from my HTC Hero using XDA App
You dont NEED any kind of killer. Get rid of your junk apps, just delete them all. Disable all the vibrate options for everything(may not be necessary) and reboot. Run some tests. Is there a process popping that you think causes it? Delete its source.
bjoernbertelsen said:
I was kind of hoping that wasn't necessary, but maybe I'll give it a try.
Click to expand...
Click to collapse
You won't regret it one bit Trust me...
bjoernbertelsen said:
Any link to the easiest way to install a custom rom?
Click to expand...
Click to collapse
CM6 is my favorite. Here's the link http://forum.xda-developers.com/showthread.php?t=755795
Root - Do a Nandroid backup in case you ever want to go back - Wipe Data - Flash - Enjoy
Where can I find a stock Gingerbread ROM at? When I purchased my phone it already had ICS on it, and honestly I do not like it at all. I jumped to my favorite phone mod site (XDA) and did some searching but came up empty handed. Can anyone assist me with my request? Thanks!
qtipextra said:
Where can I find a stock Gingerbread ROM at? When I purchased my phone it already had ICS on it, and honestly I do not like it at all. I jumped to my favorite phone mod site (XDA) and did some searching but came up empty handed. Can anyone assist me with my request? Thanks!
Click to expand...
Click to collapse
Sorry. There are not any GB ROMs for the D4 that will work on ICS. The GB D4 ROMs there are are not compatible with the ICS kernel. Maybe if you can describe the issues you are having with ICS we can help you with those.
Sent from my XT894 using Tapatalk 2
Mainly just nitpicking things, but the one thing I've had an issue with ICS is the fact that I cannot link notification and ringer volumes together.
Another issue I'm having is when typing using the hardware keyboard, I'll be typing something and the cursor will
jump and start typing at the beginning. Happened just as I was typing this reply, too.
qtipextra said:
Mainly just nitpicking things, but the one thing I've had an issue with ICS is the fact that I cannot link notification and ringer volumes together.
Another issue I'm having is when typing using the hardware keyboard, I'll be typing something and the cursor will
jump and start typing at the beginning. Happened just as I was typing this reply, too.
Click to expand...
Click to collapse
That is odd stock ICS does not have the functionality to link notification and ringer volume. You should be able to find an app on the market that will give you this functionality. Found this on another forum with a quick google search: "Get cvolume from the market. Under settings you need to check notification volume not(Use incoming call volume for notifications). Works great" aarong03 - DroidForums
There are other volume control apps out there as well that may have similar functions. Try some out and let us know!
Not sure about the cursor jumping on you. It seems like I had this problem once too and it ended up being something I was doing that was causing it but I cannot think for the life of me what it was. Some button I was hitting or something.
kwyrt said:
That is odd stock ICS does not have the functionality to link notification and ringer volume. You should be able to find an app on the market that will give you this functionality. Found this on another forum with a quick google search: "Get cvolume from the market. Under settings you need to check notification volume not(Use incoming call volume for notifications). Works great" aarong03 - DroidForums
There are other volume control apps out there as well that may have similar functions. Try some out and let us know!
Not sure about the cursor jumping on you. It seems like I had this problem once too and it ended up being something I was doing that was causing it but I cannot think for the life of me what it was. Some button I was hitting or something.
Click to expand...
Click to collapse
Thanks for the information. I have tried many volume apps that claim to link the volumes together, but do not work. I basically just want to use my hardware volume buttons as a master volume control, so when I set it with the hardware buttons, nothing is higher. or lower than that volume. I had a Samsung captivate glide on att that was running GB and the app that I used on that phone did not work on my D4 for linking volume. I tried this cvolume app and it doesn't seem to be working either, even though the option to link them is set.
qtipextra said:
Thanks for the information. I have tried many volume apps that claim to link the volumes together, but do not work. I basically just want to use my hardware volume buttons as a master volume control, so when I set it with the hardware buttons, nothing is higher. or lower than that volume. I had a Samsung captivate glide on att that was running GB and the app that I used on that phone did not work on my D4 for linking volume. I tried this cvolume app and it doesn't seem to be working either, even though the option to link them is set.
Click to expand...
Click to collapse
I use audio manager pro. It costs about $3 but is well worth it - Play Store
-
There is also a free version that just doesn't allow saving of profiles.
azrael293 said:
I use audio manager pro. It costs about $3 but is well worth it - Play Store
-
There is also a free version that just doesn't allow saving of profiles.
Click to expand...
Click to collapse
I've been using AudioGuru for profile selection, but I would much rather be able to dynamically change the volume of notifications and ringer together from the hardware buttons instead of set profiles with defined volume levels at each.
I have not found an app yet that works on this phone/ICS that works to lock both volumes together.
Perhaps I will just have to wait until JB is officially released for our phones. But I really liked GB on my previous phone, its too bad I can't get a ROM to work from ICS to GB, considering that the phone was originally released with GB.
Another thing I don't like about ICS is the stock messaging only let's you save a maximum of 1000 messages per contact. I would prefer messages never get automatically deleted, and in ICS it cannot be disabled, you can only change the max number of kept messages.
If you attempt to downgrade the phone to official GB there is a very high risk of bricking the phone.
I'd recommend you stop trying to do this and instead try to either get used to ICS or to replace the bits you don't like with some 3rd party apps.
I'm always having that cursor problem with the keyboard. Happens whenever I open up the keyboard and immediately start typing. Wait a second or two before typing, and it's usually ok. Seems the input editor is too slow to initialize itself, so it's still trying to set the cursor to column zero by the time you start typing...
Sent from my DROID4 using Tapatalk
If you need to back to gingerbread dowlnoad official moto ginger software
http://sbf.droid-developers.org/cdma_maserati/list.php
niko99 said:
If you need to back to gingerbread dowlnoad official moto ginger software
http://sbf.droid-developers.org/cdma_maserati/list.php
Click to expand...
Click to collapse
did you try yourself before suggesting?
There is no risk in downgrading to GB via SBF. No risk, because you will most certainly B R I C K your phone. So learn to live with it.
I too have some issues with ICS. The cursor jump happens to me too, and I hate it. I also have issues with BT volume control. Music is no problem, but controlling Youtube volume does not work for me. And when docked (lapdock or plain HDMI cable) volume also doesn't work. On or off, nothing in between.
But still, I think ICS runs much smoother than GB.
with locked bootloader is unable to brick droid ( always is way to get back phone to life) but ppl must know what ar they doing
niko99 said:
with locked bootloader is unable to brick droid ( always is way to get back phone to life) but ppl must know what ar they doing
Click to expand...
Click to collapse
Yes you can (maybe) bring your phone back to life, but one thing that will definitely not happen is that Gingerbread ROM actually booting. The locked bootloader does not allow you to downgrade.
Do not even bother trying to downgrade it will waste your time and you may end up with a brick.
highlandsun said:
I'm always having that cursor problem with the keyboard. Happens whenever I open up the keyboard and immediately start typing. Wait a second or two before typing, and it's usually ok. Seems the input editor is too slow to initialize itself, so it's still trying to set the cursor to column zero by the time you start typing...
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Die Bruine said:
There is no risk in downgrading to GB via SBF. No risk, because you will most certainly B R I C K your phone. So learn to live with it.
I too have some issues with ICS. The cursor jump happens to me too, and I hate it. I also have issues with BT volume control. Music is no problem, but controlling Youtube volume does not work for me. And when docked (lapdock or plain HDMI cable) volume also doesn't work. On or off, nothing in between.
But still, I think ICS runs much smoother than GB.
Click to expand...
Click to collapse
At least I know I am not the only one with the cursor jump issue. And yes, I notice it only happens to me when I open the keyboard and immediately start typing. I will have to start being patient and give it a few seconds before typing.
I've tried many different Volume apps, and even when locking volume settings are enabled, the volumes are not locked when I adjust it with the hardware volume rocker.
I did read that JB will be getting an official push to the D4, but they have not said when. ICS just doesn't set too well with me for some reason. Yes, it runs pretty smooth, but I don't like it's all black theme, some functionality that was left out, and the new widget being part of the app list doesn't always show new widgets immediately. I guess my biggest upset about it is that it seems rather... buggy or undeveloped. To me, GB seemed to be more developed and work the way you would come to expect an android OS to run now days, and ICS just isnt there yet. Hopefully JB will be better...
niko99 said:
with locked bootloader is unable to brick droid ( always is way to get back phone to life) but ppl must know what ar they doing
Click to expand...
Click to collapse
I bricked my first droid 4 without problems with locked bootloader. do you want a link I sell it for parts?
olegfusion said:
I bricked my first droid 4 without problems with locked bootloader. do you want a link I sell it for parts?
Click to expand...
Click to collapse
unless you borked your bootloader or had a hardware failure niko is right there is no way to hard brick your phone just by flashing roms/sbf's
as long as your bootloader is intact you are able to recover your device
All that said, there's no reason someone couldn't get a vanilla AOSP GB build working with the ICS kernel for use with safestrap. On the XDAndroid project we had a single Linux 3.5 kernel working for Froyo, GB, and ICS. It's not a slamdunk, but the amount of patching required isn't that bad.
Sent from my DROID4 using Tapatalk
I'm doing research for a friend's phone. He has the AT&T HTC Vivid. My old phone actually. I have yet to root it or do any of the dirty work as I am concerned with the stability and flaws in ROMs for this device. A little advice would be appreciated.
I have read about the Dirty Unicorn ROM with the Pac kernel (or since updated stock kernel). They say the volume is fixed in this ROM. Can anyone confirm?
Also would like to know of other ROMs and what is available out there through others advice. I want to find him stable as he cannot be flashing daily the way I can. I have seen lots of bluetooth issues called out. I am more concerned with stability, call volume, and definitely good data/wifi. Someone point me in the right direction perhaps?
I would love to see Sense gain more support for this device, but I'm not a dev so I'm sure it's no easy task. I have used CM alot in the past, and loved most of it, but it always had its bugs so I hesitate to flash without gathering information.
Thanks guys.
acw928 said:
I'm doing research for a friend's phone. He has the AT&T HTC Vivid. My old phone actually. I have yet to root it or do any of the dirty work as I am concerned with the stability and flaws in ROMs for this device. A little advice would be appreciated.
I have read about the Dirty Unicorn ROM with the Pac kernel (or since updated stock kernel). They say the volume is fixed in this ROM. Can anyone confirm?
Also would like to know of other ROMs and what is available out there through others advice. I want to find him stable as he cannot be flashing daily the way I can. I have seen lots of bluetooth issues called out. I am more concerned with stability, call volume, and definitely good data/wifi. Someone point me in the right direction perhaps?
I would love to see Sense gain more support for this device, but I'm not a dev so I'm sure it's no easy task. I have used CM alot in the past, and loved most of it, but it always had its bugs so I hesitate to flash without gathering information.
Thanks guys.
Click to expand...
Click to collapse
No DU just fixes The volume increase decrease while in a call
If you care about in call volume try a sense 4.1 rom or a sense 3.6 rom
Ok. I knew that answer was coming. How bad is the volume thing? My main goal is just to not have to flash his phone 100 times. If it was my phone, as I already do.. I would flash and play with it for weeks before I chose a ROM. It's not an ideal option for this, though. I don't even want mess with internals if it's not for a clear upgrade.
Is there ongoing work in your CM builds to figure out these in-call volume issues?
bilibox said:
No DU just fixes The volume increase decrease while in a call
If you care about in call volume try a sense 4.1 rom or a sense 3.6 rom
Click to expand...
Click to collapse
acw928 said:
Ok. I knew that answer was coming. How bad is the volume thing? My main goal is just to not have to flash his phone 100 times. If it was my phone, as I already do.. I would flash and play with it for weeks before I chose a ROM. It's not an ideal option for this, though. I don't even want mess with internals if it's not for a clear upgrade.
Is there ongoing work in your CM builds to figure out these in-call volume issues?
Click to expand...
Click to collapse
It's always going to be work. and for me my volume is just fine. In call works loud enough for me. But everyone has their own preferences. Other people cant use the roms due to the volume issue
To answer your question... I would put CM10.1 from albinoman... Prolly the most stable we gots
Sent from my Vivid 4G using Tapatalk 4
acw928 said:
Ok. I knew that answer was coming. How bad is the volume thing? My main goal is just to not have to flash his phone 100 times. If it was my phone, as I already do.. I would flash and play with it for weeks before I chose a ROM. It's not an ideal option for this, though. I don't even want mess with internals if it's not for a clear upgrade.
Is there ongoing work in your CM builds to figure out these in-call volume issues?
Click to expand...
Click to collapse
I have an AT&T Vivid, and have had varied results in this department. Though, I work in a server room/data center, so I have more ambient noise to contend with, but I've experienced horridly low volume on some builds all the way to just less that stock quality. The first ROM I experienced this on was a Sense 4.1 ROM, but also experienced it in different ways with aosp/aokp builds as well. I don't know if it is related, but I did notice a significant increase in the in call volume after performing the S-OFF wire trick. Though that could just be a coincidence. But one common theme I have found, is when the in call volume has been low, don't even attempt speakerphone use. As when I did, it either didn't work at all (or so low it's inaudible) and then when returning to the earpiece, 6/10 times (guesstimate) the issue of no volume followed for the duration of the call. And the odds would increase when activating speaker before the call is answered on the other end (making calls). However, I must say that I the in call volume using bilibox's unofficial rootbox, I do not experience the low in call volume, but the speakerphone is (mostly) useless. (Still an awesome ROM though, just waiting for mobile data fix )
Not sure if my ramble is helpful or not, but those are summed up experiences I've had thus far. If you really just want it to work without goofing with anything, I 'd recommend either a rooted/modified/de-bloated stock ROM.
There's my 2 cents {plunk plunk}
I'm running TD 9.1, and prior was on 8.0. Tried both stock kernel, and a few other ones with no luck. At first when the sounds starts playing, the left speaker works fine, then with in a sec, it will fad to almost nothing. Is this something someone else has encountered? For all I know it has been like this since day one.. But I don't believe so.
Edit: I have also tried clean installs. i have not tried other roms yet.
Double edit: My xda search is not working, but google did for me. Found one other person having somewhat the same issue, but it was never answered. I hate to bump an old tread like that, after i have posted mine already.
[Q] HTC One speaker problem - One speaker turning off / mono sound
vwmaniacx said:
I'm running TD 9.1, and prior was on 8.0. Tried both stock kernel, and a few other ones with no luck. At first when the sounds starts playing, the left speaker works fine, then with in a sec, it will fad to almost nothing. Is this something someone else has encountered? For all I know it has been like this since day one.. But I don't believe so.
Edit: I have also tried clean installs. i have not tried other roms yet.
Double edit: My xda search is not working, but google did for me. Found one other person having somewhat the same issue, but it was never answered. I hate to bump an old tread like that, after i have posted mine already.
[Q] HTC One speaker problem - One speaker turning off / mono sound
Click to expand...
Click to collapse
I have the exact same issue. Tried million ROMs, sound patches and tricks but nothing change. The easiest way to see the difference between the two speakers is to run the Audio Test using HTC Function Test by dialing *#*#3424#*#*
Finally, I managed to get S-Off and now I'm going to get back to 100% stock flashing RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe, I'll do the test again and update the post.
EDIT: I'm full stock and it didn't fix it I guess I have to send it back...
BTW, what did you do? Did you fixed yours?
Running Sinless 5.1.5 now with elemental, everything works 100%. I guess for some reason my phone just didn't like TD, we all know they have a personality of there own..
Sorry for the long wait before response, I don't pay attention very well.
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