Database Develop

question about kernel

Sorry for asking this , but just yesterday i made it to install my 1st custom rom.
Now im on vanir rom and at my settings sais that my kernel is: 3.1.10-cm+ . i dont seem to have any problem. everything is fine. battery is fine too. So my question is , can i install whatever kernel i want ? and if i have any issues i can just install another one ? No need for for wipings all cache and data right ?

thing is , i dont seem to understand what kernel to choose. for example i see kernel for stock rom, kernel for cm and kernel for miui. vanir rom sais in settings its jellybean 4.3. so that means i choose stock kernel ?

Search before posting! All these things you ask for are basic knowledge,
which you should have if you flash a custom rom/kernel or you probably
end up posting a "please help me"-thread here.
So take your time and search/read everything about android.
Don't expect anyone to give you a step by step tutorial on
every single thing you could do, as XDA is a development forum.

Omario-242 said:
Mod Edit: Personal attacks will not be tolerated. If you have a problem with another member, report them, ignore them, or respond to them in a mature and respectful manner. Negative responses like these serve no purpose other than to stir up trouble and start arguments.
Click to expand...
Click to collapse
????????

kessaras said:
????????
Click to expand...
Click to collapse
you don't need to understand this part, just ignore it
about the vanir kernel, it's the "safest" way to use the stock kernel. I've made a vanir version of my kernel, but it has some GPU issues which i am trying to resolve ATM.
Some people reported CM10.2 kernel would also boot/work, but i am not sure about this one.
So make a nandroid backup, flash another kernel, wipe /cache and dalvik cache, reboot and see if it boots
if it does, congrats, if it doesn't, just restore your boot image via recovery

laufersteppenwolf said:
you don't need to understand this part, just ignore it
about the vanir kernel, it's the "safest" way to use the stock kernel. I've made a vanir version of my kernel, but it has some GPU issues which i am trying to resolve ATM.
Some people reported CM10.2 kernel would also boot/work, but i am not sure about this one.
So make a nandroid backup, flash another kernel, wipe /cache and dalvik cache, reboot and see if it boots
if it does, congrats, if it doesn't, just restore your boot image via recovery
Click to expand...
Click to collapse
well.... the only vanir rom i found around was one of werewolf but the phone didnt get passed the boot logo.
The only rom that worked ( tested every single rom out of curiosity since im new to android ) , was the iodak cm 10.2. wierd ? maybe... others here were surprised a little. maybe ! i dont know. anyway now im on that kernel and i dont like it too and i dont know how to extract the kernel out of the vanir rom to put it back like it was. the iodak hasnt got the feature to customize the hardware buttons. those buttons now never go off unless i stop touching the phone.

and by the way +thanks from this post for the vanir rom. is my favorite )) i was 5 years on ios , android is new to me. hope i find a way to get the vanir stock kernel without i need to do a whole downgrade to the full rom and then update back. ( it would be faster though since im a noob but i like to kill my time "destroying" my phone and then have to restore it )

Can't Install Roms HELP PLEASE! Huawei U9000 Problems!

Hi I am new to this "romming" business. For my u9000 I installed UtterChaos kernel .32. Most to the roms require .35 kernel. And when I try to install SUT LR 1.8 it never works with windows 8 64 bit. I do have CWM Recovery, and I do have superuser permissions. But for some reason when I try to flash a different kernel like CK Kernel Lebay edition, the whole device gets stuck at boot. Yes I have wiped data, cache and davlik. before doing so. I had to then remove the batteries and put them back to start the phone in download mode to replace the boot image from a back up then go do a CWM restore. And I have tried doing factory resets but the UC kernel boot wont change.
Bottom line is, I AM LOST and I will be using this phone for a long time and I can use a way out of this and I need to find a very fast and stable rom with all working features.
What I have:
- .32 kernel
- UtterChaos kernel
- Custom SU
- CWM Recovery
What I need (please help):
- To get rid of UC kernel (boot, etc...)
- .35 kernel (if possible)
- SUT LR for Windows 8 64bit (if possible)
- A really good rom for heavy gaming, performance, stability, something other than GB (preferably JB or ICS)
I may be asking for too much, and sorry if I am, but I can use some help with this phone right about now.
Thanks in advance!

