Related
I had that screen dying this rom also... on build 3 as many more i´ve noticed.
I flashed that earlier kernel after not succesful try on that build 3 kernel.
http://dl.dropbox.com/u/12943198/ics22.zip by arakmar.
Normally build3 trough odin and flashed this ics22.zip trough cwm
Big thanks goes to MrComputerRevo for posting this:
"So I had no waking up issue so I falshed another kernel, but that decreased perfomance and sound was laggy... So I thought what if I flash the kernel that arakmar posted a couple pages ago... Guess what: I don't have lockscreen or waking up issues, sound is perfect and headset works! Try it!"
I followed these instructions and it really helped!
hopefully this helps someone too
nice news i needed to hear that to change to cm9
thanks a lot !!
by the way how do you see the battery backup? similar to cm7? or worse?
siruz said:
nice news i needed to hear that to change to cm9
thanks a lot !!
by the way how do you see the battery backup? similar to cm7? or worse?
Click to expand...
Click to collapse
Nice to hear
Well my whole g3 is only 6months old so no battery issues on that case. But i noticed on cm7 that 1.3 hv kernell was the best, didn' t drain battery so fast. If u want more power/speed ( over 1ghz) with different kernell prepare to lose your battery faster.
On cm9 i'm using the same as 1.3hv stats, max 1ghz on processor speed. My battery has lasted on this for last 4 days, since i flashed this rom.
Sent from my GT-I5800 using xda premium
thanks for th info mate
i flashed cm9 with arakmar's kernel and everything is ok..but i want to get rid off the gapps that i dont need , i only use market and gmail..but i dont want to delete anything vital for the phone or these two apps :/ any idea what should i keep and what not?
none of the google apps is vital for the phone
Imo u can delete what u dont need, gapps are not vital for the phone, many roms doesn't have any of google apps but many devs put up a link for every one who wants gapps on their phone
Sent from my GT-I5800 using xda premium
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 never really paid attention to my wifes stock TF101, until recently I used and wow...it is pretty slow (I have an N7 and was surprised how much slower it was). I'm just wanted to get some feedback on what ROMs & kernals currently have the strongest preformance and stabilty.
Have JB roms become stable enough to surpass ICS ones?
Cryingmoose said:
I never really paid attention to my wifes stock TF101, until recently I used and wow...it is pretty slow (I have an N7 and was surprised how much slower it was). I'm just wanted to get some feedback on what ROMs & kernals currently have the strongest preformance and stabilty.
Have JB roms become stable enough to surpass ICS ones?
Click to expand...
Click to collapse
The Custom ROMs may be more unstable than the stock one. I am not sure, I have the same problem, but I am waiting for a Jelly Bean update for this tablet. I think they will release a JB update this christmas. Try overclocking it? You can Overclock it to 1.6 GHz.
Sent from my Transformer TF101 using xda app-developers app
I've played around with the JB roms (my favourite being ParanoidAndroid), but I ultimately went back to stock ICS.
What I found was that flashing a custom kernel that allowed overclocking and using Nova Launcher with animation speed set to "Faster Than Light" corrected any lag or slowness that I noticed in stock ICS.
tmcquake said:
I've played around with the JB roms (my favourite being ParanoidAndroid), but I ultimately went back to stock ICS.
What I found was that flashing a custom kernel that allowed overclocking and using Nova Launcher with animation speed set to "Faster Than Light" corrected any lag or slowness that I noticed in stock ICS.
Click to expand...
Click to collapse
Well, as you have experienced, I have some questions, because I want to overclock my TF101.
1. Is it safe? I mean, could it kill your processor or brick your tablet?
2. Do you need to have a custom ROM to overclock?
3. Does it wipe all your data?
4. If possible, do you have a link that actually works with full tutorial? I have tried overclocking and my tablet got hard bricked while changing kernel.. by the way, I read like 7 tutorials and then did what I remembered.
Thank you in advance!
Sent from my Transformer TF101 using xda app-developers app
I'm also back to stock. Had stability/performance/usability issues with all the roms I tried, stock is the better one for mine it seems. But I have well over 400 apps installed and it's running very well and fast. I'd look into why your wife's is running so slow with stock, tons of tools out there to help you figure that out like task managers/explorers/killers/etc.
mrkevio said:
Well, as you have experienced, I have some questions, because I want to overclock my TF101.
1. Is it safe? I mean, could it kill your processor or brick your tablet?
2. Do you need to have a custom ROM to overclock?
3. Does it wipe all your data?
4. If possible, do you have a link that actually works with full tutorial? I have tried overclocking and my tablet got hard bricked while changing kernel.. by the way, I read like 7 tutorials and then did what I remembered.
Thank you in advance!
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
I will do my best to try and answer your questions. Please keep in mind that I am not responsible for anything that happens to your device, I am just reporting my experiences and what I recommend. I do not consider myself an expert or a developer. I am just an android enthusiast who has been rooting/unlocking/flashing/modding for a few years. I hope I am able to help you out.
1. I haven't had any issues overclocking. I suppose if you push it up to the max MHz then you could have issues but I have been able to safely run my TF101 at around 1600 MHz. My TF101 is about 16 months old now and I haven't had any problems.
2. A custom ROM is not required but you have to be sure that the kernel is specifically built for Asus based ROMs. The developer usually states it in the respective thread.
3. Flashing a kernel does not wipe your data. As a general rule however I always wipe cache and dalvik cache after flashing anything. It maybe not necessary but it only takes 10 seconds to do.
4. I don't have a link to a tutorial for flashing a kernel or overclocking. There are probably tutorials out there but it's pretty basic stuff. Just flash the kernel using a custom recovery (CWM or TWRP). I personally prefer TWRP. Then i usually use SetCPU (available in the Play Store) to set the max/min MHz. I usually set max=1600 MHz and min=384 MHz.
There are a couple good custom kernels available in the development section. The one that I currently use is made by guevor (http://forum.xda-developers.com/showthread.php?t=1565519). The one I use is in Post #3 and is called "Kernel-2-ICS-V1.1-OC1700-fb_28.zip" - it is the first one under the heading "2.6.39 based".
I hope the above information is helpful!
tmcquake said:
I will do my best to try and answer your questions. Please keep in mind that I am not responsible for anything that happens to your device, I am just reporting my experiences and what I recommend. I do not consider myself an expert or a developer. I am just an android enthusiast who has been rooting/unlocking/flashing/modding for a few years. I hope I am able to help you out.
1. I haven't had any issues overclocking. I suppose if you push it up to the max MHz then you could have issues but I have been able to safely run my TF101 at around 1600 MHz. My TF101 is about 16 months old now and I haven't had any problems.
2. A custom ROM is not required but you have to be sure that the kernel is specifically built for Asus based ROMs. The developer usually states it in the respective thread.
3. Flashing a kernel does not wipe your data. As a general rule however I always wipe cache and dalvik cache after flashing anything. It maybe not necessary but it only takes 10 seconds to do.
4. I don't have a link to a tutorial for flashing a kernel or overclocking. There are probably tutorials out there but it's pretty basic stuff. Just flash the kernel using a custom recovery (CWM or TWRP). I personally prefer TWRP. Then i usually use SetCPU (available in the Play Store) to set the max/min MHz. I usually set max=1600 MHz and min=384 MHz.
There are a couple good custom kernels available in the development section. The one that I currently use is made by guevor (http://forum.xda-developers.com/showthread.php?t=1565519). The one I use is in Post #3 and is called "Kernel-2-ICS-V1.1-OC1700-fb_28.zip" - it is the first one under the heading "2.6.39 based".
I hope the above information is helpful!
Click to expand...
Click to collapse
Thank you for answering my questions. I can finally overclock my tablet. I'll try it later. Thank you in advance again
=====================
EDIT:
=====================
Thanks man.. I have successfully flashed the kernel.. I have a sister and she has some games on my TF101 and she already lost for like four times her progress. My heart was beating so hard lol. Thanks again. You saved my life xD
Hi all,
First let me start by telling you what device I am using a Samsung Galaxy S III I535 running Liquid Smooth 2.37 rom.
I have been flashing phones for years and have bricked, unbricked & in most cases had success with dirty flashing and doing clean flashes. I have gotten to the point in my adventures with flashing phones to experiment with kernels, since that's all anyone talks about that gets some legit performance and battery life stats. So my questions are as follows ( and i apologize now if this has been asked a bazillion times before. If that is in fact the case, some direction to the link would be much appreciated, thanks! )
1) what are the steps one would have to take to properly flash a Kernel
2) are there any pitfalls and caveats i should be concerned about ( bricking is the obvious one here )
Thank you again in advance for taking the time to help me out. Just trying to get fully educated before i decide to start messing around further with my phones!
e_poch145 said:
Hi all,
First let me start by telling you what device I am using a Samsung Galaxy S III I535 running Liquid Smooth 2.37 rom.
I have been flashing phones for years and have bricked, unbricked & in most cases had success with dirty flashing and doing clean flashes. I have gotten to the point in my adventures with flashing phones to experiment with kernels, since that's all anyone talks about that gets some legit performance and battery life stats. So my questions are as follows ( and i apologize now if this has been asked a bazillion times before. If that is in fact the case, some direction to the link would be much appreciated, thanks! )
1) what are the steps one would have to take to properly flash a Kernel
2) are there any pitfalls and caveats i should be concerned about ( bricking is the obvious one here )
Thank you again in advance for taking the time to help me out. Just trying to get fully educated before i decide to start messing around further with my phones!
Click to expand...
Click to collapse
1) Make sure the kernel is compatible with your rom, Do some reading about the kernel -pros & cons.
2) Flash away. In theory, you don't even need to wipe cache or dalvik cache, but just wipe them to make you feel like...it's clean!!
3) The worst thing is you get a bootloop which is an easy fix.
One other thing to note, is AOSP kernels are not compatible with TouchWiz roms, and TW kernels are not compatible with AOSP roms.
Make sure you get the right one, if the developer offers both options.
Sent from my SCH-I535 using XDA Premium 4 mobile app
buhohitr said:
1) Make sure the kernel is compatible with your rom, Do some reading about the kernel -pros & cons.
2) Flash away. In theory, you don't even need to wipe cache or dalvik cache, but just wipe them to make you feel like...it's clean!!
3) The worst thing is you get a bootloop which is an easy fix.
Click to expand...
Click to collapse
Just adding onto this, one good way of ensuring #1 is to flash a compatible AOSP 4.3 or 4.4 kernel that is dated at or about the same time as your rom. If the more recent kernel doesn't work, try the release prior to that.
Sent from my SCH-I535 using Tapatalk 4
Thanks Guys!
SlimSnoopOS said:
Just adding onto this, one good way of ensuring #1 is to flash a compatible AOSP 4.3 or 4.4 kernel that is dated at or about the same time as your rom. If the more recent kernel doesn't work, try the release prior to that.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Much appreciated guys! I decided to go with [4.3/4.4][AOSP] ¤ BMS ¤ d2vzw / d2usc 3.4.y (link below). So far so good, flashed easily and no problems at this point. Ill report back and see how the performance gains are.
http://forum.xda-developers.com/showthread.php?t=2133550
Thanks again for all of your advice!
I run that kernel on all roms. Hope u get good battery life. I suggest let it stabilize a day or two.. Jst my two cents
Sent from my unknown using Tapatalk
wont connect to wifi for me
twistedillutions said:
I run that kernel on all roms. Hope u get good battery life. I suggest let it stabilize a day or two.. Jst my two cents
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
I noticed as soon as I loaded the Kernel there was an issue. It wouldn't connect to any wifi networks. As a matter of fact, I couldn't even turn on wifi, the switch just stayed grayed out after i initially hit it. So currently I am running KT until I can find a solution to my issue. I would love to run BMS given the great response but I need to be able to use wifi lol
e_poch145 said:
I noticed as soon as I loaded the Kernel there was an issue. It wouldn't connect to any wifi networks. As a matter of fact, I couldn't even turn on wifi, the switch just stayed grayed out after i initially hit it. So currently I am running KT until I can find a solution to my issue. I would love to run BMS given the great response but I need to be able to use wifi lol
Click to expand...
Click to collapse
What is the name and date of the rom that you are on? Which version and date of KT747 are you using? Lastly, which version and date of BMS did you flash?
Sent from my SCH-I535 using Tapatalk 4
versions im running
SlimSnoopOS said:
What is the name and date of the rom that you are on? Which version and date of KT747 are you using? Lastly, which version and date of BMS did you flash?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Liquid Smooth 2.37 from 11/06/2013
KT747-AOSP-JB-MR2-3.4-VZW-11-04-2013
BMS_3.4_d2_2014-01-27
U need an older version of BMS thoss new version from dec till now are for 4.4 roms and liquid 2.37 is a 4.3 thats the reason why ur having issues
Sent from my unknown using Tapatalk
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