Related
Inspired by supercurio creating a master git repo for SGH-I997R development, I'm in the process of uploading today's source release from Samsung of the Gingerbread kernel for the Rogers Infuse 4G. (I'm surprised none of the other kernel hackers here have already done it... )
See supercurio's post http://forum.xda-developers.com/showthread.php?t=1054738 for more info on why git is good, and superior to kernel devs using tarballs directly from Samsung. This method is already unofficially how the kernel devs have been working - nearly every kernel here is forked from gtg465x's github repo.
I don't plan on directly doing development on this repo - It's just here as a starting point for everyone else to fork from. Some of us have slow upstream, so it's easier to pull a fork than it is to push a tarball import. However I might consider pulling in basic fixes to this repo (.gitignore, Makefile fixes - basically the same things supercurio has fixed in his unified git repos). (Edit: I'm starting to consider doing things a bit differently in order to allow this to stay as a relevant reference - After all there are certain "core" features like Voodoo Lagfix/Sound that have no known detrimental effects and are basically expected from any kernel used by the community.)
One thing is that most of the other ref repos are on a github "team" account - mine is on a personal account. I'm going to look into whether I can change this without breaking the fork relationships.
The repo is located at https://github.com/Entropy512/linux_kernel_sgh-i997r
Initramfs from Wednesday's dump is at https://github.com/Entropy512/initramfs_sgh-i997r
Note: If someone creates a better "master" repo for everyone to track, I'll happily edit this post to point there.
Update: Merged a pull request from LinuxBozo that has a bunch of .gitignore fixes and Makefile fixes.
Good work! Looking now.
Entropy512 said:
Inspired by supercurio creating a master git repo for SGH-I997R development, I'm in the process of uploading today's source release from Samsung of the Gingerbread kernel for the Rogers Infuse 4G. (I'm surprised none of the other kernel hackers here have already done it... )
See supercurio's post http://forum.xda-developers.com/showthread.php?t=1054738 for more info on why git is good, and superior to kernel devs using tarballs directly from Samsung. This method is already unofficially how the kernel devs have been working - nearly every kernel here is forked from gtg465x's github repo.
I don't plan on directly doing development on this repo - It's just here as a starting point for everyone else to fork from. Some of us have slow upstream, so it's easier to pull a fork than it is to push a tarball import. However I might consider pulling in basic fixes to this repo (.gitignore, Makefile fixes - basically the same things supercurio has fixed in his unified git repos)
The repo is located at https://github.com/Entropy512/linux_kernel_sgh-i997r - There is nothing visible there yet as the push is still in progress. It should be done within 30 minutes or so.
I don't have an initramfs repo yet - we need an initramfs dump from a device first.
Note: If someone creates a better "master" repo for everyone to track, I'll happily edit this post to point there.
Click to expand...
Click to collapse
Absolutely awesome news :-D
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Oh blast, hadn't even seen that kernel code was available... thanks Entropy!
A personal favor I'd like to ask of people forking - try to keep things to one feature per commit. An example being LinuxBozo's ext4 backport to the Froyo kernels - it was simple and easy to apply to other kernels. As opposed to someone had a massive supercommit that added a whole bunch of stuff at once, making it hard to either pick-and-choose or hard to apply if they had already applied a single-feature commit for one of the features. (One example being a commit that combined something like TinyRCU, jhash3, and BFQ all in one. I don't remember exactly what it was.)
Entropy512 said:
A personal favor I'd like to ask of people forking - try to keep things to one feature per commit. An example being LinuxBozo's ext4 backport to the Froyo kernels - it was simple and easy to apply to other kernels. As opposed to someone had a massive supercommit that added a whole bunch of stuff at once, making it hard to either pick-and-choose or hard to apply if they had already applied a single-feature commit for one of the features. (One example being a commit that combined something like TinyRCU, jhash3, and BFQ all in one. I don't remember exactly what it was.)
Click to expand...
Click to collapse
Defuse kernel
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Is that all we needed for gb roms or is there still more needed?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
nelomen said:
Is that all we needed for gb roms or is there still more needed?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Click to expand...
Click to collapse
Initramfs, radio firmware dump, proper /system dump. Ours is incomplete.
Updates:
Merged LinuxBozo's pull request with build fixes
Merged LinuxBozo's pull request with the rainbow fix
Added initramfs repo
Entropy512 said:
Updates:
Merged LinuxBozo's pull request with build fixes
Merged LinuxBozo's pull request with the rainbow fix
Added initramfs repo
Click to expand...
Click to collapse
Nice!! Anything buildable yet?
ookba said:
Nice!! Anything buildable yet?
Click to expand...
Click to collapse
should be buildable since initramfs is available, tomorrow gtg's voodoo commit should be available too. this is all very exciting.
ookba said:
Nice!! Anything buildable yet?
Click to expand...
Click to collapse
A few more things got pulled in last night.
Kernel - not much
Initramfs - Working CWM - or at least it comes up, it hasn't been fully tested functionally yet
As of last night a few people have custom kernels running including myself, although some people still can't boot them. CWM wasn't working until past midnight...
Next up is voodoo - Not sure if I'll include that in the main initramfs repo or not. Maybe as a branch. It is a fairly standard mod, so it should be in a readily accessible repo
Bad news - as I said before CWM hadn't been fully tested.
Apparently, after further testing, it still does indeed have some pretty severe issues.
Sadface
10c
P1 Wookie said:
Sadface
10c
Click to expand...
Click to collapse
We have what seems to be working CWM and Voodoo thanks to gtg - in testing now.
The trolls in IRC aren't helping. Not a good time for the ops to be AFK.
trolls suck.
GL guys.
Entropy512 said:
We have what seems to be working CWM and Voodoo thanks to gtg - in testing now.
The trolls in IRC aren't helping. Not a good time for the ops to be AFK.
Click to expand...
Click to collapse
Gotta love the trolls.
Good luck guys. I know you all will figure it out
Well, thanks to the blasted trolls and the unfortunate circumstance of my only internet being my phone, I'm borked from being able to participate in the main infuse4g room as webchat is banned (for a good reason) and I can't get past the SASL issue otherwise.... oh well.
bedwa said:
Well, thanks to the blasted trolls and the unfortunate circumstance of my only internet being my phone, I'm borked from being able to participate in the main infuse4g room as webchat is banned (for a good reason) and I can't get past the SASL issue otherwise.... oh well.
Click to expand...
Click to collapse
why no use of a client?
drowningchild said:
why no use of a client?
Click to expand...
Click to collapse
Finally got it to work, had to hack a command line client.... urg.
11/22/11 Update: Added "reboot bml8 recovery" patch for ROM Manager suppport.
11/8/11 Update: Updated keyfix kernel with the EI22 initramfs. Also, Samsung has placed the previous official (and now labeled EI22) source tarball on their opensource site.
10/24/11 Update: It appears that Samsung has removed the "official" Epic GB source tarball from their website. I've mirrored it for anyone interested in the original release. For anyone actually looking to build with the sources, you're probably better off using Rodderik's GitHub
10/19/11 Update: As everyone's found out by now, Samsung released official Epic GB sources last night. There's not that many changes to our device in the official source tree compared to the previous, but a few appear to be subtlely important (see abbreviated deltas). It still needs some work to get into a buildable state, but it does appear to work great on EH17!
I've updated most of my patches for GB, conveniently packaged together. I've also uploaded a new EH17 kernel that works on stock (rfs) EH17 ROMs and includes the keyboard fixes with optimized values, along with userdebug and kexec support. Feel free to give it a try.
Meanwhile Rodderik is updating his GitHub repo to include all these patches for folks to clone from, stay tuned.
Happy hacking!
So apparently when Samsung released the kernel sources to the Mesmerize's Gingerbread update a month-and-a-half ago, that source tree contained almost-buildable kernel sources for our device as well.
I've patched the sources (removed modemctl definition, added tfsr driver, compile right camera driver) to build for the Epic. I've also built a custom EH17 kernel combining these sources with the EH17 initramfs. It's essentially stock EH17 with ro.debugging=1, adbd always-spawning during recovery, and testkey signature verification. I'll get to porting over some other patches (like the dropped key fix) soon.
As for compatibility with EH17, the source tree itself appears to have been checked out on 8/30 and looks to include everything EH17 does. I ran "strings Image | sort -u" on both kernels to make sure there weren't any obvious strings/symbol differences between them. The ones that remain appear to be minor, but legitimate fixes.
Thanks to jt1134 & Rodderik for pointing out that the Mesmerize source released contained Epic code, and Tortel & ugothakd for testing.
GitHub repo, thanks Rodderik!
To build:
Grab SCH-I500_USCC_Opensource_Update3.zip SPH-D700_GB_Opensource.zip from opensource.samsung.com, extract.
Run "make mrproper" to get rid of atlas (Mesmerize) config junk.
Patch to complete Epic support.
Build with EH17 initramfs as usual, use victory_8G_defconfig for kernel configuration.
Mirror links:
Official GB sources: SPH-D700_GB_Opensource.zip (originally posted on opensource.samsung.com, since removed.)
Epic GB source patches: kernel-GB-3a-patches.tar.gz
Source-compiled, keyboard fix EI22 kernel: kernel-GB-3a.tar.md5
(URLs for Mesmerize tree patches removed, although they're still valid.)
Flashed this yesterday(11/13). Working good so far.
Edit: Oh, and first! Sorry iSaint
Sent from my SPH-D700 using Tapatalk
HAHAHAHA! Epic. I love you guys!
Yeah, um, I love you. <3 lol.
No. I was first. I tested it lol
[edit] actually, tortel was first. but that was before i got on board.
Hmmmm...who would of known part of our kernel source was right under our noses
Sent from my SPH-D700 using xda premium
It just occurred to me that, with this finding a lot of good can happen, as well as ICS tomorrow. Depending on timezone I should say.
Sweet. Hopefully this'll help cm7
Heart just stopped beating LOL!
What about stratosphere then?
Oh well nice work!
Sent from my SPH-D700
winning
bet samsung was just watching and waiting to see how long it took one of you/us to figure it out, lol.
this is wonderful news
Ceelos09 said:
Hmmmm...who would of known part of our kernel source was right under our noses
Click to expand...
Click to collapse
Ideally there would be one Samsung Android kernel source tree that would contain code for our device as well as all their others. However, I've been checking somewhat recently and code for Epic never appered in the GT-I9000 sources (which have been updated recently) nor in the Stratosphere ones.
It didn't occur to me to check the Mesmerize sources sooner, but as the only US device with an official GB release (still?) it shouldn't have been much of a surprise. It's also worth nothing that there appears to be GB sources for the Indulge in there as well. I'm not sure of their buildability though.
GREAT work mkasick.... everyone be SURE to thank him!
SWEET !!!
Exciting! Do the cm7 guys know about this, or is already used in the build we have?
Neckberg said:
Exciting! Do the cm7 guys know about this, or is already used in the build we have?
Click to expand...
Click to collapse
I'm not sure, JT helped Decad3nce with CM 7 though and they both hacked the EH17 kernel to work for this. So hopefully it's something Decad3nce can use.
He said he was moving so he probably won't be back until tomorrow.
Neckberg said:
Exciting! Do the cm7 guys know about this, or is already used in the build we have?
Click to expand...
Click to collapse
The main CM7 people are Decad3nce and jt and they haven't been on irc today.
this is exactly what we been needing...THANK YOU VERY MUCH mkasick!! You rock my friend!
Downloading now - going to see if I can compile a bootable kernel
Sent from my CyanogenMODed Epic
Neckberg said:
Do the cm7 guys know about this, or is already used in the build we have?
Click to expand...
Click to collapse
I believe JT was the one who discovered the Mesmerize sources were pertinent to us. He might've been able to compile something, but at least Rodderik was stuck on the missing tfsr driver without the right debugging bits.
I discovered this worked somewhat haphazardly when Rodderik mentioned the Mesmerize sources to me. They booted the first time with EH17 on SD, but wouldn't boot from flash. Since I was able to get it to boot off SD, debugging was a good deal easier.
In any event, it's a drop-in replacement for the current kernel used by the Epic CM7 build, so I'm sure they'll make good use of it sooner or later.
Actually what I'm curious about is if the reboot problems still persist with this. I haven't had one yet, but they haven't been a problem with stock EH17 on my device either.
A third zip file has appeared in the Samsung Open Source Site called SGH-T959V-TMB_GB_Opensource.zip.
It might possibly be the gingerbread source code for KJ6. Hope this is okay to post in the development section.
https://opensource.samsung.com
I'm downloading the file now to see what it might be.
This was discovered 2 days ago.
You do realize it is the GB code for KJ6 everyone was happy for. Hence the thread on MIUI and CM7
So are you going to be putting together a KJ6 kernel with CWM and voodoo, airfliup? The fancy stuff can come later but with dsexton not having a computer and so on you might have to do it. Should be easier from the source than dr. honk's patching compiled machine code.
Woohoo!
SGH-T959V - USA - T959VUVKJ6 - SGH-T959V-TMB_GB_Opensource.zip
I am not good with kernels, still learning. Also I have to use virtual box for Linux.
Sent from my SGH-T959V using xda premium
so does this mean more stable roms?
maybe, or they could make a kernel that doesn't work at all. Looks like nobody has done anything with the source code yet.
Sorry if this has been asked, but I checked a lit of the q&a but is there any hope or any developers working on ICS for us? And because I don't know much why is it hard to port to the sgs 4g?
Sent from my SGH-T959V using XDA App
An entire kernel needs to be built from practically scratch... Its a tonnnn of work. And our GB source JUST came out...
Sent from my SGH-T959V
OK sorry, like I said I don't know much and just was curious. Thank you for the info tho
Sent from my SGH-T959V using XDA App
tehgyb said:
An entire kernel needs to be built from practically scratch... Its a tonnnn of work. And our GB source JUST came out...
Sent from my SGH-T959V
Click to expand...
Click to collapse
Really? I know some (almost all except the very newest ones) of the Motorola phones have completely locked boot loaders which prohibit any unauthorized kernel from being loaded. Take for example, the Milestone and the Milestone xt720- they were forced (figuratively speaking) to build roms for Froyo and Gingerbread off of the same, crappy kernel that was released with Eclair. They have done a lot, it's far from stable. Which surprises me considering how bad the phone was, how few people got it, and the general negative attitude that tends to flow through Xda.
I don't know much about it- for example, once the kernel is built for gingerbread, does a new one need to be built, or can that kernel be repurposed?
How about building a Gingerbread Kernel ( CM7 based )
Now that they have finally released a Gingerbread source for the 4GS, It would be nice to have a CM7 build. I know the Devs are busy with ICS, or other products, but if one would be willing to work with me, I'd be willing to make a jab at it. I can currrently build the released kernel, but something is missing that I can not get the zimage to successfully load. It is also smaller in size. The only referenced web discussion I could find was for the I9003 series and there are files mentioned that are not part of the 4G. Any help would be appreciated.
mccabet said:
Now that they have finally released a Gingerbread source for the 4GS, It would be nice to have a CM7 build. I know the Devs are busy with ICS, or other products, but if one would be willing to work with me, I'd be willing to make a jab at it. I can currrently build the released kernel, but something is missing that I can not get the zimage to successfully load. It is also smaller in size. The only referenced web discussion I could find was for the I9003 series and there are files mentioned that are not part of the 4G. Any help would be appreciated.
Click to expand...
Click to collapse
Oh trust me, devs are looking at cm7. I know I am, like its a big New York steak!
But its going to be a while, unless you can employee me to work on it. Otherwise... Gotta pay the bills before I have fun.
Sent from my SGH-T959V using xda premium
I know that and realize other priorities make everyones time valuable. I am trying to get up to speed and just need a little bit of help getting the base kernel to build. I have successfully built the CM7 in the past for the captivate, but this is the first time for an raw, untouch source release from samsung.
Thanks for your input.
Also, just to note. There are multiple kernel devs here.
Still waiting for drhonk to release some Bali goodness.
My kernel has a different goal and approach from drhonk's. Search the op of my kernel thread for 'plan'.
As usual, all code is GPL and is available on github (see my signature), so if you want to learn or help out, start with the source.
Sent from my SGH-T959V using xda premium
finch8423 said:
Really? I know some (almost all except the very newest ones) of the Motorola phones have completely locked boot loaders which prohibit any unauthorized kernel from being loaded. Take for example, the Milestone and the Milestone xt720- they were forced (figuratively speaking) to build roms for Froyo and Gingerbread off of the same, crappy kernel that was released with Eclair. They have done a lot, it's far from stable. Which surprises me considering how bad the phone was, how few people got it, and the general negative attitude that tends to flow through Xda.
I don't know much about it- for example, once the kernel is built for gingerbread, does a new one need to be built, or can that kernel be repurposed?
Click to expand...
Click to collapse
you seem to be forgetting that every device except for the SGS1 series takes a boot.img this makes it a lot easier to do things because of the partition layout. sgs1 series uses zImage with initramfs, and has a BML/RFS file system. Not ext4, mtd, yaffs2, ext3...but a **** file system.
krylon360 said:
you seem to be forgetting that every device except for the SGS1 series takes a boot.img this makes it a lot easier to do things because of the partition layout. sgs1 series uses zImage with initramfs, and has a BML/RFS file system. Not ext4, mtd, yaffs2, ext3...but a **** file system.
Click to expand...
Click to collapse
Yea, don't sweat this quite yet, Krylon360
I say we work on the cwm that converts to ext4 like epic4g, like you'd suggested in irc. I already have some code and tests in place to convert to mtd. It's just not in any kind of stable/usable/releasable form yet. It's still early code.
When (hopefully soon) I get time, and hopefully an email back from chipworks about some info I need, I'm going to get u-boot rolling. It's hard for me to explain all the benefits of this now, but some snippets:
fastboot mode (say, flash an mtd partition like: fastboot flash <partition name> <file>)
android usb gadget support (adbd) in u-boot (say to have early console access at the bootloader), and plenty of other goodies.
many other things I just don't have time to list, on top of the fact that we can now control the bootloader...
doing the auto conversion is cake. it's just a bit inside init.rc that tells it to run a script in /sbin, that script is just a quick conversion to ext4. as long as /system, /data, and /cache have the ext4 mounting bit in init.rc, and the ext4.ko is in /lib/modules, it should would just fine.
I'll get the script while Im at work tomorrow.
Krylon360,
you mentioned the initramfs being combined with the zimage. Can you shed some light on how this is done?
bhundven,
Thank you for your help. I will be checking out your source to look over and looking at your forum. Thanks Again!
I know everyone has prob said this. But I'm willing to test betas and such for the sgs4g. Let me know if I can. Thanks
Sent from my SGH-T959V using XDA App
This thread is no longer active. Jomeister plans to continue work on Evervolv. He will open a new thread for that purpose.
Introduction
The purpose of this thread is to coordinate work on the AOSP-based Evervolv 2.2 ROM for Skyrocket (and its sister, T989).
Skyrocket is not an officially supported ROM by Evervolv, but we have fully integrated device and vendor directories in their tree. Therefore we get fixes from the main tree and also have the ability to push fixes to Evervolv's tree. This is something we could never do when we worked directly off the Code Aurora source.
Our desire is to give the dev community a single codebase to coalesce around. Hopefully, with more devs working on the same project, we can progress faster towards AOSP.
To build, follow the instructions here (choose ev_skyrocket-eng at the lunch menu):
https://github.com/Evervolv/android
Or, the short, short version:
Run "repo status" and make sure you have no local mods.
Run "repo sync" and make sure it completes without error.
Run "rm -rf out" to remove any old compiled stuff
Run ". build/envsetup.sh" to set up your environment
Run "lunch ev_skyrocket-eng" to select the target
Run "make -j4 otapackage" (adjust -j option to match your # of processors)
What works:
2D/3D graphics, hw accel of gui, bluetooth, gps, nfc, wifi, sdcard (int+ext), MTP/PTP over USB
What doesn't work:
audio, calls, camera, cell data, sms, anything else you can think of
Issues are being managed on Github:
https://github.com/Evervolv/android_device_samsung_skyrocket/issues
Want a ROM link?
Then follow the instructions to build a ROM! The point, at this time, is to get devs involved in the process. The ROM is not ready for anyone to try out or use at this point. There are many problems left to solve.
Want to help?
Are you a dev with a Skyrocket and a burning desire to get AOSP for your phone? Please, check out Evervolv and start debugging! The Github Issues link above is a great starting point.
Jomeister and RaverX3X graciously agreed to join forces here. We hope other devs join too!
Current Dev Contributors:
jomeister15
RaverX3X
topprospect
Credit and Thanks:
Xboarder56 for the original Evervolv Skyrocket device tree
romracer for the unsecure mods to the ICS kernel
Changes Log:
04/11/12: Posted succint build instructions
04/11/12: Fixed unstable-ness of GUI (link)
04/06/12: Build now boots on its own boot.img (link)
this is on 4.0.4 now?
Sent from my GT-P7510 using XDA Premium HD app
BaconStep said:
this is on 4.0.4 now?
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
yes because google has released 4.0.4 sources and ota updates to nexus.
wali01x said:
yes because google has released 4.0.4 sources and ota updates to nexus.
Click to expand...
Click to collapse
Sweet!
Sent from my GT-P7510 using XDA Premium HD app
Looks great, will try building/debugging when I get my Ubuntu box up again!
Sent from my SAMSUNG-SGH-I727 using XDA
I'll be helping out as well, just got me a T989. I was working on cm9, but I'll switch to this. Hope I can help.
This is obviously a stupid question, and probably not the place to be asking it, but it is going to be asked anyway so.. I understand what the device tree is, but why is it not possible to pull one from the existing ICS leak?
giant420 said:
This is obviously a stupid question, and probably not the place to be asking it, but it is going to be asked anyway so.. I understand what the device tree is, but why is it not possible to pull one from the existing ICS leak?
Click to expand...
Click to collapse
No stupid questions here. A fully compiled ROM like the ICS leak obscures a lot of the details about how to build the ROM from scratch. You have to reverse engineer a lot of what Samsung did to compile AOSP, plus how to avoid pulling in too much Samsung bloat code. Hope that helps.
more or less were going to keep as much samsung out of it as we possibly can . Yes u can kang in stuff from the leak but then that actually causes more issues in the long run then doing it right the first time ;P.
bsbachert said:
I'll be helping out as well, just got me a T989. I was working on cm9, but I'll switch to this. Hope I can help.
Click to expand...
Click to collapse
I think we as a community should still continue working on things such as CM9 and AOKP in addition to Evervolv, just to give people as many options as possible. The good thing that Evervolv device trees are very similar to those required by CM9 and AOKP, so with a few hacks here and there I'm sure we can get those building as well. I don't know about the other devs, but I definitely have enough time to collaborate on multiple projects, as long as I'm not the sole carrier.
ur killing me. I finally managed to get media server to stay up for msm8660 audio pulled from the leak with jos isotope a4 with some other libs and bins. acdb pulling audio policy was still a problem though.
This is definitely for the better though. I was uncomfortable with all those Samsung libs bins and blobs, especially after staring at them under IDA. like raver said it woulda been a nightmare later on.
This is great though, everyone on the same pile should make this go a lot faster.
im very excited for this.
What's IDA?
Sent from my SGH-T989 using XDA
Wow. This build is going to b epic! Can't wait guys. Nice work so far
LawStud3nt said:
What's IDA?
Click to expand...
Click to collapse
http://en.m.wikipedia.org/wiki/Interactive_Disassembler
crazy what u can find in those blobs. helps a lot for debugging though
all I know is I love evervolv on my nexus one its super baller... Thanks to all 3 of you guys
Sent from my SAMSUNG-SGH-I727 using xda premium
Any updates? Got ants in my pants waiting for this one!
softballjunkee13 said:
Any updates? Got ants in my pants waiting for this one!
Click to expand...
Click to collapse
Thanks for the interest.
We will post updates as they happen. Right now we are just trying to organize and get everyone on the same page.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
topprospect said:
Thanks for the interest.
We will post updates as they happen. Right now we are just trying to organize and get everyone on the same page.
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Click to expand...
Click to collapse
OK...enjoy the holiday as well!