Hi, as I began to port MIUI ROMs some month ago, I started by always reusing the same kernel, but I would like to understand a little bit more.
So I tried to use Android Image Kitchen, but I was wondering what to do to change the "kernel". Is it some specific files in the ramdisk, or does it represent the whole boot.img file ?
In fact I wanted to rebuild a "clean" boot.img from stock rom (including offline battery animation) and make it compatible with MIUI, and eventually try to add the last version of Vegito kernel for battery life and performance.
Does anyone have the knowledge to help me and clarify all this for me ?
right
Related
Maybe it's an idea for the developers when they create rom's to include smaller boot images (2.2MB) by default.
This will solve the issue with the bad blocks on several devices.
It depends on the kernel used in the ROM. If the kernel is closed source like the kernel on Dj Droid (it's still a HTC test ROM) then there's no way to get it working.
On other ROMs you most probably gonna lose features such as ext2/3 mounting (needed for old school A2SD).
All you can do is hope..
beidl said:
It depends on the kernel used in the ROM. If the kernel is closed source like the kernel on Dj Droid (it's still a HTC test ROM) then there's no way to get it working.
On other ROMs you most probably gonna lose features such as ext2/3 mounting (needed for old school A2SD).
All you can do is hope..
Click to expand...
Click to collapse
OpenDesire 1.5 supports ext and and has a boot image of 2.2MB. Maybe when 1.6 comes out, Adam can changes his boot image back to 2.2MB, otherwise there's not a lot of choice flashing different roms
Hello, I have 2 custom roms for my phone, they are gingerbread based stock roms. One has perfect ram management (strict), and the other has more relaxed ram management settings. The first rom runs smooth and has great battery life, the second still runs fairly smooth, but has some app instability do to low ram, and the launcher closes often. Battery life is not as great on the second rom. But the second rom has some great additions to the first, that I would rather not loose. I would like to transfer the lowmemorykiller settings from rom 1, to rom 2. Or edit the settings in Rom 2 somehow. However I'm a noob, and have windows, and cannot make sense of splitting the imagefile, editing the ramdisk and repacking it to a flashable image. Is there a way to change the settings with root manager? OR an iso image editor, or something that can open the img file, and allow me to edit the ramdisk, without linux, and special coding and fancy wizardry?
Sorry for the long post. Another alternative was to swap the boot.img from the two roms, but I'm not sure what other settings were changed in it.
Any thoughts or tips would be greatly appreciated.
Ok, sorry I asked. I just figured someone here would know how, and might care to share some tips.
Hello everybody,
I don't know if this has been done already, but I couln't find it so I thought why not make a version of my own.
Next to WhiteXP i'm also working on a version of CyanogenMOD 7.2, but with a different approach.
In my oppinion before even trying to release something it's important to have a permanent and working version of instead of the stock recovery.
The difference between this phone and many other phones is the fact that the recovery is included in the boot.img file.
My own phone for example, a Samsung Galaxy S Plus, has a seperate standalone recovery.img.
Because I don't own this phone myself I hope another developer can test if this is working properly.
I didn't change the kernel or important boot files other than the recovery itself, so booting into android shouldn't be a problem and remember it's build upon the stock kernel for now.
Here is the downloadable boot.img: http://depositfiles.com/files/90ye57wtm
The kernel should be flashable through the existing CWM which is already posted in the forums with this file:
http://depositfiles.com/files/e21qacxo9
Hopefully somebody is willing to give me some feedback.
Greetings PsychoGame
Hello
Here I am again with a little update.
This version doesn't seem to work okay, it gets into a bootloop.
I will try to fix these problems at a later time.
Greetings
Psycho Game
Thanks...for your work merge CWM into stock kernel...:thumbup:
Sent from my GT-S5360 using xda app-developers app
Here's a little update of the work i'm doing right now.
As I already said I'm also working on a version of CyanogenMod myself.
The problem is not anymore the availability of the drivers, because BroadCom released their drivers to the public.
In my opinion the next bottleneck is the Kernel. I didn't own a Galaxy Y at first, but I recently bought one to make it easier to test different configurations.
My main phone is a Samsung Galaxy S Plus which already has a realy stable CM9 version, but also the kernel is already updated to version 3 from 2.6.35.14.
This is also my goal ultimatly, but the Galaxy Y uses RFS filesystem in combination with FSR. These are closed source modules from Samsung, which make it difficult to update kernels.
There is a known hack that you can alter the version in the make file of the kernel to 2.6.35.7 while it realy is patched up to 2.6.35.14, but i'm not very fond of such hacks.
I'm a daily linux user already since the year 2000 or so, and build many kernels for Linux computers from source. I can say I have good knowledge of the compilation proces and what's going on in the kernel.
Now back to what i'm doing at the moment:
I already converted the complete galaxy y to EXT4 file system, incl. the EFS partition, and yes I still have my IMEI data etc. so this is considered done [status: complete]
Next step is getting rid of the RFS & FSR kernel modules, which are proprietary [status: complete]
At the moment I'm busy updating the kernel to version 2.6.35.14 the proper way, so I have a stable base kernel to build CM on [status: WIP]
After this I will add CWM recovery to the updated kernel, and make sure everything works as it should, like ADB in recovery mode, formatting, and all these things. [Status: Planned]
When CWM recovery functions as it should work, the proces of building CWM into the Galaxy Y can begin [Status: WIP -> Stalled until kernel stable].
This is a little update on the things I have in mind.
If you like it, please post a comment, that also lifts my spirit in the lots of things that have to be done.
Greetings
Psycho Game
Hi guys,
I want to make my own heavily optimized MIUI ROM, that will be sufficient to my requirements. My goal is to optimize ROM to highest speed and lowest RAM-consumption possible, that can be achieved on my Desire HD.
But I cant find any relevant and newest info, how current MIUI ROM works, and how they are build.
My plan is to somehow optimize released ROM for speed, and low memory requirements (ROM is from MIUIandroid.com) and add there some things, like language pack, and gapps.
Is there some guide about MIUI ROM, that has complete description of directories and files in MIUI ROM ZIP file? I have found nothing on google, MIUI forum or XDA. Just some scattered info, that was months or years old and thus outdated.
I was looking for some complete guide, or things like:
- how and where I must placed gapps files in ROM, so they be available right after flashing ROM, and the user not have to flash it separately?
- what files is required to core functions of MIUI ROM
- what apps in system/app can be deleted without compromise other functions of ROM, and is there some description of each apk file in system/app directory?
- is there a way to specificate what apps will be alwais running in the background, and OS will not close them? (I dont want to wait 10s to start facebook or browser, because System close them after some time of not being used)
...and many more questions like this, about various functions of MIUI ROM.
Where I can find this info, and from where have people knowledge about building custom MIUI ROM, or tweaking/optimizing it? There must be somewhere a complete information about how it works, because obtaining information from google, etc. is highly ineffective....
Hello friends,
I wanted to start kernel developing for the N910F. So i wanted to start compiling the original samsung sources.
Please excuse me, I'm pretty new to android/linux development.
I managed to get the kernel compiling, which gives me an output folder with some GB of stuff and as i could point out a zImage-file, which is hopefully the compiled kernel
To get my kernel working, extracted a stock boot.img with umkbootimg, which gave me a warning, that i can't repack the boot.img without using a modified mkbootimg executable.
A mkbootimg is included in the sammy-source so i used this to pack my zImage together with the extracted initfs.gz, resulting in a boot.img.
Which I flashed ofc, but the reason why i opened this thread is the result of this
The kernel is obviously not booting, it shows for maybe 0.5s the sammy logo and directly starts into download mode.
I guess it has something todo, how i pack my kernel. because i didnt even manage to unpack the stock kernel and repack it and get it booting.
So where is my mistake? Do i miss something?
greez d4rk
Deleted - I notice I replied to an old thread