I can't get init.d scripts to work with cataclysm rom. They simply do nothing. Permissions are correct, I double checked everything. What is going wrong?
Does the kernel have init.d support?
rootSU said:
Does the kernel have init.d support?
Click to expand...
Click to collapse
Yes, it is latest franco kernel. I think something may have gone wrong with the rom itself, but I have no idea what it might be. Perhaps busybox got borked from updating it over the playstore?
Have they ever worked on the ROM?
How does the ROM call root? Some ROMs call root via init.d - I'm not sure in this case if init.d scripts that run before that are causing an issue.
You can crate init.d scripts that don't require root. Thinks like:
Code:
echo "hello" > /sdcard/hello.txt
And check they can do that.
As for specifics, I'm not familiar with the rom or kernel.
That doesn't work either. The roms FAQ says that init.d support would rely on kernel. So I guess it should be able to do it. Strange.
Lownita said:
That doesn't work either. The roms FAQ says that init.d support would rely on kernel. So I guess it should be able to do it. Strange.
Click to expand...
Click to collapse
And franco definitely has support? I only ask cause I cant see any feature list for it.
rootSU said:
And franco definitely has support? I only ask cause I cant see any feature list for it.
Click to expand...
Click to collapse
Yep, for sure! They are even sharing some scripts in the thread
You probably need a helper app as Cataclysm is pretty much stock rom. Just with some added extras
Sent from my Nexus 5 using Tapatalk
Related
Here the the first offical release of Fluff Kernel for the Epic 4G
Ok here are two new versions for you all.One is the performance kernel and the other is the battery saver.Both are using the new version of my initramfs that comes with ChainsDD's Superuser.apk and su binary.So i suggest if you have Superuser.apk installed to uninstall it before flashing either of these kernels since Superuser.apk will be installed in /system/app instead of /data/app.And now for the kernels.Both of these kernels are Rom Manager compatiable and have root in them.
This is the battery saving kernel.Changes to it are:
Both Kernels are updated to DI18 sourcecode.
CPU governor set to userspace you can use SetCPU to set the speed of the kernel if you like although SetCPU seems a bit unstable on anything other then conservative.
Default scheduler set to CFQ
http://www.sdx-downloads.com/devs/skeeterslint/FluffKernel-Epic-V1.0.5B.zip
This is the performance kernel.Changes to it are:
CPU governor set to performance your cpu will always be set to max this gives the best numbers in linpack and quadrant if numbers are you thing.
Default scheduler is set to CFQ.
http://www.sdx-downloads.com/devs/skeeterslint/FluffKernel-Epic-V1.0.5P.zip
This is another battery saver kernel for those who don't want to mess with SetCPU is uses the conservative CPU governor that the overclocked kernels use.
http://www.sdx-downloads.com/devs/skeeterslint/FluffKernel-Epic-V1.0.5C.zip
All kernels have been compiled against a toolchain that is stable on the newest OTA.And all kernels have been built with stock Samsung kernel source with no modifications to the source code all changes were to the .config file.
This zip can be flashed with ClockWorkMod or can be taken out of the zip and the zImage can put used as a replacement for the zImage in the one click root method although this kernel has root built into it.I recommend removing the JoeyKrim root method to not cuase and conflicts.
This kernel still has some Samsung bloat in it this will be stripped out as time goes on.I will also be trying out different combinations of CPU governors and schedulers to see which one performs the best.So please test it out and post your feedback.
Link to the stock samsung source that was used for these kernels.
http://opensource.samsung.com/ Please search for SPH-D700 DI18.
Sent from my SPH-D700 using Tapatalk
Sorry for the double post but does this kernel have overclocking??
Sent from my SPH-D700 using Tapatalk
mrkrabs said:
Sorry for the double post but does this kernel have overclocking??
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
No it doesn't.
Is this the new kernel from the ota
Sent from my SPH-D700 using Tapatalk
dondadah88 said:
Is this the new kernel from the ota
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Was just about to ask..
No overclock. Will this conflict with custom roms?
rjmjr69 said:
Was just about to ask..
No overclock. Will this conflict with custom roms?
Click to expand...
Click to collapse
This is not the kernel from the ota this is a custom compiled kernel it should run fine on any roms that are out right now.I am running it myself with no issues at all to speak of.
skeeterslint said:
This is not the kernel from the ota this is a custom compiled kernel it should run fine on any roms that are out right now.I am running it myself with no issues at all to speak of.
Click to expand...
Click to collapse
Thank you. And your right its running just fine right now. I am using it with noobnl latest rom. And I had it running fine on the BOSS rom
Hi
Does this kernel support loop-back. Im trying to install ubuntu on samsung epic.
darknoobie said:
Does this kernel support loop-back. Im trying to install ubuntu on samsung epic.
Click to expand...
Click to collapse
All the b usybox applets to setup the the loop device should be there. But I have never tried to use them I will have to check the kernel config to see if the kernel is setup for it.
Sent from my SPH-D700 using Tapatalk
Skeeter this its the best kernel I have used on my phone to date, however one thing to note is that the version of busy box used in this kernel is not compatible with ti backup so the busy box that comes with ti back up needs to be used.
Sent from my SPH-D700 using Tapatalk
mark920 said:
Skeeter this its the best kernel I have used on my phone to date, however one thing to note is that the version of busy box used in this kernel is not compatible with ti backup so the busy box that comes with ti back up needs to be used.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Really it works fine for me same version of busybox that i use in all my kernels.Try reloading Ti when its running and see what happens.
skeeterslint said:
Really it works fine for me same version of busybox that i use in all my kernels.Try reloading Ti when its running and see what happens.
Click to expand...
Click to collapse
I actually tried installing an updated version of BusyBox from the market and it finds TWO different installs??? And both are old versions lol
Updated OP.
I added a link to a fully compatiable Rom Manager kernel.Try it out its just as fast as vaersion 1.0.1-2.Enjoy everyone.And I want to thank Koush for the recovery.
skeeterslint said:
Updated OP.
I added a link to a fully compatiable Rom Manager kernel.Try it out its just as fast as vaersion 1.0.1-2.Enjoy everyone.And I want to thank Koush for the recovery.
Click to expand...
Click to collapse
I have this running and recovery works fine as well as the kernel. Rom manager is nice to have so my thanx goes to skeeter and koush. Its late so I will report any issues I have tomorrow if any arise.
OK I apologize for this but it was very early in the morning when I put this up but I fubar'd my root scripts in the RM kernel it is fixed now please redownload and apply the new zip.
Thanks
skeeterslint said:
OK I apologize for this but it was very early in the morning when I put this up but I fubar'd my root scripts in the RM kernel it is fixed now please redownload and apply the new zip.
Thanks
Click to expand...
Click to collapse
That explains a lot lol. My battery has been draining like mad all day and I noticed that JuiceDefender was having all kinds of errors. Re-downloading and applying now....
odub303 said:
That explains a lot lol. My battery has been draining like mad all day and I noticed that JuiceDefender was having all kinds of errors. Re-downloading and applying now....
Click to expand...
Click to collapse
OK it was still broken but i promise its fixed now.The battery drain probably wasn't cuased by the kernel some people have had problems with android system running away and draining battery but it has nothing to do with the kernel they have flashed back to the stock kernel and still have had issues with battery drain and android system running away on them.
skeeterslint said:
OK it was still broken but i promise its fixed now.The battery drain probably wasn't cuased by the kernel some people have had problems with android system running away and draining battery but it has nothing to do with the kernel they have flashed back to the stock kernel and still have had issues with battery drain and android system running away on them.
Click to expand...
Click to collapse
I wasn't implying that the drain was caused by the kernel, I was saying that my battery was draining because JuiceDefender wasn't able to disable the APN because my root access was broken. D/l-ing update now. Thanks again!
Can i use this kernel with noobnl's Andromeda Galaxy v1.0.3 ROM?
Do we have any GB kernels that support init.d? if so could we implement this http://forum.xda-developers.com/showthread.php?t=1111145?
So far not much has been done to the ChargeGB kernel. The source isn't released yet.
There is the kernel in the NAMELESS ROM that says it does init.d and ext4 (lagfix), but it also doesn't completely work yet (bluetooth and the hardware buttons)
thanks, hopefully it'll completely work soon!
scarygood536 said:
Do we have any GB kernels that support init.d? if so could we implement this http://forum.xda-developers.com/showthread.php?t=1111145?
Click to expand...
Click to collapse
This looks pretty neat after reading the other thread, but is this any different from the values that Autokiller seems to modify? If so, how? Thanks!
Most custom kernels already have values similar to the one's that init.d script sets pre-configured
I've looked into many threads, but have still not been able to find a definitive answer: when changing kernels (going for example from ElementalX to Franco or Purify) should I do a dirty re-flash of the rom and then flash the new kernel or will just a flash of the new kernel be enough?
I know it's been asked before, but I can't seem to find a clear answer.
Thanks
Alex
alexm231 said:
I've looked into many threads, but have still not been able to find a definitive answer: when changing kernels (going for example from ElementalX to Franco or Purify) should I do a dirty re-flash of the rom and then flash the new kernel or will just a flash of the new kernel be enough?
I know it's been asked before, but I can't seem to find a clear answer.
Thanks
Alex
Click to expand...
Click to collapse
1st option
Primokorn said:
1st option
Click to expand...
Click to collapse
Thanks for the reply.
So (just to make sure I have it correct) right now I am running Purity + Purify. If I want to switch to a Purity + Franco setup, I need to dirty flash Purity rom (in which case it brings the kernel back to the standard Purity kernel) and then Franco kernel after that, right?
Do I need to wipe cache or anything else?
Thanks again for all the help
Alex
alexm231 said:
Thanks for the reply.
So (just to make sure I have it correct) right now I am running Purity + Purify. If I want to switch to a Purity + Franco setup, I need to dirty flash Purity rom (in which case it brings the kernel back to the standard Purity kernel) and then Franco kernel after that, right?
Do I need to wipe cache or anything else?
Thanks again for all the help
Alex
Click to expand...
Click to collapse
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.
Primokorn said:
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.
Click to expand...
Click to collapse
Great. Thanks so much for the detailed answer, it clears up my confusion!
Now off to try Franco's kernel
Alex
Primokorn said:
You're right. To prevent any issue it's better to follow this rule regardless of the custom kernel. We need to dirty flash our current rom due to modifications done by the kernel on the ramdisk.
You never need to wipe before flashing a kernel.
Click to expand...
Click to collapse
I actually have an additional question: do we need the same process even if we're talking about the newer version of the same kernel? Like going from an older version of Franco's to the newest
Alex
No only when you change kernel you need to do it.
Sent from my Nexus 5 using Tapatalk
kufikugel said:
No only when you change kernel you need to do it.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you, I promise I will (try) not (to) ask any more silly questions
Alex
alexm231 said:
Thank you, I promise I will (try) not (to) ask any more silly questions
Alex
Click to expand...
Click to collapse
Its better to ask "Silly" questions and understand what you're doing than it is to brick your phone then ask for help.
We'll answer your questions, dont worry. Just ensure you read all the sticky threads in Q&A and General.
rootSU said:
Its better to ask "Silly" questions and understand what you're doing than it is to brick your phone then ask for help.
We'll answer your questions, dont worry. Just ensure you read all the sticky threads in Q&A and General.
Click to expand...
Click to collapse
Yes, I consider your guideline (on your signature) very good advice indeed.
Thanks again to all
Alex
Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk
justinisloco said:
Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?
matts290 said:
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?
Click to expand...
Click to collapse
I know I had to do that when I flashed elemental. Otherwise some apps won't open. But now I want to find out was the the full correct way? Or was it the lazy way
Sent from my Nexus 5 using Tapatalk
justinisloco said:
Just wanted to add to this...
If I'm on the stock ROM. I decide to flash elementalx. Then, want to switch to Franco or something, would I need to flash the stock img? Or can i just flash the stock kernel?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
matts290 said:
Wondering the same thing. If I am currently on stock rom with franco kernel, in order to switch over to elemental do I have to flash the stock rom zip from the thread here on XDA and then install the elemental kernel?
Click to expand...
Click to collapse
Flash the stock boot.img and system.img and then flash the kernel you want to change to..
I have also tried just flashing the stock boot.img and then the custom kernel.. Sometimes it works, sometimes it doesn't. So I would reccomend flashing both! (boot and system)
also check to see if the original kernel left any init.d files, some kernels do. you would want to delete them, as those could, probably would, not play well with your next kernel.
simms22 said:
also check to see if the original kernel left any init.d files, some kernels do. you would want to delete them, as those could, probably would, not play well with your next kernel.
Click to expand...
Click to collapse
another noob question,
does your advice still applies if someone flashed both stock system.img and stock boot.img?
if it is where that file will be located?
thanks.
akmsr said:
another noob question,
does your advice still applies if someone flashed both stock system.img and stock boot.img?
if it is where that file will be located?
thanks.
Click to expand...
Click to collapse
yes. they arent located in either of those locations, so my advice applies, and is the only reason why i posted this. they are located in /etc/init.d/. you either dont have that location (best option), have it but an empty folder, or have an init.d folder with files in it. if there are files there, delete them.
Flashing a system.img will overwrite init.d scripts. /etc is a symbolic link to /system/etc so when you replace /system/etc with whatever is in a ROM.zip or a system.img, these changes apply to /etc too.
If you look in any ROM.zip or kernel.zip, they all flash their scripts to /system/etc/init.d
Sent from my Nexus 5 using Tapatalk
Hello. I'd like to install Faux123 kernel in my moto G but I don't have clear how I should install it . I have found the app on the play store Faux123 Kernel Enhancement Pro. Should I have to install it to get work it properly?
mazzy89 said:
Hello. I'd like to install Faux123 kernel in my moto G but I don't have clear how I should install it . I have found the app on the play store Faux123 Kernel Enhancement Pro. Should I have to install it to get work it properly?
Click to expand...
Click to collapse
You dont need the app to use the kernel, but you need to have an unlocked bootloader, a custom recovery (maybe also a rooted phone).
ItzzAce said:
You dont need the app to use the kernel, but you need to have an unlocked bootloader, a custom recovery (maybe also a rooted phone).
Click to expand...
Click to collapse
Ok I understood how to install correctly faux123 kernel. but what should I do if I want to come back to the original kernel?
mazzy89 said:
Ok I understood how to install correctly faux123 kernel. but what should I do if I want to come back to the original kernel?
Click to expand...
Click to collapse
Before installing faux kernel do a nandroid backup in recovery. If you're unsatisfied with faux kernel then restore your backup.
Sent from my XT1033 using Tapatalk
rajibie said:
Before installing faux kernel do a nandroid backup in recovery. If you're unsatisfied with faux kernel then restore your backup.
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Thank you very much :laugh:
If you want the stock xt1032 kernel send me a pm and I'll send you a link
Sent from my XT1032 using XDA Free mobile app
rajibie said:
Before installing faux kernel do a nandroid backup in recovery. If you're unsatisfied with faux kernel then restore your backup.
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
do you loose data when installing a custom kernel? what are the advantages of this kernel? I am enjoying the stock rom and want to stick with it, but don't know what I'm missing if I switch the kernel to Faux123. Already UL and rooted
3RAN7ON said:
do you loose data when installing a custom kernel? what are the advantages of this kernel? I am enjoying the stock rom and want to stick with it, but don't know what I'm missing if I switch the kernel to Faux123. Already UL and rooted
Click to expand...
Click to collapse
No, you will not loose your data when flashing a new kernel.
Long story short, the advantages are a much more effecient and optimised kernel that will allow for better performance, battery life or a balance between the two depending on what your after and how you setup the kernel... Read, read and when you think you've read enough, read somemore!
giant22000 said:
No, you will not loose your data when flashing a new kernel.
Long story short, the advantages are a much more effecient and optimised kernel that will allow for better performance, battery life or a balance between the two depending on what your after and how you setup the kernel... Read, read and when you think you've read enough, read somemore!
Click to expand...
Click to collapse
Thank you for your reply,
I did read up on this kernel but the info I found wasn't for this device and I didn't know there was anything specific to the Moto G.
3RAN7ON said:
Thank you for your reply,
I did read up on this kernel but the info I found wasn't for this device and I didn't know there was anything specific to the Moto G.
Click to expand...
Click to collapse
Yup sure is, check out his Google+ page and there is plenty of good info there specific to the Moto G.
I really miss the 33R option to change the screen gamma etc, but I dont want to lose performance or add bugs by flashing a custom kernel like franco
Would be awesome if someone made a stock kernel+color settings :good:
The changing of intensity/hue/etc is in the userspace, not kernel space. See franco's reply,
That's all userspace stuff, Kernel code is unchanged. The Color Enhancement feature should be enough to take care of everything automatically for you.
Click to expand...
Click to collapse
In other words, CM removed it from their ROMs. A lot of OPO roms sync their ROMs in line with CM11.
zephiK said:
The changing of intensity/hue/etc is in the userspace, not kernel space. See franco's reply,
In other words, CM removed it from their ROMs. A lot of OPO roms sync their ROMs in line with CM11.
Click to expand...
Click to collapse
Soo I can't change it with root or scripts?
Overdose1986 said:
Soo I can't change it with root or scripts?
Click to expand...
Click to collapse
At least not to my knowledge. I know its a bummer right?! Intensity/hue/contrast/etc was AWESOME.
Does anyone know why CM removed this feature so shortly after its introduction?