Even after re flashing ROMs, wiping dalvik cache, using ART, and using different ROMs/kernels, I always get a very noticeable lag (as if I use the powersave CPU governor) for around two minutes, until it suddenly becomes smooth...
I have heard this is a common problem, but I have not as of yet found a solution. Does anyone know what could be the cause?
Are you running stock, or a custom ROM? I haven't heard the problem on stock, but it's listed in the OP of many ROM threads as a known problem
Official cyanogenmod nightly ATM...
Sent from my Moto G using Tapatalk
That's a known issue.
Any current fix?
You can try restricting some startup apps which starts automatically after boot
Sent from my Moto G
Same problem here! I'm pleased there is someone else with the same issue as me! I've also tried many different ROM's, but the problem still persists. It's really annoying because it didn't used to happen, the problem only started when i swapped ROM's a couple of times. I am now using Carbon ROM, which didn't used to have this problem, but for some reason the issue is now present upon reinstallation over the standard US 4.4 Kitkat ROM.
V3-571G said:
Same problem here! I'm pleased there is someone else with the same issue as me! I've also tried many different ROM's, but the problem still persists. It's really annoying because it didn't used to happen, the problem only started when i swapped ROM's a couple of times. I am now using Carbon ROM, which didn't used to have this problem, but for some reason the issue is now present upon reinstallation over the standard US 4.4 Kitkat ROM.
Click to expand...
Click to collapse
Well, everybody who uses a CM based ROM has this issue. If it gets fixed in CM's source, all the other ROMs will have it fixed, too
@TheBananaz: you said it was a known issue, so do the developers know the cause of the regression?
All of the roms I have tried on our device does this. Not really sure why :/
Sent from my XT1031 using XDA Free mobile app
I'm not sure if they know why, but I can guarantee they're working hard to figure out why
I have lag on all roms apart from stock and slimkat.
this has been discussed in most of the threads relating to CM based roms, it's a well known issue
Is it posted in the official cyanogenmod ROM thread?
flash liquidsmooth it's a great rom and don't have that issue
Xup8 said:
flash liquidsmooth it's a great rom and don't have that issue
Click to expand...
Click to collapse
AnimeROM&AOKP works fine also, I like them more ^^
Sent from my Moto G using XDA Premium 4 mobile app
Related
I've been trying my best to avoid returning the phone, but mine is freezing 10-12 times a day. All require hard reboot. I rooted and put CWM on. Here's my question:
Is flashing a custom ROM (CM7, EB, or Bio2) going to fix the freezing issues?
Has anyone who had freezing issues fixed their problems with a ROM?
The leak seemed to work fine for me. No reboots & no lockups
Just a few minor bugs
Sent from my LG-P999 using XDA Premium App
Same problem here...I really like the style of the phone.
philthyman21 said:
The leak seemed to work fine for me. No reboots & no lockups
Just a few minor bugs
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
What Bugs do you mean? Minor?
trevor2k said:
I've been trying my best to avoid returning the phone, but mine is freezing 10-12 times a day. All require hard reboot. I rooted and put CWM on. Here's my question:
Is flashing a custom ROM (CM7, EB, or Bio2) going to fix the freezing issues?
Has anyone who had freezing issues fixed their problems with a ROM?
Click to expand...
Click to collapse
I had problems with the stock Froyo ROM, reboots etc, they pretty much disappeared after switching to the any of the other rom's here. It's easy to return the phone back to factory stock. IMHO, I'd recommend trying a few of the rooted rom's here first before returning it.
I have been searching for related issues to no avail.
Has anyone experienced graphical errors with roms that are running custom kernels? This seems to happen to me with any rom that has a custom kernel or whenever I install a custom kernel (one without any known issues) onto a rom. The latest would be related to incubus' latest ICS with the Ktoonz integrated kernel.
The errors start with a "loading swirl" that will glitch out from time to time, and eventually my icons and menus will stop showing up. This is using stock settings on the kernels. The problems are the exact same no matter the rom, as long as a custom kernel is being used.
I get these problems even after full wipes and md5 checks, could this be hardware related?
Thanks for reading, this is driving me nuts as I have always been a hardcore OCer and it's really bumming me out that I can't tweak my S3
Any suggestions or ideas, let me know !! :good:
madeiracam said:
I have been searching for related issues to no avail.
Has anyone experienced graphical errors with roms that are running custom kernels? This seems to happen to me with any rom that has a custom kernel or whenever I install a custom kernel (one without any known issues) onto a rom. The latest would be related to incubus' latest ICS with the Ktoonz integrated kernel.
The errors start with a "loading swirl" that will glitch out from time to time, and eventually my icons and menus will stop showing up. This is using stock settings on the kernels. The problems are the exact same no matter the rom, as long as a custom kernel is being used.
I get these problems even after full wipes and md5 checks, could this be hardware related?
Thanks for reading, this is driving me nuts as I have always been a hardcore OCer and it's really bumming me out that I can't tweak my S3
Any suggestions or ideas, let me know !! :good:
Click to expand...
Click to collapse
Since you said your not running any overclocked GPU kernels (Correct?) that could cause artifacts and other related glitches, it sounds to me like that is a hardware issue. What kernel are you currently running, cause if you provide me a link to it I can double check the change log for you and make sure you didn't accidentally miss any problems that were reported or bugs .
shimp208 said:
Since you said your not running any overclocked GPU kernels (Correct?) that could cause artifacts and other related glitches, it sounds to me like that is a hardware issue. What kernel are you currently running, cause if you provide me a link to it I can double check the change log for you and make sure you didn't accidentally miss any problems that were reported or bugs .
Click to expand...
Click to collapse
Not running a kernel with an OCed GPU afaik. I have had issues running any of beans custom stock roms when I select the custom kernel in aroma, all of imoseyens custom kernels have caused the same graphical error, and running incubus' latest "[ROM] JellyBomb ICS [VZW] [VRALHE] [RLS3] [10/21/12] By Incubus26Jc" with the integrated ktoons has also caused the same graphical glitches.
I am assuming inc is using the latest ICS version found here http://forum.xda-developers.com/showthread.php?t=1853816
No one else seems to be having these issues except one person I stumbled across in a beans thread a while back. I sure hope it's not hardware
I'm having a similar error, except with certain games.
madeiracam said:
Not running a kernel with an OCed GPU afaik. I have had issues running any of beans custom stock roms when I select the custom kernel in aroma, all of imoseyens custom kernels have caused the same graphical error, and running incubus' latest "[ROM] JellyBomb ICS [VZW] [VRALHE] [RLS3] [10/21/12] By Incubus26Jc" with the integrated ktoons has also caused the same graphical glitches.
I am assuming inc is using the latest ICS version found here http://forum.xda-developers.com/showthread.php?t=1853816
No one else seems to be having these issues except one person I stumbled across in a beans thread a while back. I sure hope it's not hardware
Click to expand...
Click to collapse
Recon0212 said:
I'm having a similar error, except with certain games.
Click to expand...
Click to collapse
Interesting that both of you seem to be having somewhat similar problems, it may not be a hardware issue then after all. Some phones just don't like custom kernels and don't play nicely with them at all. For example my trusty old Droid 1 wouldn't boot if I used ULV kernels (Except for Deprimed kernel), I had to use LV kernels or above. If wanted to you could try running CM10 and see how that goes for you.
shimp208 said:
Interesting that both of you seem to be having somewhat similar problems, it may not be a hardware issue then after all. Some phones just don't like custom kernels and don't play nicely with them at all. For example my trusty old Droid 1 wouldn't boot if I used ULV kernels (Except for Deprimed kernel), I had to use LV kernels or above. If wanted to you could try running CM10 and see how that goes for you.
Click to expand...
Click to collapse
Thanks for the info, I am going to try experimenting w/ CM and report back , thanks!
shimp208 said:
Interesting that both of you seem to be having somewhat similar problems, it may not be a hardware issue then after all. Some phones just don't like custom kernels and don't play nicely with them at all. For example my trusty old Droid 1 wouldn't boot if I used ULV kernels (Except for Deprimed kernel), I had to use LV kernels or above. If wanted to you could try running CM10 and see how that goes for you.
Click to expand...
Click to collapse
I have seemed to fix the issue, it turns out that my major issue was the undervolting that comes with most custom kernels. The trick was to change settings before things got too out of whack... Hopefully this might help some others as well.
madeiracam said:
I have seemed to fix the issue, it turns out that my major issue was the undervolting that comes with most custom kernels. The trick was to change settings before things got too out of whack... Hopefully this might help some others as well.
Click to expand...
Click to collapse
Glad to see you were able to fix the problem
I am posting it for first time but have tried many ROMs since GB ROMs on my skyrocket. I am not yet allowed to post this question on dev's ROM page. Recently I flashed Sky-Jelly-Bean ROM from Sean T11 beta. While the WiFi worked fine before flashing the 11.2 update, it became flaky after I flashed the update. Every 10 minutes or so it would switch to cell network and back to WiFi. This seriously impacts any downloads or streaming. Same happened with T10 base as well. I didn't notice it on T7.1 though.
I noticed this issue at home and at work. I had full WiFi signal when I had it. But still it switches to cell network about every 10 mins.
I did wipe cache and dalvik 5X before flashing the update. Fixed permissions too. Using TWRP open recovery for flashing the ROMs. Is anyone else noticing the same issue? Any help would be much appreciated.
Thanks Sean for another wonderful ROM. I have been flashing all your ROMs and updates since GB ROMs on my skyrocket. None of them failed to impress me.
wait continues...
I have to wait for 9 more posts to start posting the questions directly in dev's ROM pages.
It's a beta. He stated if you want a flawless Rom go back to 7.1
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Yeah, I took the risk with the beta. But I had the same issues with T10 as well. I wanted to know if anyone is facing similar issues or is it only me. Are you on T11? Do you see any similar issues?
Sent from my skyrocket
I have no issues with wifi with T11.2
I don't have WiFi issues using T11.3
Sent from my SAMSUNG-SGH-I727 using xda premium
raj3366 said:
Yeah, I took the risk with the beta. But I had the same issues with T10 as well. I wanted to know if anyone is facing similar issues or is it only me. Are you on T11? Do you see any similar issues?
Sent from my skyrocket
Click to expand...
Click to collapse
No I don't use that Rom, sorry man.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I went and fixed permissions for few times and now the frequency of the problem has reduced, but not completely. I guess I have to live with that for now. Hoping future updates or ROMs from sean might fix it.
Thanks all for responding.
Sent from sky
Dose anyone know where I can get a different boot animation for the sky jelly bean? To like the nexus one or the original jelly bean animation?
Try a different radio or reflash the current one.
Sent from my SAMSUNG-SGH-I727 using xda premium
I had that issue on UCLF6 and tried UCLI3. But both had the same issue.
As I mentioned before, it got much better after fixing permissions for few times. I can live with it until 4.2 updates come.
Sent from Milky way
CaLLm3LAzY- said:
Dose anyone know where I can get a different boot animation for the sky jelly bean? To like the nexus one or the original jelly bean animation?
Click to expand...
Click to collapse
You might want to post this directly under Sean's SkyJelly bean thread if you are using his ROMs.
Btw, someone in that thread mentioned that the ROM stopped working after flashing a new boot animation. You might want to search around a bit before playing with flashing boot animations.
<<<<<
Originally Posted by kamui957 View Post
Really liked this rom, then after flashing a new boot animation it stopped working completely, and now even when I wipe it completely it still will not boot. Formated cache, system, data, etc 5x and then flashed just the base 5.0 rom, Nothing. Flashed back to Sky ICS just fine. Flashed to other JB based roms fine, but this one just won't flash. Kinda sad really.
>>>>>
I was just wondering whether there are any 4.4 roms available? The only one I found was CM but I feel like there must be more. I might be just going blind, however I could not see any other roms. Any links or suggestions are appreciated. Thank you.
mefistofel666 said:
I was just wondering whether there are any 4.4 roms available? The only one I found was CM but I feel like there must be more. I might be just going blind, however I could not see any other roms. Any links or suggestions are appreciated. Thank you.
Click to expand...
Click to collapse
nope those 3 build threads are it
I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)
SSPENCER10 is working very well for me. Everything he is putting out is stable and appears to be having fewer issues than KitKang. It is even working just as well with ART as it was with Dalvik. The 11-23 build also has the new CM11 boot animation.
markdapimp said:
I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)
Click to expand...
Click to collapse
You realize they are all based on exactly the same code right?
And you realize that if one makes 'progress' they all make 'progress' because they use the same code right?
[ROM][4.3.1][Official][OSE Rom][d2vzw]
I'm using this one and so far so good.
It has nightlies that have 4.4
I'd recommend KitKang. It's been extremely stable and has really good battery life. ART works very well.
Sent from my SCH-I535 using Tapatalk
KitKang!!
Second that!!
Sent from my SCH-I535 using xda app-developers app
markdapimp said:
I suggest using kitkang http://forum.xda-developers.com/showthread.php?t=2525831
as its the latest rom with Nightlys going on every night
and seems to be the only one making progress so far (FCC,SD,Overall UI smoothness,Video GPU performance)
Click to expand...
Click to collapse
Summary: I don't think KitKang is recognizing my SIM card, and is causing "Phone" to crash every second or two.
Hey guys, I tried flashing the latest KitKang ROM last night, but ran into a big issue. I wiped system, cache, dalvik cache, etc. I then reflashed the MF1 firmware (it was already flashed, but for some reason I always feel better re-flashing it every time.) Then I flashed the latest KitKang D2VZW nightly linked above, and flashed the GApps mentioned in that thread too. However, upon rebooting, every second or so it would say "phone has forced closed" (or something along those lines. Also, there was no signal. I got through the setup process after a VERY long time of pressing "okay" to that error and setting up my CM and Google accounts with one key in between each error. I thought I would be able to go into Mobile Networks and change the settings, which fixed certain early issues with CM10.1 or 10.2, but to no avail. I then tried reflashing (after wiping clean) CM10.2 again to get certain files for the phone to work, then flashing CM11 over that, and it seemed to work up until it freezes after getting to the home screen. Any thoughts on what the issue may be and/or how to fix it?
Thanks!
Sent from my SCH-I535 using xda app-developers app
Am i the only one experiencing touch screen issues like ghost touches and screen not being responsive sometimes? :/
No, you're not, its a pretty common issue, and I haven't been able to fix it.
Sent via Telnet
This thing is so frusturating, I have to reboot my mobile everytime when this happens :/
Found this while I made a search to increase touch sensitivity. I guess it's worth a try; or you guys can just disassemble to check if this is the issue.
http://forum.xda-developers.com/showthread.php?p=56996136
Sent from my Moto G using XDA Free mobile app
---------- Post added at 09:51 AM ---------- Previous post was at 09:48 AM ----------
Or it can also be this. It is on the same thread as the one given before.
http://forum.xda-developers.com/showthread.php?p=58830708
Sent from my Moto G using XDA Free mobile app
Hameedhudeen said:
This thing is so frusturating, I have to reboot my mobile everytime when this happens :/
Click to expand...
Click to collapse
What ROM are you on?
I had it really bad with CM12 but went back to Stock 11s and it's not noticeable to me anymore. I know it's likely a hardware problem but they have apparently baked a few software fixes into the stock ROM. Made my phone usable again, no more reboots needed
Maybe Firmware matters
I have had this issue ranging from different roms. As I have been frequently changing ROMs and kernels, I have found that this issue doesn't persist.
Is it the touch firmware or kernel? I may not know. But here is my experience:
1. CM11 : Faced touch issue uptil 44S
2. CM12: Stock, built myself. Faced loads of issues not only with touch
3. CM12 SlimSaber: Never faced an issue till date.
And if reboot really works, then it must be a software issue.
Im currently on official cm12. Here the issue is not too intense it only happen if i keep it tightly in my jean packets.
In miui, the issue was soo frequent.
Ill try switching to slimsaber now.
Screen responsiveness seems to be stable in slimsaber, but that rom lacks much features.
Damn , Why cant Cm just identify and fix this thing -_-
Update:
Even slimsaber has this issue
Hameedhudeen said:
Update:
Even slimsaber has this issue
Click to expand...
Click to collapse
I also have this issue from couple of weeks. Touch unresponsiveness and ghost touches. Typing is a nightmare. I've tried everything from going to CM11s stock to flashing old firmwares but nothing. Waiting for offical CM12 now.
So I have to go back to kitkat? Bleh.
Update:
Flashed CM 11s 44s and franco kernel. Havent had a single touch issue till now. Been using for almost 2 days.
Hameedhudeen said:
Update:
Flashed CM 11s 44s and franco kernel. Havent had a single touch issue till now. Been using for almost 2 days.
Click to expand...
Click to collapse
Are you still good with CM11S, or have the ghost touches re-appeared?
kalpik said:
Are you still good with CM11S, or have the ghost touches re-appeared?
Click to expand...
Click to collapse
Was good till the last moment.
Now im on Cm12s, this is as good as cm11 44s