Database Info

Kernel questions?

I'm running opensensation cm9 (latest version). the last few builds have been hell on my battery, on a full charge im getting 5 hours with no wifi bluetooth and so forth. my phone like overheated today and took forever to finally boot back up. someone mentioned switching kernels, idk anything about how that works or which ones are safe to use on which roms. any help would be nice. thanks.

Installing a kernel is done the same way you flashed the rom. Flash the zip file in your recovery.
I think your choices right now are either stock opensense kernel or faux's cm9/aosp kernel. Also, I don't think developers release kernels dangerous for your phone. Worst case scenario your phone gets stuck in a bootloop and you have to go back to stock kernel or reflash your rom.
Just keep in mind that a rom like that which is in alpha stage will have bugs that won't be fixed by just switching kernels. Luckily Vorbeth has been working nonstop on Opensense. One would think he was getting paid to dev.. Lol
Sent from my HTC Sensation Z710e using Tapatalk

I don't really recommend switching kernels since Vorbeth has done kernel-level fixes for OpenSensation. Flashing a different kernel has a good chance of breaking something in the ROM...until the wake lock issue is figured out, I suggest using a stable Sense ROM like Android Revolution HD or Virtuous Inquisition if you still want the ICS AOSP look.

How do I do an ADSP firmware update?

I installed the JB ROM JellyTime Beta 7 fine. When I installed JellyTime Beta 8, it hung on the Jellybean boot screen. The OP of the JellyTime thread told someone else with the same problem to update their ADSP firmware for new kernels. I searched and searched, but I couldn't find a reference to how do do that or what it even really was. Could anyone help point me in the right direction?

bananagranola said:
I installed the JB ROM JellyTime Beta 7 fine. When I installed JellyTime Beta 8, it hung on the Jellybean boot screen. The OP of the JellyTime thread told someone else with the same problem to update their ADSP firmware for new kernels. I searched and searched, but I couldn't find a reference to how do do that or what it even really was. Could anyone help point me in the right direction?
Click to expand...
Click to collapse
Sure wish i could get some help with this too.

Have you guys tried the latest releases? When full wiping include format all partitions except sd card.
Sent from a dream.

What latest releases are you referring to? Could you please be more specific?
EDIT: I did a full wipe and reformat of everything, including system, data, and cache.

Right now they are on beta 10. Funny thing, I don't recall anyone mentioning a need to do a adsp firmware update. I don't even know what it is.
Sent from a dream.

I upgraded my radio and ril and it still would not work. I then flashed a stock htc ROM that had sense 3 and then it would take beta 10.
Sent from my Desire HD using xda app-developers app

jlochamy said:
I upgraded my radio and ril and it still would not work. I then flashed a stock htc ROM that had sense 3 and then it would take beta 10.
Click to expand...
Click to collapse
Are you referring to this one?

bananagranola said:
Are you referring to this one?
Click to expand...
Click to collapse
That is the one. But if you don't do a full wipe before you do beta 10 it will have errors. It would still boot but have lots of errors.
Sent from my Desire HD using xda app-developers app

In case anyone is looking for a solution and finds this thread, I can confirm that flashing the stock ROM, wiping, and flashing Beta 10 works.

bananagranola said:
In case anyone is looking for a solution and finds this thread, I can confirm that flashing the stock ROM, wiping, and flashing Beta 10 works.
Click to expand...
Click to collapse
It worked for me as well.
along the same discussion I'd like to ask another question about the new 3.0 kernel.
I'm a weekly ROM changer and usually run IceColdSandwich. Once I switch back to ICS and want to reflash JT to check out the latest improvements/updates, do I have to re-flash the GizRoot_v_2 with the 3.0 kernel then flash JellyTime? Would it work If I did a backup of JellyTime and tried to restore it when a new update comes out or does it become non flashable once I've returned to the older ICS kernel?
In other words, can I flash between ICS and JT without having to go through all the steps to reload the 3.0 kernel?
Thanks in advance to a great community!

uss..p8triot said:
It worked for me as well.
along the same discussion I'd like to ask another question about the new 3.0 kernel.
I'm a weekly ROM changer and usually run IceColdSandwich. Once I switch back to ICS and want to reflash JT to check out the latest improvements/updates, do I have to re-flash the GizRoot_v_2 with the 3.0 kernel then flash JellyTime? Would it work If I did a backup of JellyTime and tried to restore it when a new update comes out or does it become non flashable once I've returned to the older ICS kernel?
In other words, can I flash between ICS and JT without having to go through all the steps to reload the 3.0 kernel?
Thanks in advance to a great community!
Click to expand...
Click to collapse
Nope. You only need to flash the stock once; after that, flash back and forth to your heart's content.