My answer
You can get 35.7 kernel here, depending on what rom you wish to use. Just flash it along with your preferred rom.
http://forum.xda-developers.com/showthread.php?t=1919097&highlight=kernel
For the rom, it really depends on your preference, because the performance is mostly the same between all the JB roms, smooth enough if you don't install lots of apps that stay in the background. Currently, I'm using the XperienceXperia JB rom. It's about as good as the other JB roms, just with Xperia stuff. Also, make sure that you don't put too much load on it, because it might freeze. No kind of software would be able to magically turn our phone into a gaming powerhouse, because it has an old, outdated gpu to start with. So, don't think about running games like Asphalt 8, because it probably wouldn't run.
http://forum.xda-developers.com/showthread.php?t=2479460
I'm not aware of a Win8 x64 compatible SUT LR, but I don't think you'd need it for anything besides flashing stock roms.
By the way, what rom are you using now? If you flash a cm10 (JB) designed kernel to a GB rom, it would definitely cause problems.
Sorry for the long reply, I don't know how to make it simpler.

THANKS
Hi thanks very much I am using the stock rom. Thank you sir :good:
And I suppose for any rom I flash the corresponding kernel first before I flash a rom?

2nd answer
_ikhan_ said:
Hi thanks very much I am using the stock rom. Thank you sir :good:
And I suppose for any rom I flash the corresponding kernel first before I flash a rom?
Click to expand...
Click to collapse
I'm not sure about the order myself, but I usually flash the rom first, then the kernel. I do this everytime I want to flash a rom, and I've never had any problems. Have you tried flashing one of the JB roms for this device? If you haven't tried, remember to wipe data and cache before flashing the rom, and backup your current rom just in case something goes wrong.

[Q] Persistent failure in trying to root device - GT-N7000

Hi all, my Galaxy Note is running:
- stock android 4.1.2
- Baseband version N7000DXLS8
- build JZO54K.N7000DXLSE
Tried several times to root device but unsuccessful although Odin says "installation was a success". Tried to root using PhilZ-cwm6-DXLSE-OLB-4.91.2.tar.md5. Superuser doesn't show up and only noticeable change when device reboots is the exclamation mark when it retarts. Hopefullu you guys can help solve my problem. Thanks

kuplet said:
Hi all, my Galaxy Note is running:
- stock android 4.1.2
- Baseband version N7000DXLS8
- build JZO54K.N7000DXLSE
Tried several times to root device but unsuccessful although Odin says "installation was a success". Tried to root using PhilZ-cwm6-DXLSE-OLB-4.91.2.tar.md5. Superuser doesn't show up and only noticeable change when device reboots is the exclamation mark when it retarts. Hopefullu you guys can help solve my problem. Thanks
Click to expand...
Click to collapse
If you have a nice touch recovery then flash this:
http://forum.xda-developers.com/showthread.php?t=1538053
Also, if you want to remove that yellow triangle:
http://forum.xda-developers.com/galaxy-s2/orig-development/2013-10-04-triangleaway-v3-10-t1494114
If you don't have the touch recovery then download the same version of Philz kernel in .zip format and flash it through your stock recovery.

XxPixX said:
If you have a nice touch recovery then flash this:
http://forum.xda-developers.com/showthread.php?t=1538053
Also, if you want to remove that yellow triangle:
http://forum.xda-developers.com/galaxy-s2/orig-development/2013-10-04-triangleaway-v3-10-t1494114
If you don't have the touch recovery then download the same version of Philz kernel in .zip format and flash it through your stock recovery.
Click to expand...
Click to collapse
Thanks for the help. Finally got my device rooted. So if i plan to flash this omni-4.4.2-20140522-n7000-NIGHTLY ROM - do I just save it on the SDcard and use the recovery mode?
By the way, since i'm choosing between Slim-n7000-4.4.2.build.5-OFFICIAL-4078 and omni ROM - which one is better? I just want a smooth ROM that has good battery life.

