Hi,
Whether and how to can decompile / decompress zImage?
S.
What is your reason to do this?
You can download source code, kernel is OpenSource ;-)
http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.32
I know.
I can do: source to zImage
but I can not do: zImage to source
ATomCZ said:
What is your reason to do this?
You can download source code, kernel is OpenSource ;-)
http://git.linuxtogo.org/?p=groups/mobile-linux/kernel.git;a=shortlog;h=refs/heads/htc-msm-2.6.32
Click to expand...
Click to collapse
Considering how the OP dodged your question, I'd guess he wants to decompile a kernel for which no source code is / has been provided (idk, maybe he got his hands on an "experimental" kernel by Cotulla or something like that). Since that would imply some yet "unofficial" kernel, I'd say it's good that he can't decompile it
I'd be keen to learn a little about it too...
For example at the moment I'm running an older kernel tat has been undervolted/overclocked.
Obviously the kernels released by the devs are not undervolted.
So what I'd like to know is how to take the latest kernel and apply the undervolt/overclock to it or vice versa...
I'm keen to try and get a grasp at how this Linux whatdyacallit works
the_scotsman said:
I'd be keen to learn a little about it too...
For example at the moment I'm running an older kernel tat has been undervolted/overclocked.
Obviously the kernels released by the devs are not undervolted.
So what I'd like to know is how to take the latest kernel and apply the undervolt/overclock to it or vice versa...
I'm keen to try and get a grasp at how this Linux whatdyacallit works
Click to expand...
Click to collapse
git, change, compile...
Anyone got anything worthwhile to say....
I have limited Linux knowledge so a few pointers would be a good start, if possible...not looking for anyone to hold my hand...but looking for something a little more than the previous post.
Thanks
the_scotsman said:
I'd be keen to learn a little about it too...
For example at the moment I'm running an older kernel tat has been undervolted/overclocked.
Obviously the kernels released by the devs are not undervolted.
So what I'd like to know is how to take the latest kernel and apply the undervolt/overclock to it or vice versa...
I'm keen to try and get a grasp at how this Linux whatdyacallit works
Click to expand...
Click to collapse
I'm keen as well, fairly new to programming and whatnot, so this would be very helpful...
Ok so there's a little more info here: http://git.linuxtogo.org/?p=groups/...7;hb=e51cb9c975bb81ae498c286ff28efa89489c3b17
The readme explains a little about how to do it, but it looks like they assume you have a fair understanding of it already...some light reading for me tomorrow then
the_scotsman said:
Ok so there's a little more info here: http://git.linuxtogo.org/?p=groups/...7;hb=e51cb9c975bb81ae498c286ff28efa89489c3b17
The readme explains a little about how to do it, but it looks like they assume you have a fair understanding of it already...some light reading for me tomorrow then
Click to expand...
Click to collapse
thats it! its not to simple... LOL, its impossible to teach such a thing in a post
Sorry, i didn't want to be rude my friend...
the_scotsman said:
I'd be keen to learn a little about it too...
For example at the moment I'm running an older kernel tat has been undervolted/overclocked.
Obviously the kernels released by the devs are not undervolted.
So what I'd like to know is how to take the latest kernel and apply the undervolt/overclock to it or vice versa...
I'm keen to try and get a grasp at how this Linux whatdyacallit works
Click to expand...
Click to collapse
Maybe I'm being too risk-avoiding, but I'd stay away from especially anything that has to do with undervolting and overclocking, even if it means taking the functionality from source code that works and putting it in another piece of code... that may not be the best way to learn about how that kind of coding works
+1 for me too, the reason why I want to know is there is a solution to a problem in one kernel, which I want to see how it was fixed and to see if it can be added to another kernel.
And if you ask why not use the kernel that has the fix, the answer is compatability.
A decent answer wouldn't be bad, for me either.
I recently got a cheap 3Q Q-Pad tabby, which is closed, and 1GHz + 512MB RAM + ICS 4.0.3 is not a good mix :S
Why wont you just get tytungs kernel from guthub?
Related
I was wondering why its been so quite after HTC released the new kernel for the Sprint Hero, I thought that was the missing link that was needed for complete 1.6/2.0/2.1 roms?
It hasn't been quiet.
Also the kernel that HTC released needs to be ported to 2.6.29 to fully work with 1.6+.
All this info is on the forum & easily obtainable.
gu1dry said:
It hasn't been quiet.
Also the kernel that HTC released needs to be ported to 2.6.29 to fully work with 1.6+.
All this info is on the forum & easily obtainable.
Click to expand...
Click to collapse
I just thought we would see some 1.6/2.0/2.1 releases now that the kernel was released, that's all
There's been 1.6+ releases for a while...
Let me elaborate a little here:
This kernel that was released is not a magic bullet, it allows us to see what code needs to be changed to get the correct Kernel to run these newer versions. It also lets us make any performance changes we can find.
All of the changes need to be put into the current kernel source,making it a .29 or whatever we need.
It has been fairly quite, we aren't seeing tons of Roms being thrown out to the market, thankfully. Our devs are taking all the time they need to make sure everything works and is stable. We should see some big stuff happen in the next week or so.
gu1dry said:
There's been 1.6+ releases for a while...
Click to expand...
Click to collapse
Yea but not completely working, which I thought the new kernel would fix?
kyrumo71 said:
Yea but not completely working, which I thought the new kernel would fix?
Click to expand...
Click to collapse
gu1dry said:
the kernel that HTC released needs to be ported to 2.6.29
All this info is on the forum & easily obtainable.
Click to expand...
Click to collapse
/thread....
Kcarpenter said:
Let me elaborate a little here:
This kernel that was released is not a magic bullet, it allows us to see what code needs to be changed to get the correct Kernel to run these newer versions. It also lets us make any performance changes we can find.
All of the changes need to be put into the current kernel source,making it a .29 or whatever we need.
It has been fairly quite, we aren't seeing tons of Roms being thrown out to the market, thankfully. Our devs are taking all the time they need to make sure everything works and is stable. We should see some big stuff happen in the next week or so.
Click to expand...
Click to collapse
Good to know, I guess I'm like a kid in the candy store, thanks for educating me on the kernel process.
Modaco's 2.2 has the customized kernel in it now.. read the front page of the Hero forum for the link..
its very nice..
tyrnight said:
Modaco's 2.2 has the customized kernel in it now.. read the front page of the Hero forum for the link..
its very nice..
Click to expand...
Click to collapse
Yea that's what I'm rocking right now, I'm just impatient for a fully funcional newer OS
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
hallfleming said:
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
Click to expand...
Click to collapse
I unfortunately haven't the answer but I'd like to add that I am curious about this too.
dalingrin said:
I unfortunately haven't the answer but I'd like to add that I am curious about this too.
Click to expand...
Click to collapse
I'll second this and ask that if you do figure it out, please share with the community.
I think that vanilla Roms are a little further away in the future. First step in the process right now would be for someone to be able to compile a kernel from the Samsung released source code that works. Unfortunately the current Captivate kernel source code, when compiled, causes issues (voices garbled, lag when waking up the phone) that are not present in the stock precompiled kernel. These bugs are apparently not present in the other versions of the source code. Once these initial bugs are ironed out, we can truly start down the path of having custom fixes, and the devs can start to focus on bigger challenges, like making the vanilla Eclair or Froyo Roms to start working with our kernel. Good thing about this phone is that there are going to be so many versions of it, that parallel development is happening on multiple platforms. This will likely produce independent breakthroughs that could be theoretically ported between the platforms, but unfortunately it also slows down the development of each platform due to the quirks that have to be overcome. I hope that, in the future, we get to a place where all the source codes are merged into master repository that has all the necessary improvements and the ability to overcome individual platform quirks, so that the development can proceed more rapidly.
hallfleming said:
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
Click to expand...
Click to collapse
Check out this wiki from cyanogen:
http://wiki.cyanogenmod.com/index.php?title=Main_Page
On the bottom right you will see an advanced section that explains how to build from source code. (aosp)
Good luck!!! It's definitely not for me, not with kids and a full time job!
Good info. I haven't seen a post on people testing out the source code testing and their experience. Can you IM or point me to that?
Thanks!
rajendra82 said:
I think that vanilla Roms are a little further away in the future. First step in the process right now would be for someone to be able to compile a kernel from the Samsung released source code that works. Unfortunately the current Captivate kernel source code, when compiled, causes issues (voices garbled, lag when waking up the phone) that are not present in the stock precompiled kernel. These bugs are apparently not present in the other versions of the source code. Once these initial bugs are ironed out, we can truly start down the path of having custom fixes, and the devs can start to focus on bigger challenges, like making the vanilla Eclair or Froyo Roms to start working with our kernel. Good thing about this phone is that there are going to be so many versions of it, that parallel development is happening on multiple platforms. This will likely produce independent breakthroughs that could be theoretically ported between the platforms, but unfortunately it also slows down the development of each platform due to the quirks that have to be overcome. I hope that, in the future, we get to a place where all the source codes are merged into master repository that has all the necessary improvements and the ability to overcome individual platform quirks, so that the development can proceed more rapidly.
Click to expand...
Click to collapse
Also for clarification, when you bought a Nexus One straight from Google for AT&T, was it considered "Vanilla"? Is the build on that phone just like someone downloaded the source for 2.1 and compiled it with the hardware drivers and that's it? I'm wondering what all comes on a "basic" Andriod ROM straight from the source.
hallfleming said:
Also for clarification, when you bought a Nexus One straight from Google for AT&T, was it considered "Vanilla"? Is the build on that phone just like someone downloaded the source for 2.1 and compiled it with the hardware drivers and that's it? I'm wondering what all comes on a "basic" Andriod ROM straight from the source.
Click to expand...
Click to collapse
Nexus One is as Vanilla as it comes. Just straight up Android! I don't think there is anything added to stock 2.1 or 2.2 on the Nexus.
hallfleming said:
Good info. I haven't seen a post on people testing out the source code testing and their experience. Can you IM or point me to that?
Thanks!
Click to expand...
Click to collapse
Most of the kernel compiling struggles are documented here:
http://forum.xda-developers.com/showthread.php?t=740747
Mimocan himself has started some work on it here:
http://forum.xda-developers.com/showthread.php?t=747040
There are also people having success mixing Vibrant ROM on the Captivate with some GPS crash issues:
http://forum.xda-developers.com/showthread.php?t=746466
I am trying to follow those threads, and since I am not a developer, I can't personally contribute to the process. But it is interesting to me anyway.
I've seen these before. I thought they were just edited versions of ROM's sucked off a existing phone. Are these compiled from scratch?
rajendra82 said:
Most of the kernel compiling struggles are documented here:
http://forum.xda-developers.com/showthread.php?t=740747
Mimocan himself has started some work on it here:
http://forum.xda-developers.com/showthread.php?t=747040
There are also people having success mixing Vibrant ROM on the Captivate with some GPS crash issues:
http://forum.xda-developers.com/showthread.php?t=746466
I am trying to follow those threads, and since I am not a deveoper, I can't personally contribute to the process. But it is interesting to me anyway.
Click to expand...
Click to collapse
hallfleming said:
I've seen these before. I thought they were just edited versions of ROM's sucked off a existing phone. Are these compiled from scratch?
Click to expand...
Click to collapse
The first two are attempts to recompile the kernel to put in the ext3/ext4 mimocan fix. The third one I believe is a script for boot logo animation hack to achieve the same thing.
I forgot to mention one more thread:
http://forum.xda-developers.com/showthread.php?t=739823
So we've got the source code with drivers and know which ones to use from the T959 for fixing the voice issue. We've got the stock kernel. What's left to creat a plain jane captivate?
hallfleming said:
So we've got the source code with drivers and know which ones to use from the T959 for fixing the voice issue. We've got the stock kernel. What's left to creat a plain jane captivate?
Click to expand...
Click to collapse
I'm guessing not too much. There are somethings that would need to be edited such as handling the capacitive buttons. The i9000 roms handle buttons differently regardless of the kernel so, its apparently an OS level config.
I've been wanting to work on this but I've been neck deep in source code from work.
Here is a good how to: http://forum.xda-developers.com/showthread.php?t=704561
Thanks for the link. The US codes out there so we don't need i9000 port
Sent from my SAMSUNG-SGH-I897 using XDA App
hallfleming said:
Thanks for the link. The US codes out there so we don't need i9000 port
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
My point was that given the I9000 rom needs source level changes in order to work as expected(haptic feedback on certain buttons, etc) then running an AOSP build may require some source level changes as well. It may not be as simple as building and flashing.
Hi all,
I am so excited now, can't wait to tell all you guys that news
Maybe someone know that I have upgraded our kernel to the newest kernel tree from nvidia's git and waiting for it to be stable for daily use. However, I found it can't boot in the newest ACER's stock ROM yesterday. After one full day hack, it finally can boot in the stock ROM now.
However, the last function I can't confirm is HDMI support, so I want some volunteers to test HDMI support and the stability. If you use vache's Taboonay 0.9.x and are interested in it, please PM me
Thanks
I can test the stability, but not the HDMI output.
P.S : Nice to see you here roggin
I can test hdmi, only 720p, but at least I can verify that.
roggin said:
Hi all,
I am so excited now, can't wait to tell all you guys that news
Maybe someone know that I have upgraded our kernel to the newest kernel tree from nvidia's git and waiting for it to be stable for daily use. However, I found it can't boot in the newest ACER's stock ROM yesterday. After one full day hack, it finally can boot in the stock ROM now.
However, the last function I can't confirm is HDMI support, so I want some volunteers to test HDMI support and the stability. If you use vache's Taboonay 0.9.x and are interested in it, please PM me
Thanks
Click to expand...
Click to collapse
What kernel is it? If I may ask.
Can it OC?
Johnny0906 said:
What kernel is it? If I may ask.
Can it OC?
Click to expand...
Click to collapse
Nvidia's kernel is the ORIGINAL kernel, all others base their continued work on, so Acer use these updates as reference..
Can you check up on the bluetooth issue on this kernel you make..
I know tiamat/xoom kernel is really close to stock nvidia kernel too (or fully supported with drivers). so maybe something dirty needs changing..
havent had chance to fix..
problem for now, seems to be it can scan, but seems to timeout on transmitting, so it suddenly cannot see new units after some minutes. maybe worth doublechecking.
vache said:
I can test the stability, but not the HDMI output.
P.S : Nice to see you here roggin
Click to expand...
Click to collapse
Hi vache,
Coooool, it's so nice to see you here
I have pm you the link, please take it a try
Thanks for your help again
Johnny0906 said:
What kernel is it? If I may ask.
Can it OC?
Click to expand...
Click to collapse
sorry, I haven't added OC code in it, but I will add it when it stable enough
Thanks
Dexter_nlb said:
Can you check up on the bluetooth issue on this kernel you make..
I know tiamat/xoom kernel is really close to stock nvidia kernel too (or fully supported with drivers). so maybe something dirty needs changing..
havent had chance to fix..
problem for now, seems to be it can scan, but seems to timeout on transmitting, so it suddenly cannot see new units after some minutes. maybe worth doublechecking.
Click to expand...
Click to collapse
Hi Dexter_nlb:
I have tested the bluetooth function in this kernel, it works fine in my kernel
If you are interested in it, I can mail or share a link of my kernel source for you
Thanks
roggin said:
However, the last function I can't confirm is HDMI support, so I want some volunteers to test HDMI support and the stability. If you use vache's Taboonay 0.9.x and are interested in it, please PM me
Click to expand...
Click to collapse
Hi Roggin,
I play with versions and can test HDMI 1080P with Taboonay 0.9.1. Please send me the link to kernel. Do you make also modules, especialy for 3G?
roggin said:
Hi Dexter_nlb:
I have tested the bluetooth function in this kernel, it works fine in my kernel
If you are interested in it, I can mail or share a link of my kernel source for you
Thanks
Click to expand...
Click to collapse
please do i would love to play around with it "internally" and testing...
im little occupied atm, so hdmi can be tested, and regular use for now..
I can probably make you the oc add-ons and see how it turns out with your work and send you my diff back.. (don't know git commit)
I would be willing to due some stability testing with the acer stock rom.
Let me know.
Dexter_nlb said:
please do i would love to play around with it "internally" and testing...
im little occupied atm, so hdmi can be tested, and regular use for now..
I can probably make you the oc add-ons and see how it turns out with your work and send you my diff back.. (don't know git commit)
Click to expand...
Click to collapse
Hi Dexter_nlb,
It's a big big help that you can help me ,
I am not releasing kernel source is because I don't want to brick someone's tablet, but It's ok for power developer like you.
I am uploading the kernel, I will info you when uploading done
Thanks for your help
snickle said:
I would be willing to due some stability testing with the acer stock rom.
Let me know.
Click to expand...
Click to collapse
Hi snickle,
I think it's fine using Taboonay's ramdisk in stock rom, but not sure
If you can help me for test, I will pm the link for you
Thanks
roggin said:
I am not releasing kernel source is because I don't want to brick someone's tablet
Click to expand...
Click to collapse
If they know how to compile it, then I guess they can enjoy their brick
Just be careful not releasing the source code, as it is under a open licence. I'm pretty sure that's why thor2002ro's kernel thread was deleted by moderators off fo this forum. I don't want to see another Kernel development go south because it wasn't public .
roggin said:
Hi snickle,
I think it's fine using Taboonay's ramdisk in stock rom, but not sure
If you can help me for test, I will pm the link for you
Thanks
Click to expand...
Click to collapse
I think the usage of ramdisk should be optional, because it might not allow to encrypt your device, and as you hopefully know, encryption is necessary to allow exchange activesync connection for email push, except if somebody finds out a what has to be modified to use activesync without encryption.
I also join ShadowXVII concerning the kernel source, if somebody wants to brick his device, it's up to him, but be carefull not to get removed because you did not publish the source.
otherwise well done my friend.
zoubidou said:
I also join ShadowXVII concerning the kernel source, if somebody wants to brick his device, it's up to him, but be carefull not to get removed because you did not publish the source.
Click to expand...
Click to collapse
You only have to publicly release the source if you publicly release the binary - he's only obliged to give the source to the people he gave the binary to. So there's no problems
On that note: I've just flashed Taboonay and am happy to give your kernel a try. I don't have a dev environment set up these days, but if you can send me the boot.img I'll take a crack at it.
themono said:
You only have to publicly release the source if you publicly release the binary - he's only obliged to give the source to the people he gave the binary to. So there's no problems
Click to expand...
Click to collapse
Cool, thanks for the clarification. Just being cautious as I'd prefer Kernel development wasn't hindered at all. That being said, a public source may promote development as opposed to ending up with several different kernels by different developers. I'm all for collaboration, and it's great to see some within this thread
On a side note, any Kernel developers that may be able to shed some light onto this thread would be appreciated -- in particular, the kernel requirements for networking over USB; http://forum.xda-developers.com/showthread.php?p=15452414#post15452414
Hi all,
It's not I don't want to release it. It's almost 300+ patches between older and newer version, and include some regulator voltage patch. I want to sure not damage any part in all functions.
Give me one more days, when I collect all necessary response from tester, I will release it
Thanks
I did exactly the same on the tiamat kernel, waited and hoped to had time debugging the bluetooth issue, but got modarator complaints on not publicing any source
anyways, as long as no binary appear in this thread, i think you're safe from any mods attacking you on GPL issues (or do like thor200ro move it offsite, if you feel like breaking GPL)
Talk is just talk for now, no mods can argue against that for now..
I'm preparing to be flamed, but I figured I might as well create this thread. Now I know many of you know this, along with the i896 source, is out, but there wasn't a thread for it and the i896 one had issues, so here . Hopefully we can get some development going for those of us that want *shutters* Audience Chip drivers, along with the many features that are present in the i9000 roms.
Just search KK4 on here: https://opensource.samsung.com/index.jsp
nygfan760 said:
I'm preparing to be flamed, but I figured I might as well create this thread. Now I know many of you know this, along with the i896 source, is out, but there wasn't a thread for it and the i896 one had issues, so here . Hopefully we can get some development going for those of us that want *shutters* Audience Chip drivers, along with the many features that are present in the i9000 roms.
Just search KK4 on here: https://opensource.samsung.com/index.jsp
Click to expand...
Click to collapse
Doesn't bother me anymore since now ICS is doing great.
But, if really want to stick with GB(usually MIUI and CyanogenMOD).
I would like:
a.) The Audience Chip thingy.
b.) Battery life.
Fate-Silver said:
Doesn't bother me anymore since now ICS is doing great.
But, if really want to stick with GB(usually MIUI and CyanogenMOD).
I would like:
a.) The Audience Chip thingy.
b.) Battery life.
Click to expand...
Click to collapse
What? I'm not making anything. I was informing the community (those who didn't know) of the source code.
nygfan760 said:
What? I'm not making anything. I was informing the community (those who didn't know) of the source code.
Click to expand...
Click to collapse
Yea, I know.
I just want to tell AT&T/Samsung is SLOW for their firmware codes sharing... too stingy...
Fate-Silver said:
Doesn't bother me anymore since now ICS is doing great.
Click to expand...
Click to collapse
yea I been onICS for 24 hours now ,, its great , but nothing special I see very few differences in anything , except I am missing all of the features I m use to on GB .
imo dotn believe the hype , the only 2 things I like about my current ICS set up is sixstring kernel allows me to OC higher then on sammy rom (not higher then cm7 tho) and the launcher is pretty cool but still not as nice as on the gnex .
Eventho its 2.3.5 I welcome source of KK4
eventho Im 2.3.6 (i9000 base )
I'm looking forward to the more refined kernels the source code release should bring around. Those features we've been missing will now be possible.
nygfan760 said:
I'm preparing to be flamed, but I figured I might as well create this thread.
Click to expand...
Click to collapse
Why? There is already a thread created in General. This is where searching comes in handy.
Red5 said:
Why? There is already a thread created in General. This is where searching comes in handy.
Click to expand...
Click to collapse
Saw the thread. It is a discussion thread about the firmware, this thread is to alert people of the actual source code, so we can get new kernels and stuffs Also, aren't most source code threads posted in here? At least for Froyo, and i896 GB, I believe they were.
Audience chip support was already extracted from the I896 gingerbread source kernel. It is available in the i9000 captivate corn kernel. Specifically gave me thanks for being able to introduce audience tip finally.
If you would like Audience support in any other kernels just contact the developer of corn.. A few months ago
TRusselo said:
Audience chip support was already extracted from the I896 gingerbread source kernel. It is available in the i9000 captivate corn kernel. Specifically gave me thanks for being able to introduce audience tip finally.
If you would like Audience support in any other kernels just contact the developer of corn.. A few months ago
Click to expand...
Click to collapse
I know, I know, I have been running it for a while now.
but im surprised that kk4 was final release. had time-stamp issue.
but now if we can get a unbranded kernel, we can have a complete unbranded rom with the ATT removal mods i posted while back.
TRusselo said:
but im surprised that kk4 was final release. had time-stamp issue.
but now if we can get a unbranded kernel, we can have a complete unbranded rom with the ATT removal mods i posted while back.
Click to expand...
Click to collapse
I'm pretty sure that problem only happens when you put AT&T software on an i896. I can't say for sure though because both my cappy's are canadian. Anyways I don't think ts a problem with the phone per se.. I think its a network thing. There is no time stamp issue for people on the AT&T network that I know of.
KK4 Source has been available since around Christmas. Some of the I897 kernel devs have been trying to compile a kernel from source but have been running into issues with the kernel not booting which is why you haven't seen any yet.
erbsmokah said:
I'm pretty sure that problem only happens when you put AT&T software on an i896. I can't say for sure though because both my cappy's are canadian. Anyways I don't think ts a problem with the phone per se.. I think its a network thing. There is no time stamp issue for people on the AT&T network that I know of.
Click to expand...
Click to collapse
Its a network AND software issue. Either they can fix the problem though the network, (its been done before) or you can de-compile the MMS.apk and change a line of code to fix the problem.
Kyuta Syuko said:
KK4 Source has been available since around Christmas. Some of the I897 kernel devs have been trying to compile a kernel from source but have been running into issues with the kernel not booting which is why you haven't seen any yet.
Click to expand...
Click to collapse
that was the kh2 rogers i896 source that they were having trouble with.... or are they having trouble with kk4 also???
TRusselo said:
Its a network AND software issue. Either they can fix the problem though the network, (its been done before) or you can de-compile the MMS.apk and change a line of code to fix the problem.
that was the kh2 rogers i896 source that they were having trouble with.... or are they having trouble with kk4 also???
Click to expand...
Click to collapse
He is a kernel dev but yeah I hope that isn't the problem.
TRusselo said:
that was the kh2 rogers i896 source that they were having trouble with.... or are they having trouble with kk4 also???
Click to expand...
Click to collapse
Both JSmokey and I haven't been able to get a kernel compiled from the KK4 source that we had gotten around Christmas. Though JSmokey said he did have a working kernel before, but isn't certain what he did to make it not work anymore. I've even tried to compile a stock kernel per the included instructions with no luck...
Kyuta Syuko said:
Both JSmokey and I haven't been able to get a kernel compiled from the KK4 source that we had gotten around Christmas. Though JSmokey said he did have a working kernel before, but isn't certain what he did to make it not work anymore. I've even tried to compile a stock kernel per the included instructions with no luck...
Click to expand...
Click to collapse
Same here, there must be something missing. Pulling a dmsg doesn't give much help, something about wanting sh in /system/bin (I think).
I have moved over to cyanogenmod 7 for now, waiting for cm9. Lots to tinker with there.
boog said:
Same here, there must be something missing. Pulling a dmsg doesn't give much help, something about wanting sh in /system/bin (I think).
I have moved over to cyanogenmod 7 for now, waiting for cm9. Lots to tinker with there.
Click to expand...
Click to collapse
.... no our original 2.3 kernel dev has given up
Sounds like the only way to get bln is to go to 2.2 or i9000.
Wdustin1 said:
.... no our original 2.3 kernel dev has given up
Click to expand...
Click to collapse
Maybe we can ask DG for help. I know he has moved on a long time ago, but recently he came back and helped with ICS kernel development. If he could help us getting KK4 kernel compiled from source, I am sure we will see a lot more ROM development going on.
Hi there,
I'm trying to build some froyo rom for g1 from source. The problem is that lot of stuff lying here is old, unusable slow or hopelessly broken. The only rom that seems to work is hxxp://forum.xda-developers.com/showthread.php?t=1273549
[Rom][2.2.3 AOSP] DREAMteam Froyo v2.0.0 [9/3/2012]
The kernel source can be easy found by Ezterry
hxxps://github.com/ezterry/kernel-biff-testing/tree/ezgb-2636-v1.5.2-20111106
but I can't find any (git) repo or hint how the "DREAMteam" guys built it. :crying:
Thanks in advance for any hints,
ptau
pm the devs
Sent from my HTC Vision using xda premium
All you need for building the kernel is here at this url:
https://github.com/ezterry/manifest-gingerbread-DS/blob/gingerbread/README.mkdn
It used to be on the ezgingerbread rom thread but seems he has a link to the guide which is now on github ^_^
Sent from my GT-I9300 using xda app-developers app
xillius200 said:
All you need for building the kernel is here at this url:
https://github.com/ezterry/manifest-gingerbread-DS/blob/gingerbread/README.mkdn
It used to be on the ezgingerbread rom thread but seems he has a link to the guide which is now on github ^_^
Click to expand...
Click to collapse
Building the kernel for froyo or building the ezgingerbread rom is no problem:
http://forum.xda-developers.com/showthread.php?t=882356
Unfortunately (Ez)gingerbread is an overkill for the tiny G1
My problem is to find out how to build a froyo rom that is not
broken (e.g. cm6). The DREAMteam's
http://forum.xda-developers.com/showthread.php?t=1273549
rom seems to have the most bugs fixed, but again I don't know
how to build it. I need the right android manifest, git repo, etc.
The DREAMteam changelog is astonishingly sparse:
V2.0.0 - 2012-03-09
Update to android 2.2.3. Some changes from 1.9.2 included.
Thanks ptau
ptau said:
Building the kernel for froyo or building the ezgingerbread rom is no problem:
http://forum.xda-developers.com/showthread.php?t=882356
Unfortunately (Ez)gingerbread is an overkill for the tiny G1
My problem is to find out how to build a froyo rom that is not
broken (e.g. cm6). The DREAMteam's
http://forum.xda-developers.com/showthread.php?t=1273549
rom seems to have the most bugs fixed, but again I don't know
how to build it. I need the right android manifest, git repo, etc.
The DREAMteam changelog is astonishingly sparse:
V2.0.0 - 2012-03-09
Update to android 2.2.3. Some changes from 1.9.2 included.
Thanks ptau
Click to expand...
Click to collapse
Well I got in touch with tval aint spoke to him for a while. He said a repo was never made for DREAMteam froyo and the way in which it was created some by pushing files not everything was coding, there was not much point in a repo and he has not got around to it lol and I totally agree with him. So best thing would be to compile a rom from plain AOSP and begin to modify it yourself, this way you learn and better understand rom creation. Plus doing it straight from AOSP will give you the updates you want and in most ways will actually be better ^^ If you want any help I could always introduce you to a few devs see if they would be willing to help ^^
PS: From how you worded your first post it sounded like you were trying to compile just the ezterry kernel xD so I apologise that I misunderstood ^^
99%
xillius200 said:
As far as I remember when it was first started they never had a repository and unless it has changed they still do not lol ill email tvall later lol seems Ldrifta is gone.... :'( if not you can always just compile a normal aosp and then customize it to your liking and speed helps you learn on how to speed up roms that way unlike having an already fast rom of which you learn less from.
Click to expand...
Click to collapse
Thanks. After I looked in the zip, I thought something like that.
Seriously, you don't need speed with this hardware.
Think of cheap, stable, not battery eating
and hackable ARM11 development platform
After that incident with kernel.org they removed all the old android repos
so I have hard times to find the G1 pieces again. ezterry rocks. The kernel
changes are in his git, I could tweak+build the kernel with all the
modules I needed.
Let's see how to get the aosp together ...
(any hints greatly appreciated
PS: From how you worded your first post it sounded like you were trying to compile just the ezterry kernel xD so I apologise that I misunderstood ^^
Click to expand...
Click to collapse
I know, but my German is much better, I swear :angel:
Well.. I'd be happy to help rebuild my rom. Been wanting to set up a repo, but I'm lazy..
tvall said:
Well.. I'd be happy to help rebuild my rom. Been wanting to set up a repo, but I'm lazy..
Click to expand...
Click to collapse
Thanks for the email with tips.
I try to document the building process here:
hxxps://sites.google.com/site/aospdream/
As always, any hints or help from anybody are greatly appreciated ...
Thanks,
ptau