uss..p8triot said:
In other words, can I flash between ICS and JT without having to go through all the steps to reload the 3.0 kernel?
Thanks in advance to a great community!
Click to expand...
Click to collapse
IceColdSandwich runs on a 2.6.5 kernel, and will not work with a 3.0 kernel. Jellytime runs on a 3.0 kernel and will not work with a 2.6.5 kernel. Both of those ROMS have their respective kernels included. You only have to flash the ROM. I'd also recommend a full wipe before each flash as well.
sent from my IceCold Inspire 4G

fatboyRICH said:
IceColdSandwich runs on a 2.6.5 kernel, and will not work with a 3.0 kernel. Jellytime runs on a 3.0 kernel and will not work with a 2.6.5 kernel. Both of those ROMS have their respective kernels included. You only have to flash the ROM. I'd also recommend a full wipe before each flash as well.
sent from my IceCold Inspire 4G
Click to expand...
Click to collapse
usspatriot is actually referring to a separate question. Some of us need to update our firmware to run JB, which can only be done by flashing the latest stock before flashing JB. He wanted to know if the updated firmware would be overwritten by flashing ICS, requiring a reflash of stock before reflashing JB. The ICS and JB kernels are not at issue.

I wonder if this has anything to do with my issue with JB on a Desire HD:
I came from SmartDroid_Reloaded_wwe_1.5.2, did a full wipe, installed, everything works fine for me except for cellular data.
I'm wondering if it's something to do with JB not liking my phone? I've also tried a couple of ICS roms.. See below:
SmartDroid_Reloaded_wwe_1.5.2 = cell data works
Sabsa_Prime_v5.0 = cell data works
TrickDroid_v1.1.1 = cell data works
cm-cfX-20120925-OFFICIAL-ace = no cell data
cm-JellyTime_R10 = no cell data
cm-JellyTime_R10.1 = no cell data
cm-JellyTime_R11 = no cell data
i set my APN's to suit my network (crazy johns in australia) but nothing works..
If i connect to wifi, both the wifi signal and cell signal turn blue, if i disconnect from wifi, both turn grey.
MMS, SMS, Phone calls work fine..
Click to expand...
Click to collapse

First time flashing ROM....help?

So Im ready to go through and flash a ROM finally but I just want to make sure I do things right. I have clockwork mod and have made a backup already. After I download the ROM do they come with different kernels or can I use stock? Also what is a good stable ROM to start with? Id like to get a jellybean one but I have seen one with a lot of bugs still. Any help would be great
Tap'n

9Start with clean rom + clean kernel . This is a good dose to start.
Once you feel comfortable and would like a higher dose
Then move to beans or synergy ..here you can mix and match kernels and roms
Beans comes with imos kernel
Synergy comes with ziggys kernel
Mix and match kernels for your perfect combination
By now you are probably craving a rom with daily updates
Cm10 paranoidandroid AOKP are 3 roms with daily updates
Here youll find imos aosp kernel and kt kernel that go hand in hand with aosp.
By now the first leak of VZW touchwiz jellybean should be hitting the interwebs to take care of any addiction that may ensue. Happy flashing.
VZW GALAXY S 3 4G LTE

DROID3R said:
9Start with clean rom + clean kernel . This is a good dose to start.
Once you feel comfortable and would like a higher dose
Then move to beans or synergy ..here you can mix and match kernels and roms
Beans comes with imos kernel
Synergy comes with ziggys kernel
Mix and match kernels for your perfect combination
By now you are probably craving a rom with daily updates
Cm10 paranoidandroid AOKP are 3 roms with daily updates
Here youll find imos aosp kernel and kt kernel that go hand in hand with aosp.
By now the first leak of VZW touchwiz jellybean should be hitting the interwebs to take care of any addiction that may ensue. Happy flashing.
VZW GALAXY S 3 4G LTE
Click to expand...
Click to collapse
Thanks for the help. Now if I were to cwm back to my backup of stock does that reinstall my stock kernel?
Tap'n

yep

So do I flash the .zip of the ROM first then the kernel then reboot? Cause I tried beans but you can use stock kernel with it cause my bootloader isn't unlocked
Tap'n

techgov8 said:
So do I flash the .zip of the ROM first then the kernel then reboot? Cause I tried beans but you can use stock kernel with it cause my bootloader isn't unlocked
Tap'n
Click to expand...
Click to collapse
Just download ezunlock from the market to unlock your bootloader. No reason to keep it locked.

