Database Info

K.A.T. kernel on EOS ROM does not detect SDcard switch

I am on a custom EOS rom, nightly 72, but when I use the K.A.T. kernel an insert of a SD card in the dock is not detected. On the stock kernel it does however.
Problem on stock is the stability of gmail, etc. Does anyone know how to fix the kat issue with not detecting change of sd card in the dock?
Sent from my Transformer TF101 using xda app-developers app

Update, since I found a way.
I installed Guevor Kernel #700 and now the sd card will be detected, so I will stick with that.
Recap:
- K.A.T. kernel: stable, working gps, not-detecting change of SD card
- Harmony kernel: stable, detecting sd-change, non-working gps
- Stock kernel: working gps, detecting sd-change, not so stable
- Guevor kernel: working gps, detecting sd-change, more stable
Sent from my Transformer TF101 using xda app-developers app

Custom Kernel

I have downloaded CM 10 from get.cm and installed it on my galaxy tab 2, and flashed it through recovery. Does flashing the ROM means I am using CM kernel or I have to download the kernel and flash it manually?
Sent from my GT-P5100 using xda app-developers app

You will be using the CM kernel

imnuts said:
You will be using the CM kernel
Click to expand...
Click to collapse
Besides the CM kernel, are there any other kernels who offer a smoother transition to the higher CPU speeds or more governors?

You will use CM kernel. Coz they are only match with CM ROM .

[Q] How to run INT2EXT scripts on Stock Rom 2.3.3

I have been using LG P500 from last 2 years. I have tried many custom ROM but now back to stock ROM.
Can anyone tell me how to use INT2EXT on this ROM, as I already tried flashing these scripts in recovery. But unfortunately none of it worked.
I followed this thread
http://forum.xda-developers.com/showthread.php?t=1716124

rishabhgangwar said:
I have been using LG P500 from last 2 years. I have tried many custom ROM but now back to stock ROM.
Can anyone tell me how to use INT2EXT on this ROM, as I already tried flashing these scripts in recovery. But unfortunately none of it worked.
I followed this thread
http://forum.xda-developers.com/showthread.php?t=1716124
Click to expand...
Click to collapse
Does the stock rom have init.d support? If you look in system/etc is there an init.d folder?

As far as I know stock ROM doesn't come with init.d support
But you can use this app to add init.d support
https://play.google.com/store/apps/details?id=com.androguide.pimp.my.rom
Sent from my LG-P500 using xda premium

akiratoriyama said:
As far as I know stock ROM don't come with init.d support
But you can use this app to add init.d support
https://play.google.com/store/apps/details?id=com.androguide.pimp.my.rom
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I tried this but still no success on stock ROM 2.3.3
Sent from my LG-P500

Can anyone help me with this????

You cannot run int2ext or link2SD on stock because the stock kernel doesn't support ext partition. Try using a custom kernel that supports ext partition .
Sent from my LG-P500

Flash djnoxd kernel with new gpu libs, then flash int2ext
Sent from my LG-P500 using xda app-developers app

anuragchowdry said:
You cannot run int2ext or link2SD on stock because the stock kernel doesn't support ext partition. Try using a custom kernel that supports ext partition .
Sent from my LG-P500
Click to expand...
Click to collapse
Junior Einstein said:
Flash djnoxd kernel with new gpu libs, then flash int2ext
Sent from my LG-P500 using xda app-developers app
Click to expand...
Click to collapse
If I had to flash a new kernel then the purpose of being on Stock ROM will diminish.
The purpose of being on stock ROM that there is no real bug in ROM and great battery life.
Is there any other mod which I can you besides flashing kernel?

I'll just combine the above posts because they're all incomplete.
First of all, you need busybox installed.
Install it from here: https://play.google.com/store/apps/...t=W251bGwsMSwyLDEsInN0ZXJpY3Nvbi5idXN5Ym94Il0.
Then, you need to add init.d support (this will enable running scripts on boot)
For this, you have to install this app: https://play.google.com/store/apps/...wyLDEsImNvbS5hbmRyb2d1aWRlLnBpbXAubXkucm9tIl0.
Then, you need a custom kernel like Candied kernel. And finally, you can flash INT2EXT.

Lt.Win said:
I'll just combine the above posts because they're all incomplete.
First of all, you need busybox installed.
Install it from here: https://play.google.com/store/apps/...t=W251bGwsMSwyLDEsInN0ZXJpY3Nvbi5idXN5Ym94Il0.
Then, you need to add init.d support (this will enable running scripts on boot)
For this, you have to install this app: https://play.google.com/store/apps/...wyLDEsImNvbS5hbmRyb2d1aWRlLnBpbXAubXkucm9tIl0.
Then, you need a custom kernel like Candied kernel. And finally, you can flash INT2EXT.
Click to expand...
Click to collapse
I tried the PimpMyRom but no success and the point is that I don't want to flash a kernel.

rishabhgangwar said:
I tried the PimpMyRom but no success and the point is that I don't want to flash a kernel.
Click to expand...
Click to collapse
Well then you can't get these or any scripts to work on stock I'm afraid.
Sent from my LG-P500 using Tapatalk 2

Lt.Win said:
Well then you can't get these or any scripts to work on stock I'm afraid.
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
If I have to deal with few bugs on my own, then its better that i'll use some custom rom again with init.d support.
Sent from my LG-P500

Why don't you use link2sd? It's supported on stock roms, i'm using it on Stock GB 2.3.5 (Rooted obviously) and it works great, 240 apps and 62MB of free internal memory

