How hard would it be too implement ion for a sense 5 kernel,and could we base a new kernel off of one of our 4.3 kernels,been away from this phone for a while and just am surprised that hd2 has a working sense 5 (buggy though)i know its difficult just wondering if its even possible????
Sent from.................
If you want Sense badly, try to port the ion kernel form the HTC Desire yourself.
I've heard porting the kernel is really hard.
Yes it is possible.
Yeah ive been reading up on how ion is implemented in kernel and what it does,now the only thing is figuring out how to compile it into the kernel,i see sebastianfm over in sensation forms did it back in july but he has alot of knowledge on kernel stuff so it looks like if know one on are forms doesnt try it will never get done im gonna keep reading in my spare time and see what i can do too help!!!
Sent from.................
Another question since there kernel(dhd) as ion implemented already couldnt i just unpack boot.img and change out ramdisk and bootclasspath and change int.rc boards and repack kernel???
Sent from.................
jwhood said:
Another question since there kernel(dhd) as ion implemented already couldnt i just unpack boot.img and change out ramdisk and bootclasspath and change int.rc boards and repack kernel???
Sent from.................
Click to expand...
Click to collapse
Nope. The ramdisk is different than the kernel. You have to port the zImage for it to boot up on the board. The zImage is the entire Kernel.
Sent from my HTC Glacier
Related
It seems as if a lot of the reason people are hesitant to switch to froyo is the lack of custom kernels. custom kernels provide much better battery life as well as the ability to overclock as well as many other very useful features that create faster and more efficient operating system functions. From personal experience with froyo roms i have noticed the system to be quite slow compared to 2.1 and also i have noticed absolutely horrid battery life. We all know that these leaks may be far from complete but thats not to say that we shouldnt be making them better. It is obvious that Firon and noobnl have the correct information on this matter seeing as they have rooted all of the froyo releases inside of the zImage. If they were kind enough to share the information they have it would be very easy to either port our drivers to a i9000 froyo source or to use backported eclair libraries and use our current kernels. With this being said, I am very sure that this information could be the dealbreaker for froyo roms. With a good kernel comes a good functioning phone.
TO FIRON OR NOOBNL:
Please share your method of extracting the initramfs in order to quickly advance the development of froyo roms and to prolong the necessity for an updated source code
https://github.com/atinm/initramfs-utils
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
EDIT: LMAO, you think root is *just* in the kernel. >.< Root can also be put into the ROM itself...
bubby323 said:
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
Click to expand...
Click to collapse
THANKS A lot man
You have tested this on froyo kernels? And technically if we used a correct froyo initramfs combined with a 2.6.29 kernel with backported eclair libraries for certain hard/software aspects we should be able to acheive an eclair kernel on a froyo rom. Ive done it before on other phones
the jump from .29 to .32 is a massive one, but all the power to ya...
shabbypenguin said:
the jump from .29 to .32 is a massive one, but all the power to ya...
Click to expand...
Click to collapse
Ive done it on evos/nexus' and i can confirm that its been done on galaxy s phones. it may be a massive jump in version number and overall base code. but as far as android and our devices go it really hasnt changed too much. actually i can almost guarantee that it will boot just by swapping the kernel inside the zimage. but to get camera and other functions requiring updated drivers we would need older libraries. or we can just patch our board specific files onto a i9000 kernel. but hey. doubting is more fun than doing
bubby323 said:
https://github.com/atinm/initramfs- utils
There's the tools to do it. I've done it successfully with the modding of the scripts about 5 times now. You cant technically do anything as far as overclock or battery life saving goes, as it isn't the source. It mainly allows you to edit the init.rc which can give you cutstom bootclasspath's and boot animations.
EDIT: LMAO, you think root is *just* in the kernel. >.< Root can also be put into the ROM itself...
Click to expand...
Click to collapse
hey i recently tried to extract the initramfs using that method and was unsuccessful. could anyone be kind enough to either post a download to a froyo initramfs or to give me simple instructions on how to extract it. ive tried putting the zimage in the folder and running extract-initramfs.sh and i get a 0kb cpio image
help
EnVolved said:
hey i recently tried to extract the initramfs using that method and was unsuccessful. could anyone be kind enough to either post a download to a froyo initramfs or to give me simple instructions on how to extract it. ive tried putting the zimage in the folder and running extract-initramfs.sh and i get a 0kb cpio image
Click to expand...
Click to collapse
i have tried a few different ways to use this script being that i am new to Linux but i just recently experienced the same outcome as the above member. all help is appreciated btw
If you want better battery life editing the initram isn't going to do it.Your gonna need kernel source to play with to be able to do anything about battery life.
justlovejoy said:
i have tried a few different ways to use this script being that i am new to Linux but i just recently experienced the same outcome as the above member. all help is appreciated btw
Click to expand...
Click to collapse
There should be only one way to use that script to extract.
./extract_initramfs.sh zImage
and here's the header from the repack script.
usage : ./repack.sh [kernel] [initramfs_direcotry] [kernel source dir] "title of build"
example : ./repack.sh /data/android/initramfs-utils/zImage /data/android/captivate-initramfs /data/android/linux-2.6.32 "title of build"
These are fairly simple shell scripts that only appear complicated because of the use of grep.
Currently I am using a 2.2.1 rom and which the kernel does not support rndis for wired tether. I looked around and found a thread that has patch to enable it for the DI28 system. It is a zimage file 4.3 mb, there is also a zimage in the rom of 5.5 mb (located in /kernel/update/) Would it be possible to replace the 5.5 with the 4.3? Or would there be a problem because the smaller file was from a DI28 vs a DK28
warlar12 said:
Or would there be a problem because the smaller file was from a DI28 vs a DK28
Click to expand...
Click to collapse
I am going to make the assumption that you mean DI18 instead of DI28, which is a 2.1 Eclair kernel, unlike the DK28 which is a 2.2 Froyo kernel. If your currently running a Froyo rom, then you cant use an Eclair kernel. You more than likely going to have to wait til the source code is released for Froyo before it will be available, or you can Odin back to DI18 and use a custom kernel.
Koadic said:
I am going to make the assumption that you mean DI18 instead of DI28, which is a 2.1 Eclair kernel, unlike the DK28 which is a 2.2 Froyo kernel. If your currently running a Froyo rom, then you cant use an Eclair kernel. You more than likely going to have to wait til the source code is released for Froyo before it will be available, or you can Odin back to DI18 and use a custom kernel.
Click to expand...
Click to collapse
Lol yeah I meant the DI18.
I just looked up zimage and found out that it is the kernel...damn it...time to figure out how to modify it
warlar12 said:
Lol yeah I meant the DI18.
I just looked up zimage and found out that it is the kernel...damn it...time to figure out how to modify it
Click to expand...
Click to collapse
I think the only modifiable part of the z image is the init, could be wrong...please prove me wrong so we can have over clock
Sent from my SPH-D700 using XDA App
Kcarpenter said:
I think the only modifiable part of the z image is the init, could be wrong...please prove me wrong so we can have over clock
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Ive been staring at my computer screen and getting more and more confused...I can not find a program or a way to decompress the file. But apparently it is compressed by a zip program. And on the phone it decompresses it once you flash the rom. Other then that I have decided to call it a night on trying to find a way, (I am sure there is a way.) It is giving me a major headache lol.
The main problem so far is that the source has not been released. However I think it has in a way because it is on the rom, which means there is a way to get it off and mess with it. Just hasnt been discovered yet.
Its packaged by cpio I believe... Ill find something on it tomorrow for you...theres a dev thread that talks about it somewhere...but its probably not for the weak of heart or someone without a bit of kernel knowledge. Not sure how vast your skill set is.
Sent from my SPH-D700 using XDA App
warlar12 said:
Currently I am using a 2.2.1 rom and which the kernel does not support rndis for wired tether.
Click to expand...
Click to collapse
I haven't tried any of the Froyo leaks so I can't comment on whether the Froyo kernel has RNDIS support out-of-the-box or not. Once the Epic Froyo kernel sources are released I'll patch in proper RNDIS support if necessary.
Meanwhile, if it's the case that RNDIS can't be enabled in the stock Froyo kernel, then I'm afraid that nothing can be done to fix that without the kernel source code.
I essentially want to get into the kernel to first start seeing what each file does then making smal tweaks to see the outcomes. So once I get some more knowledge I'll be able to compile my own.
Sent from my SPH-D700 using XDA App
warlar12 said:
I essentially want to get into the kernel to first start seeing what each file does then making smal tweaks to see the outcomes.
Click to expand...
Click to collapse
The kernel isn't comprised of files but linked executable code (except the initramfs image, but that's not actually the part of the kernel, it's just included inside it).
warlar12 said:
So once I get some more knowledge I'll be able to compile my own.
Click to expand...
Click to collapse
A kernel can't be compiled without the source code, that's what we're all waiting for.
mkasick said:
The kernel isn't comprised of files but linked executable code (except the initramfs image, but that's not actually the part of the kernel, it's just included inside it).
A kernel can't be compiled without the source code, that's what we're all waiting for.
Click to expand...
Click to collapse
Ahh so really there is not a way to change it besides building a new one from source
SORRY IF THIS HAS ALREADY BEEN MENTIONED
im trying to port a sensation sense 4.0 rom to our hd2's
im a noob and wanting to try and learn how to port etc
only way to learn is to try
i have used this method :- http://forum.xda-developers.com/showthread.php?t=1222746
and im getting errors in cwm mainly status error 0
what am i doing wrong
the rom im porting is this one :- http://forum.xda-developers.com/showthread.php?t=1513055
the target device rom im using is this one:- http://forum.xda-developers.com/showthread.php?t=733649
as it is also a sensation rom but ported for hd2 so i assumed there wouldnt be much to change (probably wrong)
obviously when/if i can get this to run the it will have the energy stuff removed as it wont be an energy rom and isnt my stuff to keep in (thats if it is still in i dont know it wouldnt boot)
ANY HELP WOULD BE GREATLY APPRECIATED
(going to give the kitchen a whirl)
!!!!!!!ABANDONED!!!!!!!!
Dropbox link added
happy to see your determination on study.
though i dont know how to port
but i know one thing
sharing ramdisk(initrd.gz) of between different major versions of android couldn't work
ie. 2.x/3.x/4.x
you should rebuild a new ramdisk for porting ics.
tips. may be tytung's ics r1 kenel could help.
BUMP!
HELP NEEDED
Sent from my HTC HD2 using xda premium
ok so i have ported it using dsixda kitchen using the energy sensation rom as a base
now im getting error 6 in cwm... from what i have googled i have put it down to my update-script but as a noob i have no idea whats gone wrong
The updater script isn't in linux formatting, you need to use notepad ++
I only use notepad ++ and i think it is in linux formatting, how do you put it in linux formatting
Just found interesting thread in desire hd forum
This is a port from sensation(i think) with Sense 3.6
here
I think that you will try this, it's easier to port from DHD
btw, good luck
stupid question would i use an ics rom as a base since its ics
MkBy said:
ok so i have ported it using dsixda kitchen using the energy sensation rom as a base
now im getting error 6 in cwm... from what i have googled i have put it down to my update-script but as a noob i have no idea whats gone wrong
Click to expand...
Click to collapse
you have errors in your updater script.
open your file with Vim (press "a" to start typing) rather than notepad++ to see if there is any weird thing
cheers
not to say this but, it will be hard,
sensation is armv7 if im not correct, it will make the port harder :/ but as its based on ICS it wouldn't be to hard neither
Wouldn't it be easier to port a Desire HD build of sense 4.0 instead of from the Sensation?
htccraze said:
Wouldn't it be easier to port a Desire HD build of sense 4.0 instead of from the Sensation?
Click to expand...
Click to collapse
just found this desire hd build (http://forum.xda-developers.com/showthread.php?t=1545595) so will try porting that instead
Im not expert but i was thinking it might be easier only because porting normal Desire HD builds is easier to do because the phone is rather similiar to our HD2, or at least so I've read here on XDA. I know when developers started trying to port builds from the Sensation it took a long time to work all the bugs out because the phone is so different from each other.
I also came across another thread about this found here that might yeild some useful help. They are using AROMA Installer to install the build but are having problems getting it up and running as well. I personally have not used it yet so i can't say if there is any benefits or any negative feedback about trying to boot using that or not.
DHD is MSM 8255 with Adreno 205. HD2 is QSD 8250 with Adreno 200. HD2 ~ Desire ~ Nexus One != DHD.
Swyped from my HTC HD2 using XDA App
The Sensation is Adreno 220 so wouldn't the Desire's chipset at 205 be closer and more of a match to the 200 of the HD2? I'm still
learning so I could be wrong but i know a lot of developers had problems porting from the Sensation more so then the Desire HD.
Kind of thinking about it i recall that may have been from the lack of Kernal support or something though. Not sure since its been awhile now.
htccraze said:
Wouldn't it be easier to port a Desire HD build of sense 4.0 instead of from the Sensation?
Click to expand...
Click to collapse
of cause, think of the resolution of g14...... qhd and hd2..... wvga:laugh:
So, are you going to work on dhd port or sensation port?
what´s the major difference between Sense 4.0 and 3.6?
Rayzakt said:
what´s the major difference between Sense 4.0 and 3.6?
Click to expand...
Click to collapse
Speed, look, feel, the 3.6 is more battery and RAM hungry.
Can someone point me in the direction of a flashable stock kernel? I can't seem to find one, and i prefer running custom roms, but with the stock kernel.
If I cant find one, does someone mind building one for me from source? I would really appreciate it. If you could build it, and send me the zimage with the libs, I could do the rest.
Also, would packing the boot.img from the stock rom into a flashable zip work on CM, AOKP or other custom roms? I know they change some things that make the stock kernel and components unusable, just curios.
I started to set up a build machine, but my pc does NOT have the resources necessary. I have to run linux on a VM and I only have 2gb of ram. Naturally, that makes things crawl.
Thanks for the help.
Dude... Look on the stickies. Use the search function or Google. Don't be lazy. You are obviously not a complete idiot, so use the resources available to you. This device has been around for awhile so there is a stock kernel here in the forums.
Sent from my SPH-D710 using xda premium
graydiggy said:
Dude... Look on the stickies. Use the search function or Google. Don't be lazy. You are obviously not a complete idiot, so use the resources available to you. This device has been around for awhile so there is a stock kernel here in the forums.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
You're right, sorry.
Sent from my Nexus 4 using Tapatalk 2
http://d-h.st/n51
No need to be sorry. Most of us are more than willing to help. But you gotta make an effort to help yourself. Sorry I came off as a d**k. Just how I am. You can ask almost anyone from the E4GT forums about me.
Sent from my SPH-D710 using xda premium
Yeah, unfortunately I wasn't clear in what I wanted, or I didn't ask correctly. But I did do a little more research after posting and found what I wanted. Although I had to make it myself, as I couldn't find anything like it.
Most kernels are packaged with the kernel and the ramdisk (boot.img). If you run an aosp Rom, you can use the stock boot.img. if you run a CM Rom, you can run a CM boot.img (modified ramdisk).
Now, I want to run the stock android kernel, on a CM Rom. I couldn't find ANYTHING that has that. They all have CM kernels, or variants of, but no stock, from source kernel. Any kernel reset zips include the stock libs and ramdisk which is incompatible with CM (bootloop).
To solve this, I unpacked the stock boot.img (zImage and ramdisk), put the zImage together with Koush AnyKernel, modified the updater-script for the N7 and boom, it worked.
The reason I can run the stock kernel on a CM Rom, is because I didn't mess with the ramdisk. So I can now run ANY Rom with my stock kernel, because I don't mess with the ramdisk.
Make sense? Sorry I wasn't clear before.
Sent from my Nexus 4 using Tapatalk 2
Makes perfect sense. Although, I believe that most custom kernels, including stock based ones can run almost any ROM including CM especially if you are using multirom . Once I get my N7 fixed tonight I will be able to dive into it and find out exactly what I am using because I have no problem with the 6 or 7 ROMs I have on my device.
Sent from my SPH-D710 using xda premium
Thank you.
You're right, I can run any custom kernel on any Rom, but I could never get a stock kernel zip, to not throw CM into a loop. And all kernel devs, who have kernel reset zips, use a disclaimer saying you can't use on CM based roms. I don't fully understand why
Sent from my Nexus 4 using Tapatalk 2
I see. I don't get it either. Quite perplexing.
Sent from my SPH-D710 using xda premium
I want to know if there's a 2.6.36 kernel for our device.
I know there is working 2.6.35 which I have built and used on. But I am specifically interested in 2.6.36 or 2.6.37. The reason is I'm tring to add new io schedule and .35 doesn't support row or fias.
I found some 2.6.36 msm7x30 kernels for samsung, but I can't find one for HTC. (even a dhd kernel will be fine.)
Anyone can help me on this?
Btw, I know 4.1 and 4.0 can run on 2.6 kernel. If I want to port a 4.2 rom, how can I make it work on 2.6 instead of a 3.0 kernel?
The rom has to be able to run off of a 2. kernel. I know PAC 15 does.
N_otori0us_ said:
The rom has to be able to run off of a 2. kernel. I know PAC 15 does.
Click to expand...
Click to collapse
Sorry not quite follow what you said.
Sent from my HTC Glacier using Tapatalk 4