kuplet said:
Thanks for the help. Finally got my device rooted. So if i plan to flash this omni-4.4.2-20140522-n7000-NIGHTLY ROM - do I just save it on the SDcard and use the recovery mode?
Click to expand...
Click to collapse
First you'll have to flash raw kernel. Once you ahve flashed that, reboot into recovery and you can flash Omni
kuplet said:
By the way, since i'm choosing between Slim-n7000-4.4.2.build.5-OFFICIAL-4078 and omni ROM - which one is better? I just want a smooth ROM that has good battery life.
Click to expand...
Click to collapse
I used to use Omni (haven't updated my signature in a while) and it was completely stable apart from the fuse bug. I believe Slim is based off CM and from what I have heard then all the ROMs based off of CM sources aren't very stable. In terms of performance, they should be more or less the same, Slim is lighter so it may be slightly faster. The battery life on both will be the same.
There are a few tweaks you would have to do to get better battery life on AOSP based ROMs, mainly disabling location services, blocking as many apps as possible from keeping the device awake (you can do that in Settings -> App Ops/Privacy Manager).
If you want something fast then you could try Carbon ROM (that's what I am using) but it is extremely unstable (at least for me, I haven't seen anyone else complaining).

XxPixX said:
First you'll have to flash raw kernel. Once you ahve flashed that, reboot into recovery and you can flash Omni
Hmm...so I use the r5 kernel right? Just to clear things up, when planning to flash rom and kernels then you can use recovery procedure? Always? Si which particular situations do you use Odin?
I used to use Omni (haven't updated my signature in a while) and it was completely stable apart from the fuse bug. I believe Slim is based off CM and from what I have heard then all the ROMs based off of CM sources aren't very stable. In terms of performance, they should be more or less the same, Slim is lighter so it may be slightly faster. The battery life on both will be the same.
There are a few tweaks you would have to do to get better battery life on AOSP based ROMs, mainly disabling location services, blocking as many apps as possible from keeping the device awake (you can do that in Settings -> App Ops/Privacy Manager).
If you want something fast then you could try Carbon ROM (that's what I am using) but it is extremely unstable (at least for me, I haven't seen anyone else complaining).
Click to expand...
Click to collapse
Guess it's best to go over each off the features of the ROMS before flashing.I forgot to mention in my earlier post that I was looking for the ROM that is closest to the Google android experience, being a Nexus 7 tablet user/owner.

XxPixX said:
First you'll have to flash raw kernel. Once you ahve flashed that, reboot into recovery and you can flash Omni
I used to use Omni (haven't updated my signature in a while) and it was completely stable apart from the fuse bug. I believe Slim is based off CM and from what I have heard then all the ROMs based off of CM sources aren't very stable. In terms of performance, they should be more or less the same, Slim is lighter so it may be slightly faster. The battery life on both will be the same.
There are a few tweaks you would have to do to get better battery life on AOSP based ROMs, mainly disabling location services, blocking as many apps as possible from keeping the device awake (you can do that in Settings -> App Ops/Privacy Manager).
If you want something fast then you could try Carbon ROM (that's what I am using) but it is extremely unstable (at least for me, I haven't seen anyone else complaining).
Click to expand...
Click to collapse
After flashing the kernel, proceeded to restart my Note and it wouldn't. A box with a question mark would flash on the screen. Don't know what happened. Is there anything I can do to save my Note? Thanks

kuplet said:
After flashing the kernel, proceeded to restart my Note and it wouldn't. A box with a question mark would flash on the screen. Don't know what happened. Is there anything I can do to save my Note? Thanks
Click to expand...
Click to collapse
You have to boot into recovery mode (hold down volume up, power button, home button until you are in). Once there, you can flash any 4.4 based ROM.

XxPixX said:
You have to boot into recovery mode (hold down volume up, power button, home button until you are in). Once there, you can flash any 4.4 based ROM.
Click to expand...
Click to collapse
Geez...thanks again. Was able to flash Omnirom and so far so good. Haven't gone over all the apps but noticed that Waze would always quit when trying to load the app. Will try to install the Waze app and see if it changes anything.

[Q&A] [Kernel][GB,ICS,JB,KK] 2.6.32.63-XPerience-KK06[01/08/2014]

Q&A for [Kernel][GB,ICS,JB,KK] 2.6.32.63-XPerience-KK06[01/08/2014]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

Hiya! As I well am experiencing the same thing - Straight from unlocking phone to your kernel = boot loop.
(It gave me quite a scare)

Mhodhan said:
Hiya! As I well am experiencing the same thing - Straight from unlocking phone to your kernel = boot loop.
(It gave me quite a scare)
Click to expand...
Click to collapse
It did not happened to me. Overclock quite well @ 768Mhz and its stable. Can go up to 864Mhz, just that it will reboot if put under stress.
Using KK04
Maybe your phone hardware have some defects

Hiya! Thanks for the reply. I'm new to the whole bootloader scene and figured since most apps in the android store were mostly no longer compatible with my Xperia, why not flash it. Luckily my model is 11W08, followed all the instructions word for word, line by line, downloaded every program provided, everything went SMOOTHLY
.
Then I opted for this Kernel, where I got the infinte boot loop. I couldnt even get to recovery mode. So I decided to flash
back to the Xperia stock rom then flash again to [KERNEL] 2.6.32.61-nAa-jb-06 and install [ROM] MiniCM7-2.2.2.
Everything is all good.
I am still willing to use this kernel, what hardware defect do you mean that might be hindering me from using this
or should I just try again?

Mhodhan said:
I am still willing to use this kernel, what hardware defect do you mean that might be hindering me from using this
or should I just try again?
Click to expand...
Click to collapse
Oops. I thought you have issue with overclocking. I didn't even know the lastest version (KK 06) will boot into CM7.2.2 rom.
I think you won't have any further issues from now on.
There are not actually hardware defect, just that not every cpu manufactured in the same way, there must be small deviation in making those cpus.
So, Different tolerance on overclock on different cpus. :angel:
Currently on KK04 and Running MiniCM10 - JB 4.1.0 Stable (nAa's Build).

I just tried again flashing using the Kernel, same issue of the continuous boot loop, couldn't even boot to CWM
Decided to flash back to [KERNEL] 2.6.32.61-nAa-jb-06. I'm guessing this kernel is not for me.

Mhodhan said:
I just tried again flashing using the Kernel, same issue of the continuous boot loop, couldn't even boot to CWM
Decided to flash back to [KERNEL] 2.6.32.61-nAa-jb-06. I'm guessing this kernel is not for me.
Click to expand...
Click to collapse
You can try XPerience-KK04 or XPerience-KK05 kernel. XPerience-KK06 have issues

[Q&A] [ROM][5.1.1][F-AOSP i9305] The Android Open Source Project [05.06.2015]

Q&A for [ROM][5.1.1][F-AOSP i9305] The Android Open Source Project [05.06.2015]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.1.1][F-AOSP i9305] The Android Open Source Project [05.06.2015]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

rodman01 said:
have you enabled adaptive light or brightness in settings/display? If yes try to disable it and then you can adjust the brightness.
For me 2G is working, 3G and LTE I cannot test at the moment, because not available in my home area.
Click to expand...
Click to collapse
LTE is working for me!
Edit: Device is definitely running quite hot but aside from that, haven't had any issues! Thanks rodman01! btw, is there a settings menu to adjust the battery icon, button shortcuts etc that I can't see?

Great rom thanks
All working fine only 2 bugs.
The 2g/3g/4g is not stable for me
And the sensors not workink, i cant change to landscape mode in any apps.
Can you fix this bugs ???
Thanks

Which Kernel
Hello Everybody,
I read about this Rom and it sounds really cool. I am excited to try. However, this will be the first time I will flash my S3 LTE (I have flashed other devices before). So, I dont want to brick my S3 LTE. I was confused about the Kernel. Do I need a costum kernel? There are some for Android 5.1. I am running right now a stock Android 4.4.4 rom on my device. Can i just install the Rom following the tutorial on the first page or is there something special about that?
Thank you very much for helping me,
greetings
Marc

It seems my Bluetooth is not working after flashed this rom, full wiped. The phone could not find any bluetooth device and could not be found as well.

marc-132 said:
Hello Everybody,
I read about this Rom and it sounds really cool. I am excited to try. However, this will be the first time I will flash my S3 LTE (I have flashed other devices before). So, I dont want to brick my S3 LTE. I was confused about the Kernel. Do I need a costum kernel? There are some for Android 5.1. I am running right now a stock Android 4.4.4 rom on my device. Can i just install the Rom following the tutorial on the first page or is there something special about that?
Thank you very much for helping me,
greetings
Marc
Click to expand...
Click to collapse
As long as you have rooted your phone, you can just follow the steps in the OP. The kernel is installed in the rom .zip package. You can install a custom kernel over the stock one if you want to experiment with CPU settings and governors etc, but you won't get much help on this thread if you have issues like things not working properly.
At the moment there a couple of bugs that could be fixed by using agni until the next build however

Bluetooth
Did a clean install with version 20150610. Bluetooth seems not to work. Although turned on, not finding other devices and not be seen by other devices. Is this a bug? Bluetoth was working before the flashing when using Slimkat.
Regards
rom169

[5.1.1][F-AOSP i9305] The Android Open Source Project [11.06.2015]
The mod is very good. One note: You can turn off the phone to ring. I will not ring deaf

Thanks and great work on the mod
I just want to thank you for the great mod.
I have waited for a pure (more or less) AOSP mod for the S3 LTE and here you are!
Sometimes I get forced close on the Android keyboard (mostly in Whatsapp) and one or two times FC of the SMS/MMS app. But nothing serious.
Keep up the good work.
TiggaZ

I tried the new release as of 22.06.2015 and it is pretty stable.
Bluetooth is working (connects to an BT headset) but I got some forced reboots while listening to music. Maybe it was because it was Macklemore, I don't know .
After a clean reboot everything seems to work fine. I will give some more feedback about the long term stability as I use this as daily driver now.

Anyone with problems mounting external sdcard? Already tried diferent cards and filesystems and they're only recognized on the recoveries...

With version 20150622 bluetooth is working now. Thank you!
regards
rom69

sailorpito said:
Anyone with problems mounting external sdcard? Already tried diferent cards and filesystems and they're only recognized on the recoveries...
Click to expand...
Click to collapse
Same issue here... Everything else is working great though, so thanks for that ROM :good:
The sd card appears to be working when plugged directly in my PC, and I tried formatting with no success when plugged back in my phone. It's also working when in recovery.

A problem with Gapps
Hi, I tried to install this ROM, but Gapps wouldn't install. (I'm using CWM recovery 6.0.4.7)
It says:
Code:
E:Error in /storage/sdcard1/pa_gapps-modular-micro-5.1-20150410-signed.zip
(Status 6)
Installation aborted.
Any help? It seemed that at least one another person in the main ROM thread was having the same problem.

I managed to install the ROM itself with CWM at the first time and it booted successfully, but without Gapps. Then I changed the recovery to TWRP, and it let me install Gapps (I did a clean reinstall of the ROM and Gapps), but then it stuck on a bootloop. Edit: More details: the loop animation, green, red, blue and yellow "Google spheres" swaying, just keep repeating indefinitely. I don't know if that's a "loop" exactly, but the device doesn't seem to boot further than that.
Installed CWM back, and tried to do a fresh install once again, only ROM, which worked last time. However, the it still bootloops.
I wonder what's wrong. I'm doing a clean install, so why can't I reproduce the successful boot I did the first time...?

GolDDranks said:
I managed to install the ROM itself with CWM at the first time and it booted successfully, but without Gapps. Then I changed the recovery to TWRP, and it let me install Gapps (I did a clean reinstall of the ROM and Gapps), but then it stuck on a bootloop. Edit: More details: the loop animation, green, red, blue and yellow "Google spheres" swaying, just keep repeating indefinitely. I don't know if that's a "loop" exactly, but the device doesn't seem to boot further than that.
Installed CWM back, and tried to do a fresh install once again, only ROM, which worked last time. However, the it still bootloops.
I wonder what's wrong. I'm doing a clean install, so why can't I reproduce the successful boot I did the first time...?
Click to expand...
Click to collapse
Are you sure it's a bootloop? It can take a while on the first boot. A bootloop is when the phone turns itself off and on repeatedly, if it's showing the animation, just wait (10mins?).
My install of the latest version went fine using TWRP (2.8.5 IIRC).

judorange said:
Are you sure it's a bootloop? It can take a while on the first boot. A bootloop is when the phone turns itself off and on repeatedly, if it's showing the animation, just wait (10mins?).
My install of the latest version went fine using TWRP (2.8.5 IIRC).
Click to expand...
Click to collapse
Ah, okay, then it's not bootloop. My phone just hangs indefinitely on the boot animation screen. I have waited for 30 mins, and still nothing. The strangest thing is that I tried some other ROMs ([5.1.1][Cyanogenmod 12.1][UNOFFICIAL][11.06.2015] and [UNOFFICIAL] {UBER} SlimLP 5.1.1 {-o3}), and they always hang at boot. I tried Samsung 4.4 stock ROM just a moment ago, and it booted. But it's so old, ugly and clumsy I don't want to use it. I tried installing this F-AOSP again now that the stock ROM OS booted once at least, but still no success – it always hangs on boot.
But it hardly is a fault of F-AOSP since it seems to happen with almost every ROM. I wonder if I messed something up that simple data+cache+dalvik cache wipe will not heal.

I've had the same problem and found out it's a twrp problem with recent version. Flash stock and this twrp on Odin or heimdall before flashing Rom http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
Sent from my GT-I9305 using Tapatalk

sailorpito said:
I've had the same problem and found out it's a twrp problem with recent version. Flash stock and this twrp on Odin or heimdall before flashing Rom http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
Sent from my GT-I9305 using Tapatalk
Click to expand...
Click to collapse
That did the trick! Thank you so much!

F-AOSP or Resurrection Remix which one is more smooth and have better battery performance for i9305?
BTW, in F-AOSP. Where is the option to delete screen shot in notification area?