Zalithian said:
Just download ezunlock from the market to unlock your bootloader. No reason to keep it locked.
Click to expand...
Click to collapse
Well I heard if its unlocked then it can brick you if you OTA. Or does the lock button actually re-lock it?
Tap'n

techgov8 said:
Well I heard if its unlocked then it can brick you if you OTA. Or does the lock button actually re-lock it?
Tap'n
Click to expand...
Click to collapse
yeah it can, just never accept and OTA and you'll be good. Plus since you want to install custom roms, your going to need custom recovery. These block otas from happening even if it was automatically pushed to your phone.
The lock button does relock it.

tu3218 said:
yeah it can, just never accept and OTA and you'll be good. Plus since you want to install custom roms, your going to need custom recovery. These block otas from happening even if it was automatically pushed to your phone.
The lock button does relock it.
Click to expand...
Click to collapse
If you're going into custom roms there's not really much reason to accept OTA anyway.

techgov8 said:
Well I heard if its unlocked then it can brick you if you OTA. Or does the lock button actually re-lock it?
Tap'n
Click to expand...
Click to collapse
almost all custom roms dont allow the pop up about a OTA anyways so you should be clear

Ive used Synergy v1.7, and CleanRom 2.0/CleanKernel 1.0 is way better and smoother than Synergy. Im thinking about upgrading to Beans..but im not sure I want to do that yet till all the bugs are worked out of the different Roms to choose from now.

[Q] Graphical errors with custom kernels

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

[Q] COming from Bionic, to S3....confused ?

Hey guys, I have had a Bionic for the past 18 months or so....forgive me if my questions sound silly....
Recently, I was given a S3 to use. Before I take the plunge and get it activated, I was tryign to learn about the ROMS etc out there.
- I see there are TouchWiz ROMS and AOSP roms. I'm assuming the TouchWiz ROMS are based on stock rom just tweaked and debloated and teh AOSP ROMS are the ones built from scratch?
- I see there are kernels around....same, AOSP and TW. Is it safe to assume if I use AOSP, I need to get an AOSP kernel? If I install for example the latest Liquidsmooth....do I have to do the kernel 1st? or does the ROM have the kernel built in?
- Do I have to unlock the bootloader? Or is that what the kernel does?
Again, sorry for the dumb questions....my Bionic was simpler to do...with less options....
Thanks in advance

docluv01 said:
Hey guys, I have had a Bionic for the past 18 months or so....forgive me if my questions sound silly....
Recently, I was given a S3 to use. Before I take the plunge and get it activated, I was tryign to learn about the ROMS etc out there.
- I see there are TouchWiz ROMS and AOSP roms. I'm assuming the TouchWiz ROMS are based on stock rom just tweaked and debloated and teh AOSP ROMS are the ones built from scratch?
- I see there are kernels around....same, AOSP and TW. Is it safe to assume if I use AOSP, I need to get an AOSP kernel? If I install for example the latest Liquidsmooth....do I have to do the kernel 1st? or does the ROM have the kernel built in?
- Do I have to unlock the bootloader? Or is that what the kernel does?
Again, sorry for the dumb questions....my Bionic was simpler to do...with less options....
Thanks in advance
Click to expand...
Click to collapse
1. AOSP is the original Android OS untouched by any company. Touchwiz is Samsung's version Android.
2. You don't need a custom kernel but it can optimize your phone for increase in battery life.
3. All ROMs have kernels built-in they have to or else it won't work .
4. You must unlock the boot loader in order to flash anything.

Gotcha..!
Thank you!
So is it safe to assume, you flash ROM 1st, then you flash kernel? At 1st glance, I like the Liguidsmooth ROM, but people are also raving about the KT747 kernel. SO I would have to flash his AOSP version...
I have seen some radios also...Is that advisable to do?
jmxc23 said:
1. AOSP is the original Android OS untouched by any company. Touchwiz is Samsung's version Android.
2. You don't need a custom kernel but it can optimize your phone for increase in battery life.
3. All ROMs have kernels built-in they have to or else it won't work .
4. You must unlock the boot loader in order to flash anything.
Click to expand...
Click to collapse

Yes that is correct but you must first root your phone. The bionic had a larger margin of error when it came to rooting.

Yes, 1st thing I'm going to do is root and unlock the bootloader....
One last Q...
I see people are having GPS lock issues on some ROMs (eg Liquidsmooth), compared to stock. Would that be a kernel type off issue? Would updating the kernel to the KT747 fix this?
jmxc23 said:
Yes that is correct but you must first root your phone. The bionic had a larger margin of error when it came to rooting.
Click to expand...
Click to collapse

It is a ROM issue so the devs have to make a fix for it.