gonzo_fortinero said:
Why don't you use link2sd? It's supported on stock roms, i'm using it on Stock GB 2.3.5 (Rooted obviously) and it works great, 240 apps and 62MB of free internal memory
Click to expand...
Click to collapse
I'll give a shot and will report soon.
Sent from my LG-P500

Follow this guide and it will work for any stock rom (At least it worked for the wildfire s)http://forum.xda-developers.com/showthread.php?t=1432459

Can't Flash Kernels

So I lost my phone, got a new one, rooted using the casual root/unlock w/twrp method found on this forum http://forum.xda-developers.com/show....php?t=2332825
Is it possible to somehow improperly root/unlock without bricking? Or that I just got a bad download. I am having random reboots with just about every kernel I flash, some worse than others. I can only run the stock kernel. Running a clean 2.9 and the latest TWRP. Would it be useful to do a full wipe and "reroot/unlock"

What rom are you using and what kernels are you trying to flash?
Sent from my SCH-I535 using Tapatalk 4

Right, sorry. Liquid 2.9..tried flashing multiple builds of BMS, a few lk builds, dkp, and team kernalizer kernel. I think that's all of the available kernels for the s3
Sent from my SCH-I535 using Tapatalk 4

ThunderRootedDragon said:
Right, sorry. Liquid 2.9..tried flashing multiple builds of BMS, a few lk builds, dkp, and team kernalizer kernel. I think that's all of the available kernels for the s3
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Clean flashes, freshly installed rom after first boot with the stock kernel, I reboot and flash the new kernel and just never fee stability.
Sent from my SCH-I535 using Tapatalk 4

ThunderRootedDragon said:
Clean flashes, freshly installed rom after first boot with the stock kernel, I reboot and flash the new kernel and just never fee stability.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Well, I follow AOSP kernel development a little bit. If I were you, I'd start by flashing a kernel built within seven days of July 20th cuz it seems every two to three weeks, kernel commits render older roms useless. If you don't follow AOSP commits in the more popular rom or kernel threads then I suggest staying away from custom kernels cuz they move quickly. Custom AOSP kernels built on 8/13 won't work on older roms for example.
Edit: I got July 20th cuz LiquidSmooth was last updated on July 20th btw. Just to be clear.

Good advice. I don't follow the aosp commits but I did have the same thought and flashed an older version of BMS (I really want to give it some burn) didn't work... I'll try an older build of lk too just to see where I am.
Really hoping 4.3 somehow resolves this issue for me.
Thanks for your help.
Sent from my SCH-I535 using Tapatalk 4

ThunderRootedDragon said:
Good advice. I don't follow the aosp commits but I did have the same thought and flashed an older version of BMS (I really want to give it some burn) didn't work... I'll try an older build of lk too just to see where I am.
Really hoping 4.3 somehow resolves this issue for me.
Thanks for your help.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Hope so too. I'm trying out Slim Bean beta 2 with BMS kernel from 8/15 and it's working great performance wise. I'd even suggest trying newer 4.3 rooms (CM, Unofficial CM, PA, etc) just for a couple hours and trying your hand with a custom kernel from 8/13 or newer. Or trying a newer 4.2.2 nightly with a custom kernel. For BMS, I believe GideonX said that 7/30 is the last JB 4.2.2 kernel he's made.
How long would you say you waited before flashing the kernel? I usually flash rom, reinstall my apps, set up home screens, then flash a kernel. Maybe 20 minutes between rom and kernel flash cuz of habit.
Sent from my SCH-I535 using Tapatalk 4

Can't boot custom kernels

I'm flashing roms for a very long time, but I ran into a problem, I can not understand:
I have unlocked my bootloader.
Flashed TWRP
Formatted all the partitions in TWRP.
I have flashed AOKP nightly 02/01/2014 but whenever I trie to flash a custom kernel (tried bricked and Franco) my phone won't boot. It's stuck at the Google logo.
How come?
Sent from my Nexus 5 using XDA Premium 4 mobile app

Caspertje19 said:
I'm flashing roms for a very long time, but I ran into a problem, I can not understand:
I have unlocked my bootloader.
Flashed TWRP
Formatted all the partitions in TWRP.
I have flashed AOKP nightly 02/01/2014 but whenever I trie to flash a custom kernel (tried bricked and Franco) my phone won't boot. It's stuck at the Google logo.
How come?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Make sure all the partitions are the correct size as well as make sure the Kernel supports the ROM. If you read the individual kernel threads and do a search, the information should be available. Its been discussed that many ROMs have switched some code in the nightlies to not being supported by some kernels while others work (such as Chaos kernel working on CM ROM while Franco kernel works stock). Depends on your preference then once you find which are supported and which are not. There is also a thread (I believe in Original Development or the other development thread) that bridges the kernel support of some to work on the newer CM based nightlies based on the CAF/nonCAF system codes that are being worked on.

Caspertje19 said:
I'm flashing roms for a very long time, but I ran into a problem, I can not understand:
I have unlocked my bootloader.
Flashed TWRP
Formatted all the partitions in TWRP.
I have flashed AOKP nightly 02/01/2014 but whenever I trie to flash a custom kernel (tried bricked and Franco) my phone won't boot. It's stuck at the Google logo.
How come?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Because you flashed a kernel that is not compatible with the rom. Re-flash the rom and then find a kernel that is compatible with AOKP.

I was coming from the nexus 4 running AOKP and they have had a poll about caf or non-caf. They decided non-caf, that's why I thought Franco kernel should work (worked on nexus 4).
But I see I have to do some searching.
I thought the decision was already made by the AOKP to use aosp kernel.
Sent from my Nexus 5 using XDA Premium 4 mobile app