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
Related
Hi, I know there's no such thing as the "best" ROM, it depends entirely on taste and on what you're expecting. So, I'm searching for a 2.3.4, stable, as fast as possible ROM with no particular tweaks if not for increasing speed and memory...should I simply go with a deodexed stock or is there something better speedwise? Thank you in advance!
Ricpu said:
Hi, I know there's no such thing as the "best" ROM, it depends entirely on taste and on what you're expecting. So, I'm searching for a 2.3.4, stable, as fast as possible ROM with no particular tweaks if not for increasing speed and memory...should I simply go with a deodexed stock or is there something better speedwise? Thank you in advance!
Click to expand...
Click to collapse
I would also like to get this tip...Speed increase and more available memory, maybe some tweaks in the notification bar, but besides that I would like to keep my phone pretty much in stock form.
If speed tweaks are all you want with very high stability, check out: http://forum.xda-developers.com/showthread.php?t=1065392
His ROM (When he reposts it) is very stable and very fast.
Install that with James Bond or Netarchy kernel and you'll have a very fast/stable setup.
Ok, great, thanks!
aerobahn said:
If speed tweaks are all you want with very high stability, check out: http://forum.xda-developers.com/showthread.php?t=1065392
His ROM (When he reposts it) is very stable and very fast.
Install that with James Bond or Netarchy kernel and you'll have a very fast/stable setup.
Click to expand...
Click to collapse
Thanks for the tip! That ROM seems to be exactly what I want.
Can I add shortcuts or power controls to the pull down notification bar with a separate app, or should they be cooked to the ROM? If I can could somebody point me to the right directionwhere I could find this kind of separate app? Thanks!
If you want something a little more customized, but still pretty stock, you could try the infin1ty ROM. I've been using it for a while now, it is very quick and very stable. The dev is also very involved and posts regular updates about new features and bug reports.
Linky
I would suggest you to use SupeASOP v8.0.
I find that rom is the best after i tried different roms.
Cm7 is good but not to my expectation.
I would recommend you to try SupeASOP v8.0 with kernel of Netarchy Nexus - 1.3.0.12-cfs-2.3.4-universal (Universal for non-stock 2.3.4 roms).
Link to SupeASOP ROM: http://forum.xda-developers.com/showthread.php?t=1007267
Link to Netarchy Nexus Kernel : http://forum.xda-developers.com/showthread.php?t=936219
I flashed this one:
http://forum.xda-developers.com/showthread.php?t=1060192
Rooted it by flashing su (before rebooting):
http://forum.xda-developers.com/showthread.php?t=682828
And, after first reboot I flashed Netarchy kernel (CFS 2.3.4 stock):
http://forum.xda-developers.com/showthread.php?t=936219
BLAZING fast...much faster (at least in my everyday use) than anything else I've tried...battery life also seems really good...thank you guys!
Why do you prefer this rom?
Sent from my Desire HD using XDA App
window7 said:
I would suggest you to use SupeASOP v8.0.
I find that rom is the best after i tried different roms.
Cm7 is good but not to my expectation.
I would recommend you to try SupeASOP v8.0 with kernel of Netarchy Nexus - 1.3.0.12-cfs-2.3.4-universal (Universal for non-stock 2.3.4 roms).
Link to SupeASOP ROM: http://forum.xda-developers.com/showthread.php?t=1007267
Link to Netarchy Nexus Kernel : http://forum.xda-developers.com/showthread.php?t=936219
Click to expand...
Click to collapse
Sorry, I mean SupeASOP
Sent from my Desire HD using XDA App
Ok, this rom is working great, but I get a force close when I try to make a video chat on talk...audio chat is fine...I saw many users had this problem on nexus s but I haven't understood if it's a rom related problem or a general problem with 2.3.4 on this phone...any suggestions?
Ricpu said:
Ok, this rom is working great, but I get a force close when I try to make a video chat on talk...audio chat is fine...I saw many users had this problem on nexus s but I haven't understood if it's a rom related problem or a general problem with 2.3.4 on this phone...any suggestions?
Click to expand...
Click to collapse
I don't know much about your ROM, but there was/is an issue where you have to have your volume all the way down before you start a video chat on talk. Some ROMs have it fixed, some don't. Also, some ROMs have an issue where only the back camera works with video chat.
I know most devs are working on incorporating the fix for talk into their ROMs. If it is a deal breaker for you, take a look around at different ROMs, we are very fortunate to have many active and talented devs working on various ROMs.
Sent from my infin1ty rom Nexus S.
Ok, thank you!
I've been googling and browsing XDA most of today... went on a short adventure in unlocking my Xoom and rooting it (finally), and am even happier with it running 4.0.4.
However short of flashing entire new roms and all that jazz, I think I'd like to overclock a bit.
From what I've found, it seems like there isn't many options for doing that yet? I've just setup and restored all my apps and widgets today so I'm hesitant to wipe everything again, so my question is:
Am I able to overclock presently? After rooting I now have some experience navigating to CWM, and kind of understand the process. Just want to make my Xoom that much better
Thanks!
edit: if there is a way to do it... perhaps some instructions would be great? Everytime I look at those Development threads I get so confused.
Option 1: flash a custom ROM. Most ROMs have an overclocking kernel installed.
Option 2: flash the EOS kernel. You can find it in the development section.
Also, since you are already on ICS 4.0.4, all you have to wipe is the caches when you install a different ICS ROM, such as AOKP, CM9 or Team EOS.
Sent from my MB860 using xda premium
d3athsd00r said:
Option 1: flash a custom ROM. Most ROMs have an overclocking kernel installed.
Option 2: flash the EOS kernel. You can find it in the development section.
Also, since you are already on ICS 4.0.4, all you have to wipe is the caches when you install a different ICS ROM, such as AOKP, CM9 or Team EOS.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Thanks for the reply!
Seems like this thread is most relevant?
http://forum.xda-developers.com/showthread.php?t=1484770
Not sure what to use though, as it seems to be more about the rom.
For wiping the caches, do I still need to do it if I flash a kernel? Before or after? I might try switching roms in the future but I'd like to try just the kernel now.
edit: http://forum.xda-developers.com/showthread.php?t=1488059 okay I did some googlng and JUST flashed this. Fingers crossed! This must seem silly, but it's my first time flashing a kernel so I'm nervous.
edit2: Woo I'm running at 1.7ghz! Thanks for the help! Hm restarted, maybe 1.7 is too high. Will experiment with lower...
Jeffu said:
Thanks for the reply!
Seems like this thread is most relevant?
http://forum.xda-developers.com/showthread.php?t=1484770
Not sure what to use though, as it seems to be more about the rom.
For wiping the caches, do I still need to do it if I flash a kernel? Before or after? I might try switching roms in the future but I'd like to try just the kernel now.
edit: http://forum.xda-developers.com/showthread.php?t=1488059 okay I did some googlng and JUST flashed this. Fingers crossed! This must seem silly, but it's my first time flashing a kernel so I'm nervous.
edit2: Woo I'm running at 1.7ghz! Thanks for the help! Hm restarted, maybe 1.7 is too high. Will experiment with lower...
Click to expand...
Click to collapse
I'd exercise a little bit of caution when overclocking, especially to 1.7. Because every xoom is different, there is some risk. If your xoom randomly restarts when overclocked, it means you've gone too far and a lower frequency would be better. Also remember that OCing could potentially ruin your xoom if one is not careful enough.
yosterwp said:
I'd exercise a little bit of caution when overclocking, especially to 1.7. Because every xoom is different, there is some risk. If your xoom randomly restarts when overclocked, it means you've gone too far and a lower frequency would be better. Also remember that OCing could potentially ruin your xoom if one is not careful enough.
Click to expand...
Click to collapse
Thanks for the warning. It's been going at 1.5 so far with no problems, and is still a big improvement... if even that causes problems I'll tone it down.
Do some kernels OC better than others?
Jeffu said:
Thanks for the warning. It's been going at 1.5 so far with no problems, and is still a big improvement... if even that causes problems I'll tone it down.
Do some kernels OC better than others?
Click to expand...
Click to collapse
I am not that well informed about kernels specifically. But I know that many kernels can allow overclocking, yet some kernels are more stable and play much nicer with certain roms while others could do the opposite. I think it is a matter of mixing and matching until you find a kernel that is both stable and suits your needs.
I have tried to use CleanKernel 1.2 & Lean Kernel .10 on this ROM. After installing both kernels I seem to get a huge "non responsive" delay after the screen shuts off and the lock screen appears. Is this because the base has been updated to VZW G7 OTA and Kernels are for an older base? Or is there a fix that I am missing? I have ran both kernels with no problems on older based ROMS.
natgear2510 said:
I have tried to use CleanKernel 1.2 & Lean Kernel .10 on this ROM. After installing both kernels I seem to get a huge "non responsive" delay after the screen shuts off and the lock screen appears. Is this because the base has been updated to VZW G7 OTA and Kernels are for an older base? Or is there a fix that I am missing? I have ran both kernels with no problems on older based ROMS.
Click to expand...
Click to collapse
Rule of thumb: Never flash a Rom made for one base on a different base. You have to wait until dev makes one for the new base. Many things could go wrong. Consider you're lucky.
buhohitr said:
Rule of thumb: Never flash a Rom made for one base on a different base. You have to wait until dev makes one for the new base. Many things could go wrong. Consider you're lucky.
Click to expand...
Click to collapse
Actually, most of the times, you can flash a kernel that's based off of a different source base on a different base ROM as long as they are the same Android version (same framework). VRALG7 did not change much other than some of the apps and on the kernel side, I don't believe anything has changed. That should go true for radio too. For the OP, did you come from wipe everything and flash clean? Also, I am not sure what kind of modification the ULE went through but it may be lacking some libs or ramdisk since the rom is so damn light. Go and pull the boot.img from original ULE and see if the original kernel causes the same issue.
I installed the KT747 kernel. It runs GREAT with this ROM! No lag, super smooth & fast. Thx for the replies! KTweaker app is Awesome! The unresponsive / frozen lock screen is gone! CleanROM ULE + KT747 = Winner!
Sent from my SCH-I535 using xda app-developers app
buhohitr said:
Rule of thumb: Never flash a Rom made for one base on a different base. You have to wait until dev makes one for the new base. Many things could go wrong. Consider you're lucky.
Click to expand...
Click to collapse
I agree! Scott updated Clean ROM yesterday to 2.5 which is based off of the new G7 baseband. As Scrosler states in the OP, a new clean kernel is not available yet, so when you flash the new 2.5 you will be on stock. It's worth updating though! I'm sure an updated/upgraded kernel and mods will be out soon enough.
I had that same issue
natgear2510 said:
I have tried to use CleanKernel 1.2 & Lean Kernel .10 on this ROM. After installing both kernels I seem to get a huge "non responsive" delay after the screen shuts off and the lock screen appears. Is this because the base has been updated to VZW G7 OTA and Kernels are for an older base? Or is there a fix that I am missing? I have ran both kernels with no problems on older based ROMS.
Click to expand...
Click to collapse
SO what I did, made surei have no cpu apps runnung to be set on boot ( major problem when using titanium as a restore agent )
Then I flashed scotts clean kernel ( whatever the lastest edition is ).
Then right then and there wiped cache, and dalvik and then fixed permission.
THEN HERE IS WHERE ITS VERY IMP. I LET THE PHONE SIT FOR 10 MINS BEFORE TOUCHING IT AGAIN.
Now i am running smooth .
This is on .lk 0.9 which is essentially the same as lk .10
I have just installed the CM10 -20121129-Nightly-d2vzw. This is the first time I have tried the custom rom route. I must say I love CM10 and glad I made the move but I have having a few issues that are really bothering me. First I am getting terrible battery life, would a different kernal help? And secondly I am having screen off troubles. When ending a call I a m having trouble hanging up and getting the screen back on. I am running kernel version 3.0.48-cyanogenmod-ge67063c
Battery life with cm for me seems to be bad as well. Try ktoonz kernel it can't hurt. Report back if it helps. I'm guessing cm's kernel isn't quite optimized yet for this device. Best kernel I've tried is stock obviously on a TW ROM
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