Please keep in mind this is a work in progress and is currently intended for devs only. Do not flash if you don't know what you're doing.
Ok, after making some progress towards getting this thing ready for user-space, I've decided to finally start a thread on it just to see if I can get anyone interested or willing to help... This ROM is currently in below Alpha status (if there is such a thing) and does not boot, but I believe I can get it booting in about a week barring a system crash or a zombie apocalypse. Again, this is only meant for a jumping off point towards getting AOSP ICS on our I957s, so don't blame me if you flash this and your tab becomes bricked...
Source
Link to source ------> Here
Github
Link to Github ------> Here
Want to Help?
Code:
Downloading and Building from Source
Edit
Follow the Repo instructions to download and install Repo.
Download the Android source tree by specifying the branch and manifest for a specific Code Aurora release. In this example the download the carrot.cupcake branch using manifest ''M7201JSDCBALYA6380.xml''
$ repo init -u git://codeaurora.org/platform/manifest.git -b ics -m M8260AAABQNLZA30120.xml --repo-url=git://codeaurora.org/tools/repo.git
$ repo sync
Build the source tree
$ source build/envsetup.sh
$ choosecombo 1 1 msm8660_surf eng
$ make -j4
Running choosecombo with no arguments will prompt for Android build options and target.
Downloads
Link to ROM------> Here
Thanks to Da_g for the kernel base, and thanks to the people at Code Aurora for the msm8660 source.
Great stuff jo
Sent from my SAMSUNG-SGH-I727 using xda premium
Sweet, Thank you for start a build for i957 and Finally about time!
great start, thank you!!!!
MaX
Great news, keep up the good work.
Yes thank you very much for this start!
ICS for i957?
I'm ready to test when you have a bootable ROM! Where are you getting ICS-compatible hardware drivers for the i957?
Thanks
phil_white99 said:
I'm ready to test when you have a bootable ROM! Where are you getting ICS-compatible hardware drivers for the i957?
Thanks
Click to expand...
Click to collapse
Base drivers can be used from the msm8660 ics source code provided by Code Aurora, and proprietary can be used from the stock Honeycomb firmware. Hopefully.
1. THANKS JO!
2. In order to boot, what is needed?
I'm assuming this is a CWM zip, not an odin package, right>
With ics for the skyrocket leak hopefully things will get easier
Sent from my SAMSUNG-SGH-I727 using xda premium
Thank You. Hell yeah! You guys rock. I'll help out if I can.
I'm willing to test too.
hey Jo there are some ICS CWM roms starting to come out for the skyrocket (ICSMOD5 is what I was looking at). Do you think with some script edits this could be flashed to the i957?
thanks to OP for attempting this. there are enough of us i957 users out there I think !
orlandoxpolice said:
hey Jo there are some ICS CWM roms starting to come out for the skyrocket (ICSMOD5 is what I was looking at). Do you think with some script edits this could be flashed to the i957?
Click to expand...
Click to collapse
Yes, but the problem is we would probably need our own ICS kernel to get most of the stuff working. I'll try my hand at ICSMOD5, but I'm not sure if anything will work without a dedicated kernel.
jomeister15 said:
Yes, but the problem is we would probably need our own ICS kernel to get most of the stuff working. I'll try my hand at ICSMOD5, but I'm not sure if anything will work without a dedicated kernel.
Click to expand...
Click to collapse
yes you are right about that, but i think the tmobile guys got ics running with the skyrocket kernel but they are having issues with data.
orlandoxpolice said:
yes you are right about that, but i think the tmobile guys got ics running with the skyrocket kernel but they are having issues with data.
Click to expand...
Click to collapse
Ok, I'm not really going to be able to use my tab for dev purposes this weekends, but if you want to try a port here's what you need to do.
1) Setup a build enviornment in dsixda's kitchen with ICSMOD5.
2) You'll need to look at the updater-script and change the partition blocks according to the Tab (e.g system needs to be 25 instead of 24).
3) Two ways to do 3. One: grab the kernel from this thread and put it in ICSMOD, or Two: You could just leave the kernel as is. I'm wary of option Two.
4) Flash it. If it doesn't boot, try to get a logcat and send it my way. If it does, then yay ICS.
jomeister15 said:
Ok, I'm not really going to be able to use my tab for dev purposes this weekends, but if you want to try a port here's what you need to do.
1) Setup a build enviornment in dsixda's kitchen with ICSMOD5.
2) You'll need to look at the updater-script and change the partition blocks according to the Tab (e.g system needs to be 25 instead of 24).
3) Two ways to do 3. One: grab the kernel from this thread and put it in ICSMOD, or Two: You could just leave the kernel as is. I'm wary of option Two.
4) Flash it. If it doesn't boot, try to get a logcat and send it my way. If it does, then yay ICS.
Click to expand...
Click to collapse
OK I have followed these instructions; downloaded ICSMOD5, set up the kitchen, grabbed the kernel (assuming that's boot.img) from your zipfile in the first post of this thread and copied it to the working folder, overwriting the Skyrocket kernel.
Then I looked at the updater script to see if partitions need changing. Per this post the layout looks OK. Example: /system is p24 and /boot is p08 already.
So far so good? Planning a test for later today.
Exciting let me know how it goes
Sent from my SAMSUNG-SGH-I727 using xda premium
Also don't use the default generated kitchen updater script
Sent from my SAMSUNG-SGH-I727 using xda premium
Related
For those of you that want to get in on early GB development but don't have the skill to compile it from source, I compiled the new source code that dropped for the gingerbread build for the Sprint Tab. This is NOT an installable rom. This is a zip containing the compiled AOSP kernel and system, purely for research/development purposes. Download, unzip and play. I doubt this will boot on a CDMA device without the proper bootloaders, but you're welcome to try. You can even develop AOSP roms from it that will probably run on your tab after the update on the 5th. Enjoy.
Download
Hope someone comes up with a great rom be it asop or other. Im truly looking for great things to come out of this.
Sent from my GT-P1000 using XDA Premium App
im expecting alot from these files!!!
a working 2.3 rom means the following for cdma tabs:
1.working skype video calls!
2.Working hulu!
3. Last but not least, Working Netflix!
it would make the tablet experience so much better for us CDMA owners.
i want to be the first to make a bug list on the first dev to release a rom
it would be a honor
and glad to see you finally posting something space. you have been in hiding so long, you rival osama lol
Argh, I wish I knew how to build roms >:|
kabuk1 said:
Argh, I wish I knew how to build roms >:|
Click to expand...
Click to collapse
im going to start reading this ebook i got.
its called:
learn android application development in 24 hours.
hopefully that would at least wet my feet.
man if I had broadband id have atempted to merge these into my cyanogen repo and make a build
Sent from my SCH-I800 using XDA App
wolfie083188 said:
im going to start reading this ebook i got.
its called:
learn android application development in 24 hours.
hopefully that would at least wet my feet.
Click to expand...
Click to collapse
For real? If so where can I get it.!?!?
EDIT : found it
Sent From My Evo using nanotechnology and incense!
has anyone tried just installing the kernel? anyone tried overwriting the last cdma cm7 build's system with this? anyone tried both? I'm going to see if I can get my hands on some internet soon but I might have me a date
Sent from my SCH-I800 using XDA App
Obama's>god said:
has anyone tried just installing the kernel? anyone tried overwriting the last cdma cm7 build's system with this? anyone tried both? I'm going to see if I can get my hands on some internet soon but I might have me a date
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
I guess I should add: you'll need the driver libs to get this running... you'll have to gank what you can from the gsm GB build. Stuff in /system/lib/hw and /system/lib/egl and so on. Just compare and you will get the idea.
spacemoose1 said:
For those of you that want to get in on early GB development but don't have the skill to compile it from source, I compiled the new source code that dropped for the gingerbread build for the Sprint Tab. This is NOT an installable rom. This is a zip containing the compiled AOSP kernel and system, purely for research/development purposes. Download, unzip and play. I doubt this will boot on a CDMA device without the proper bootloaders, but you're welcome to try. You can even develop AOSP roms from it that will probably run on your tab after the update on the 5th. Enjoy.
Download
Click to expand...
Click to collapse
Thanks! This is useful. I am merging the CDMA kernel sources with GSM right now and the PowerVR module is updated so it looks like I will have to switch to newer OpenGL driver from this archive.
Technomancer said:
Thanks! This is useful. I am merging the CDMA kernel sources with GSM right now and the PowerVR module is updated so it looks like I will have to switch to newer OpenGL driver from this archive.
Click to expand...
Click to collapse
I hope it's useful. Sadly, the proprietary files weren't included in the source, so of course you'll have to patchwork from other builds or wait until the official release for some of those.
You're welcome though, glad to be of service.
spacemoose1 said:
I hope it's useful. Sadly, the proprietary files weren't included in the source, so of course you'll have to patchwork from other builds or wait until the official release for some of those.
You're welcome though, glad to be of service.
Click to expand...
Click to collapse
Yeah, I just noticed that, no EGL, etc. Maybe they put this stuff in /vendor now?
I just redid my Tab. I'm ready for Gingerbread on this *****.
It seems OTA may be pushed to some users now. Anyone care to rip all the files in /system and post them?
-d
technomancer
as soon as I get my update i'll help you out, just let me know how to rip my system, hell if i could dump my whole g-tab into an installable rom i would... still waiting on the push update, 7:02 PM EST, still no update! might be tomorrow!
x4gvnferdy said:
as soon as I get my update i'll help you out, just let me know how to rip my system, hell if i could dump my whole g-tab into an installable rom i would... still waiting on the push update, 7:02 PM EST, still no update! might be tomorrow!
Click to expand...
Click to collapse
Open adb shell and run this:
tar -czvf /mnt/sdcard/system_dump.tar.gz /system/
it will create file system_dump.tar.gz in on your sdcard with the contents of your factoryfs (system) partition.
alright! So when my update comes i will do just that and put it on my dropbox, providing you a download link!
Technomancer said:
Open adb shell and run this:
tar -czvf /mnt/sdcard/system_dump.tar.gz /system/
it will create file system_dump.tar.gz in on your sdcard with the contents of your factoryfs (system) partition.
Click to expand...
Click to collapse
Would the .zip update file help? I've got that posted on mediafire (as i just a little bit ago got the notice for an update. If it'll help, here's the link.
http://www.mediafire.com/?cngx5e67dgbq04y
Otherwise i'll get the update installed and see about running the sys dump as well.
pvtjoker42 said:
Would the .zip update file help? I've got that posted on mediafire (as i just a little bit ago got the notice for an update. If it'll help, here's the link.
http://www.mediafire.com/?cngx5e67dgbq04y
Otherwise i'll get the update installed and see about running the sys dump as well.
Click to expand...
Click to collapse
has anyone tested this? i don't wanna brick my tab!
I've got it up and running on my tab and there's at least 1 other person from this thread http://forum.xda-developers.com/showthread.php?t=1148447 that has it up and running as well.. Odin'd back to stock EA24, did the OTA EB28, and then ran the update.zip from stock recovery. All is happy on my tab. Now I just have to wait till i'm at work tomorrow to get ADB to work, and I'll dump /system.
Android Development How-To: Compiling the Android/Linux kernel for the Epic Touch 4G.
NOW INCLUDES ROOT!!!
Introduction: This guide is meant for people who want to get started with android development and don't know where to start. This thread can also be used as a reference place for android development on the et4g. This guide well first be on compiling the android kernel and flashing it to your phone and, I well update it on a regular basis for more complex mods and such to get you familiar with the android platform. If at anytime anyone would like to add more to this, pm me with what you would like to add or fix. Android is an open-source wonderland and I feel like more people should experience the fun of android development. Just remember I am not responsible if you do something stupid and break your phone!
First, we are going to get familiar with the android kernel by compiling a stock build and flashing it with Odin to your et4g.
What you need to download to compile the kernel:
Samsung open-source kernel and platform files. Available at: Samsung Open Source
Type in: Sph-d710 in the search bar in the link and download latest source.
initramfs files (More on this later) (includes cwm, busy box, and of course root! Thanks to chris41g for his help.) Files available at: Initramfs Files
Tool chain for compiling: Available at: Arm-toolchain
Preferably Ubuntu or another Distro. Of Linux running on a partition or Virtual machine.
Step 1: Were going to unzip the source you got from Samsung and take a short look around.
unzip the source and unzip the file that says, “SPH-D710_GB_Kernel.tar.gz” and, open it up. You are now looking at the kernel source for the Epic touch 4g! Okay I well not go over to much whats is here but, I well add a more in depth look in the kernel soon.
Scroll to the bottom of the source and you should see a document that says, "makefile". We are just going to add a name for your stock compile of the kernel, to make it a little more special. Open it and go to where it says Extra version and add your last name ,just make it all lower case letters or it wont compile correctly. When you flash it to your phone, the about phone panel in setting well say: Kernel version: 2.6 [last name you chose] now.
Step 2: Lets get started!
Open terminal in Linux and change your directory to the kernel. You do this by putting,
“cd” and then typing where your kernel source is then hit enter. My terminal looked like this:
cd /home/shane/Desktop/SPH-D710_GB_Kernel
Click to expand...
Click to collapse
Step 3: Tell terminal where your tool chains you downloaded are located.
The kernel is compiled using a tool chain, and the terminal needs to know where the tool chain is to compile. (The tool chain is the folder called “arm-2009q3” )Start by typing this in the terminal:
export CROSS_COMPILE=
Click to expand...
Click to collapse
Then after that put where your tool chain is located. Also when you are entering where it is at, you need to put a “/bin/arm-none-eabi-” at the end of the directory. This shows the terminal that the compiling tools are under the folder bin and starts with arm-none-eabi- and the android compilation adds the last word for the compiler program it needs. (you can see this if you go into the bin folder under the “arm-2009q3 folder.) For adding the tool chain I entered this:
export CROSS_COMPILE=/home/shane/Desktop/arm-2009q3/bin/arm-none-eabi-
Click to expand...
Click to collapse
Then hit enter.
Step 4: Clean the kernel, enter configuration files and make the modules.
Enter this command:
sudo make clean
Click to expand...
Click to collapse
Then enter password and hit enter.
Then it well say something like:
make: /opt/toolchains/arm-2009q3/bin/arm-none-linux-gnueabi-gcc: Command not found
Click to expand...
Click to collapse
IGNORE THIS! It is just a fragment in a configuration file that says the toolchain is not in the default location. But, we changed the tool chain location in step 3 so it well compile correctly.
This cleans up and organizes the kernel for compilation.
Now enter this command in terminal:
make c1_rev05_na_spr_defconfig
Click to expand...
Click to collapse
This is the configuration files for the epic touch 4g and well compile the kernel based off what is in these files.
Now were going to compile all the modules so wifi,vibration... work.
Enter this in terminal:
make modules
Click to expand...
Click to collapse
Step 5: Moving the newly compiled modules to the initramfs/lib/modules folder.
We are now going to move the modules from the newly compiled modules to the initramfs files. So that wifi and vibration well be working in our kernel.
*Initramfs files are the root filesystem of the kernel and does processes the kernel can't do itself while its booting.
You can do this by terminal or by hand. We are just moving the modules to the initramfs to be used when compiling the kernel.
You can type this into terminal (Where it says “Path to initramfs” you need to replace with your own path to the initramfs folder + /lib/modules) :
cp drivers/samsung/j4fs/j4fs.ko Path to initramfs/lib/modules
cp drivers/scsi/scsi_wait_scan.ko Path to initramfs/lib/modules
cp drivers/bluetooth/bthid/bthid.ko Path to initramfs/lib/modules
cp drivers/net/wireless/bcm4330/dhd.ko Path to initramfs/lib/modules
cp drivers/samsung/vibetonz/vibrator.ko Path to initramfs/lib/modules
cp drivers/staging/westbridge/astoria/switch/cyasswitch.ko Path to initramfs/lib/modules
Click to expand...
Click to collapse
This copies the new modules out of the kernel source and puts them in the initramfs/lib/modules folder to be used later.
Now once you enter that press enter.
Step 7: Compiling the android kernel with initramfs.
Type this in terminal:
make -j5 CONFIG_INITRAMFS_SOURCE=Path to initramfs file
Click to expand...
Click to collapse
*Remember to replace the “path to initramfs file” with the path to the initramfs file.
Okay this well take anywhere from 5-15 mins. to compile depending on your system.
Step 8: Were done compiling, lets make something flashable for Odin!
Just type in terminal:
cd arch/arm/boot/
Click to expand...
Click to collapse
Then type:
tar cvf MyKernel.tar zImage
Click to expand...
Click to collapse
This well zip up the zimage (the kernel) you just compiled to something flashable in odin.
If you open up the kernel source file and go to arch/arm/boot you well see the zimage you compiled and, the Mykernel.tar file for Odin. Double check and right click on the zimage and make sure it is around 5-6 MB before flashing.
Step 9: Flashing to your phone.
Go to a windows computer and download Odin.(if you have rooted your phone using zedomax's method you should have it installed already)
Okay now open it up and place the Mykernel.tar file in the PDA section of Odin. Now download the drivers for your phone if you haven't.(I assume you already have.) Then put your phone in download mode (hold volume down button and power button on start up and push volume up button when the warning pops up) Now plug your phone into the computer and make sure “auto-reboot” is the only box checked in Odin. Hit start and your phone well be flashed with a kernel you compiled yourself! If you did this right your phone should start up. If it is stuck in a boot loop, immediately put back in download mode and flash to stock. Link available here to stock files:
http://forum.xda-developers.com/showthread.php?t=1409634
and, try to figure out what you did wrong while compiling and try again!
Good job you have finished!
Step 10: The future and your new phone!
I would like to include more android kernel mods and stuff in the future but, wanted to get this out there to get people familiar with the android compiling process. I want this guide to be something people reference as they start to develop, by using the methods here along with kernel and U.I mods on the platform being implemented in the future. My ultimate goal is to at least know I helped at least one person get into android development so, if I helped you please leave a reply or say thanks. If anyone has ideas to add to the post, please pm me.
Have fun developing!
I'll take this...
and this...
One more...
Awesome!!!! I have been patiently awaiting this. THANK YOU SOOO MUCH!!!!
Sent from my SPH-D710 using xda premium
Thank you! Definitely will be referring to this during my free time. Can't wait to see what else gets added
Sent from my SPH-D710 using xda premium
Awesome!! tyvm!!
Wow... How awesome is this? I have been looking for something like this for a long time. I will be watching for updates. Thank you very much.
all u need now is a video tutorial
My man!!! Thank you for this!!
Sent from this phone
Awesome guide, I am looking forward to giving this a go soon. Just curious but how difficult is the process to include a custom recovery?
dtm_stretch said:
Awesome guide, I am looking forward to giving this a go soon. Just curious but how difficult is the process to include a custom recovery?
Click to expand...
Click to collapse
It all depends if you wanted to flash a already made custom recovery (cwm) then we would just haved to root the kernel then build and flash the recovery. If you were to make a fully custom recovery with custom functions made by you then it could get a little more tricky but, I am guessing you just mean flashing a custom recovery like cwm. Which is not terribly hard but, not neccesary easy eather depending on how hard it is to obtain root.
I might update the guide in the future. Showing how to do something like this but, I have a few more ideas for the guide before I include this.
You nailed it, I was curious about adding root and CWM(or a variation of it). I am more than content with figuring out what you have posted so far.
Thank you so much. This is absolutely great!
Sent from my SPH-D710 using XDA App
Awesome guide. Thank u so much for this. Hope for many more.
Sent from my Nexus S 4G using xda premium
Very awesome thanks for the share!!
Sent from my SPH-D710 using XDA App
Great Guide!
Very informative and well put, Thank You.
thank you very much for this! Gives me something new to try out. Thanks again!!!
Sent from my SPH-D710 using Tapatalk
Thanks for this effort. Unfortunately I don't have anything to contribute to your work. I consider myself a budding developer and have been diligently teaching myself to program with the use of some great texts over the last 2 weeks. While I have much to learn this guide and hopefully any additions you make will help me dive nose first into Android development like I've been hoping to for the last couple of years.
I hope you continue to add more into this guide and it becomes a great resource for others like me.
Great Job!
obelisk79 said:
Thanks for this effort. Unfortunately I don't have anything to contribute to your work. I consider myself a budding developer and have been diligently teaching myself to program with the use of some great texts over the last 2 weeks. While I have much to learn this guide and hopefully any additions you make will help me dive nose first into Android development like I've been hoping to for the last couple of years.
I hope you continue to add more into this guide and it becomes a great resource for others like me.
Great Job!
Click to expand...
Click to collapse
I hope it helps!
This thread will be a little different.
I would like to make one thing very clear. Even tho I'm posting new repacked kernel with a recovery compiled from source I can't claim this as my work.
A lot of talented devs were involved in the process and they were kind enough to guide me every step of the way and not claiming any credit for that. I would like to extend my thanks to (not in any particular order):
Chris41g
Sfhub
garwynn
Mr. Sumrall
Entropy
And many more who helped along the way.
First let us understand what is "safe" recovery.
Here is direct quote from sfhub's PM to me:
"Just think of it this way. You build your own recovery executable and have examined your source tree confirming wipe.c doesn't exist, so the operations that are handled *by your recovery* are safe. That is wipe data/factory reset and nandroid backup/restore.
When you choose to install a rom from *your recovery*, it uses a "helper app" that is in the ROMs update.zip called update-binary.
This update-binary is also compiled against libext4_utils.a, except in this case (except for your own ROM), you cannot examine the source tree update-binary was compiled against, so you can't be sure wipe.c wasn't used.
Now if that ROM update.zip were to use a "known" update-binary, like the one included with the EL29 OTA, then you would know that it was "safe" update-binary, even without the source code."
End quote.
You can read more about this In this thread if you haven't done it yet.
In other words. The bug was present in GB as well but it was missing the command to trigger it. That command has been introduced (added) in ICS code.
So:
1. As long as recovery is build against GB code it is safe.
2. If any update zip is build based on GB source code it is safe.
3. If any rom has GB updater-binary in META-INF it is safe.
4. If rom is build with ICS update-binary but doesn't have format() for data in updater-script it is safe.
As we can see here the problem is with format() command in ICS source.
There is a line (command) in ICS that wasn't present in GB and it triggers the bug. It's hiding in format() and has a wipe() syntax or something like that.
GB source code doesn't have it thus we never had any bricks in GB.
When any filename_rom_theme_whatever.zip is applied in recovery it will use updater-binary that is packed into zip and located in META-INF folder.
All GB binaries are safe since they didn't have that wipe() command in them.
We have safely used Calk's format_all.zip because it has been created in GB days and has GB updater-binary in it.
If rom devs will use GB update-binary the rom zip will be safe to flash.
Any update.zip with GB binaries is safe.
Now about the update and repack I'm about to post.
Recovery has been compiled from source provided by Chris41g and with his help against CM7 (GB) source code and all menu items in recovery are safe to use.
It has been repacked into ICS zImage but since binaries are from GB there is nothing to worry about.
tFE22_v0.1.1 has GB binary in it (as all my roms did) and it's safe to flash.
FE22_Repack_AGAT.zip has GB binaries and it's safe to use.
Whenever you wanna flash a zip file in recovery you would worry only if zip has ICS binaries packed into it. I that case even simplest zip flashing can cause a brick. It doesn't mean it would but the possibility is there.
I'm using this newly repacked kernel for couple of days now and I did apply wipe data/factory reset menu option 8 times. No problems so far.
I hope you would have same experience.
Now to my update.
tFE22_v0.1.1:
1. Fixed SystemUI.apk
2. 4G icons have been replaced with ones I had in my previous roms.
3. Added S-Voice (thanks to scarmon25 for help)
4. Small revisions all over the place.
5. Bluetooth works and reconnects as soon as device is in range
FE22_Repack_AGAT:
1. Recovery compiled from source (I can't thank enough Chris41g for his help and guidance)
2. Wipe data/factory reset is back into recovery menu (use it with caution).
3. Small changes and edits in init.rc
4. Changes and edits in recovery.rc.
5. Renamed recovery to AGAT_Recovery version tREC_0.0.1. Thanks to Chris41g for being so kind and generous because it is his recovery, source and help that make all this possible.
6. Added my logo and name to recovery background.
Here are links:
tFE22_v0.1.1
1. tFE22_v0.1.1.zip
Mirror at dev-host.
2. Deodexed version coming soon.
Repacked Kernel:
1. FE22_Repack_AGAT.tar Flash with ODIN
2. FE22_Repack_AGAT.zip Flash in recovery.
If anyone wants to use this repack for a rom feel free to do so.
One more time it's not my work but rather a combined effort of many talented devs that helped me wile staying in background and didn't want/ask for any credit for this.
But they deserve more credit than I do. They could of do it without me in a heart bit. I couldn't do it without them in a year.
reserved
I'm on this bad boy!! Thanks bro!
Sounds likes you guys have got everything under control niiiiice and thanks for being brave enough to do this....
Sent from my Xoom using Tapatalk
U r the man downloading now
Sent from my SPH-D710 using XDA Premium App
Niceee
Sent from my SPH-D710 using Tapatalk
Nice work, I'm surely gonna try .Keep up.
agat63 said:
reserved
Click to expand...
Click to collapse
Awesome. Great work agat., question, I know this is your recovery, what is it based on, ACS5, rogue, CM? And just to clarify, you can wipe using this in ics? Providing that the update script in the zip isn't ics? Did i get that right? Lol. Is there any way to tell if the update meta file script uses ICS or GB? Also does this kernel come with s some of the standard goodies, initd, bootanimation support etc? Also, 1st page again!. Shout out to rwilco for putting all these kernels I'm one place.. Its in the stickies you can't miss it. Get the NEW kick ace boot animations WITH SOUND RIGHT HERE!! Again thanks for having the extremely huge round spherical objects about a foot below the waste to do this. You are the man thank you and you are appreciated.(don't want to offend anyone this time lol)
Sweet man does the rom include the new kernel was gonna be asked may as well get it out of the way
Sent from my SPH-D710 using xda premium
timmetal6669 said:
Awesome. Great work agat., question, I know this is your recovery, what is it based on, ACS5, rogue, CM? And just to clarify, you can wipe using this in ics? Providing that the update script in the zip isn't ics? Did i get that right? Lol. Is there any way to tell if the update meta file script uses ICS or GB? Also does this kernel come with s some of the standard goodies, initd, bootanimation support etc? Also, 1st page again!. Shout out to rwilco for putting all these kernels I'm one place.. Its in the stickies you can't miss it. Get the NEW kick ace boot animations WITH SOUND RIGHT HERE!! Again thanks for having the extremely huge round spherical objects about a foot below the waste to do this. You are the man thank you and you are appreciated.(don't want to offend anyone this time lol)
Click to expand...
Click to collapse
Edit: just flashed and checked out the recovery, effing awesome!!!Excellent!!!
Looks like you pulled an all-nighter...no slacker, you.
Problem: Firefox and Opera do not play well with JumboFiles for the ROM. OpenDNS blocks it and other red flags pop-up. Any mirror or other source planned? If I'm alone, c'est la vie.
Thanks and great work, agat. Without question you're putting the greatest effort into development now and it's terrific to be a beneficiary of your going up the learning curve.
EDIT: Found a work-around to download ROM, but JumboFiles.com has a bad rep. Downloading Agat's repacked was never a problem.
FYI, Did you notice when flashing the new FE22 repack, screen indicates it is "Flashing FE16 Repacked Kernel?" I assume that's a typo.
Agat, I'm currently on rooted stock FE22 ROM with your repacked FE22 kernel, including modified ACS recovery.
Can I flash your new ROM from FE22/ACS recovery or should I mobile odin back to EL26/CWM and flash from there?
I've never tried any of your ROMs but I'm surely gonna try this one haha
ejlmd said:
Agat, I'm currently on rooted stock FE22 ROM with your repacked FE22 kernel, including modified ACS recovery.
Can I flash your new ROM from FE22/ACS recovery or should I mobile odin back to EL26/CWM and flash from there?
Click to expand...
Click to collapse
FWIW, I just flashed through the "old" FE22 repack (same set-up as you) recovery without a problem.
Agat! Very nice progress made by you and all that helped in the community along the way.
Great Job!
Sent from my " Victoria Secrets is having a 50% off bra sale Too bad.. I like bras 100% off" using xda premium
Why is it an hour+ to download the ROM o.o
Can you flash back and forth from gb to ics with this?
AshyKnuttz said:
Why is it an hour+ to download the ROM o.o
Click to expand...
Click to collapse
It's always around 25 mins for me on agats server downloads. Just how it is. Never 1 hour though... Lol
Sent from my " Victoria Secrets is having a 50% off bra sale Too bad.. I like bras 100% off" using xda premium
timmetal6669 said:
Can you flash back and forth from gb to ics with this?
Click to expand...
Click to collapse
The way I read it, that depends on the update script that's in the ROM your flashing. So if you are using this kernel plus a ROM that has an update script based on the GB script then yes. Agat, please correct me if I'm wrong...
Sent from my SPH-D710 using xda premium
CyberpodS2 said:
The way I read it, that depends on the update script that's in the ROM your flashing. So if you are using this kernel plus a ROM that has an update script based on the GB script then yes. Agat, please correct me if I'm wrong...
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
That is exactly correct! So all devs technically should be building roms with updater scripts from GB base now, if they weren't already.
Sent from my " Victoria Secrets is having a 50% off bra sale Too bad.. I like bras 100% off" using xda premium
InformationThis kernel is forked from the CyanogenMod Kernel and i have added a few additional changes of my own and more to come. My builds of AOKP and Gummy have this kernel pre-installed with the Kanged Gummy Kernel but when i release 1.0 it will have a few more tweaks so you would need to upgrade.
There will be 4 files you can download. The boot.img and zImage can both be flashed using Heimdall. The Flashable zip and Odin tar.
Bugs
Deep Sleep works but when using LiveOC it does not so i recommend only using this when playing games or maybe make a script to disable this when you device locks in the time being.
Differences
LiveOC
More Frequencies (100MHz, 200MHz, 400MHz, 600MHz, 700MHz, 800MHz, 900MHz, 1000MHz, 1100MHz, 1200MHz, 1300MHz, 1400MHz)
Lulzactive v2 Governor (My preferred choice)
Tiny shmem
Working on more!
Using Features In The KernelLiveOCHere is information on it This is configurable using a tool known as NSTools on the PlayStore. When using this 100% means the bus frequency is at 100% try not to get confused. So 100% of 100MHz would be 100MHz so if you increase it to 120% so it would be 120% of 100MHz would be 120MHz and this value applies to all CPU frequencies, GPU ect.
LulactiveThis is like other governors for the CPU and can be configured using applications like Voltage Control, SetCPU, NSToolsand built-in tools from CM9/10 and AOKP ect.
Downloads
All Devices - http://goo.im/devs/henryedwardrose/Kernel/ICS
P1 - zImage - Boot.img - Flashable.zip - Odin.tar
P1L - zImage - Boot.img - Flashable.zip - Odin.tar
P1N - zImage - Boot.img - Flashable.zip - Odin.tar
Installation
zImage or boot.img
Use command line tool known as 'heimdall' (for people comfortable with the command-line)
Flashable.zip
Installed using CWM (the easiest methord)
Odin.tar
Put this file in the PDA section on Odin (Windows only)
Special ThanksThe TE4M - Nice work on developing the kernel and getting our device officially supported by CyanogenMod!
Dizgustipated - Nice Guy, Excellent Roms and Kernel!
Technomancer - The Guy who originally ported CM7 to our tab
SourcesMy Github
BuildingYou can build this kernel yourself in two ways
The First MethordIs by adding it into your manifest in your android build environment which supports integrated kernel building like CM9/10 and AOKP.
If you want it in your own Rom then simply just perform the regular build commands
If you just want to build a boot.img then apply the following commands
source build/envsetup.sh
lunch cm_p1-userdebug (change this depending on what device you would like to build)
make out/target/product/p1/boot.img
Click to expand...
Click to collapse
The Second MethordBefore the integrated kernel building system you used to build a kernel outside of this in it own separate environment so i have made it possible without have to download the android build environment to build any kernel for this device and you just have to run a build script and tell it what device you want to make.
Firstly you want to use the following commands
mkdir Kernel
cd Kernel
repo init -u https://github.com/henryedwardrose/Kernel_Manifest.git -b master
repo sync
Click to expand...
Click to collapse
Ok when synced you will see that there are three directories. Two of which are what you need. The 'Files' directory
is where all of the other files go that are necessary to build the kernel. The build.sh is a nice bash script which
you can open and easily understand what commands are being executed and how the files are being used.
Anyways here's how you build:
Firstly in the terminal go to the Files directory
cd Files
Click to expand...
Click to collapse
Now run this following command to extract the ramdisks (you only have to do this when i have uploaded a new ramdisk)
./RUNAFTERSYNC.sh
Click to expand...
Click to collapse
Then you want to build the kernel and at the end you will end up with the following flashable files 'zImage,
boot.img, .tar, .zip'
Now you need to initiate the building process
./build.sh
Click to expand...
Click to collapse
Now follow the commands on screen and you will end up with the kernel located in the out directory and you can flash
via Heimdall (zImage and Boot.img), Odin (.tar) and CWM (.zip)
Enjoy!
Thanks for you work...
Please build for all model (P1,P1l,P1N, P1C)..
a-vista said:
Thanks for you work...
Please build for all model (P1,P1l,P1N, P1C)..
Click to expand...
Click to collapse
oops! forgot this information lol :silly: Of course, well except for P1C atm
thanks for kernel. love your work bro.
i flashed on my p1. im trying and write back here for bugs etc.
can someone post some screen shots..???? PLEASEEE...
[email protected] said:
can someone post some screen shots..???? PLEASEEE...
Click to expand...
Click to collapse
ScreenShots from what???
This is a kernel, nothing changes visually...
Just performace, battery..etc..
hi
thanks again your work.
i tried kernel but it doesnt going into DEEP SLEEPtab working always 1200.
my options is smartassv2 and sio.
Used this kernel can be used camera 360 ?
It feels smooth indeed. Quadrant score at 1300 MHz with Cm9 is around 2600-2700.
Kernels includes CWM right? I wonder if I can have this on my P1000N stock GB 2.3.3.
Sent from my HTC Desire S
Hi henry.
My tab is p1000 and im on your aokp milestone 6 (not the rebuild 1). I decided to update my kanged gummy kernel to 1.0 as suggested in the op. I tried the zip for p1 using cwm recovery, and my tab was stucked to the samsung logo. Cant go to recovery too. So i decided to use the .tar in odin, and its now perfectly.
Just a heads up that there maybe something wrong with the zip version. But neverrtheless, thanks for this wonderful kernel!
I have a p1 too and i have download cwm file i have instal it with no issue.
Maybe a wrong download ?
@Henry,
with rebuild 1 kernel is the latest kernel or i have to redownload and install ?
Thank's
Hope someone can upload it to other sites. Rapishare really sucks.
Sent from my GT-N7000 using xda premium
MarlX said:
Kernels includes CWM right? I wonder if I can have this on my P1000N stock GB 2.3.3.
Sent from my HTC Desire S
Click to expand...
Click to collapse
Yes it does, yer you can and will install but it will NOT boot unless you have ICS on your device.
vince_junior said:
Hi henry.
My tab is p1000 and im on your aokp milestone 6 (not the rebuild 1). I decided to update my kanged gummy kernel to 1.0 as suggested in the op. I tried the zip for p1 using cwm recovery, and my tab was stucked to the samsung logo. Cant go to recovery too. So i decided to use the .tar in odin, and its now perfectly.
Just a heads up that there maybe something wrong with the zip version. But neverrtheless, thanks for this wonderful kernel!
Click to expand...
Click to collapse
Thank you for your report its always appreciated It has worked for me and i have a p1 but i will test it soon again to see if i have any issues
chickygamon said:
I have a p1 too and i have download cwm file i have instal it with no issue.
Maybe a wrong download ?
@Henry,
with rebuild 1 kernel is the latest kernel or i have to redownload and install ?
Thank's
Click to expand...
Click to collapse
There is no need to install it but if you install this one it won't hurt its the same.
Gpsrisk said:
Hope someone can upload it to other sites. Rapishare really sucks.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I will upload it to goo.im soon but working on jb atm
henryedwardrose said:
I will upload it to goo.im soon but working on jb atm
Click to expand...
Click to collapse
Wow!
New Link
Hey, Uploaded All files to Here now;
http://goo.im/devs/henryedwardrose
Click to expand...
Click to collapse
enjoy!
henryedwardrose said:
Hey, Uploaded All files to Here now;
enjoy!
Click to expand...
Click to collapse
Something wrong with goo.I'm server. ?
Sent from my GT-P1000 using Xparent ICS Tapatalk 2
well this sucks all links are broken
tohno said:
well this sucks all links are broken
Click to expand...
Click to collapse
Goo.im are down atm i am going to upload them again when they are back up. In the mean time i am working on a few things and i may rebuild the kernel with gcc 4.6 check the op are the links still working on rapidahare?
Sent from my GT-P1000 using xda app-developers app
Hey,
I think you guys know me from my Xperia SSpeed rom and kernel, but from now on I'll be starting with a new project
I'm going to try to compile an AOSP rom for Xperia S. I'd like to create this thread as a discussion thread about features, bugs, etc.
I'll also try to create a sort of "FAQ post" here
Everything you want to discuss about an AOSP is welcome here
Regards,
Krabappel2548
== To Do ==- Clone the right Google Source code and compile again.
== Progress ==
== Compile again using the right google source code [19/12] ==
- Going to start again, I compiled from the wrong Google source code
== Made a flashable zip [19/12] ==
- Made the rom as flashable zip
- kernel is included
- Symlinks and permissions should be ok now
== Fixed boot.img not flashing problem [18/12] ==
- Boot flashed, this is the kernel: download the kernel
- Rom still not booting
==First compiled version as system.img [18/12] ==
- Boot, not fashable
- Rom not booting with FXP kernel
- System.img is not editable with a linux disk reader
Hello, I had KA ROM since 01 in GB to 19 in ICS.
I'll try your new ROM when you'll release it.
Good luck for this project
Great. AOSP on XS will be cool. :good:
You will work with The Three Musketers team (that one on Facebook)?
The long awaited AOSP rom??? WOW thanx Krabappel!!
Felimenta97 said:
You will work with The Three Musketers team (that one on Facebook)?
Click to expand...
Click to collapse
yes, but no one succeeded in getting it to boot, so now I'm compiling my first version, just to see if it boots first
Cool ! Will test it once u release it and report back
Sent from my Xperia S using xda premium
krabappel2548 said:
yes, but no one succeeded in getting it to boot, so now I'm compiling my first version, just to see if it boots first
Click to expand...
Click to collapse
Ok. Hope to see you all working together, so you can find it faster, and avoid multiple AOSP ROMS.
Sent from my LT26i using Tapatalk
I made the second post one to post my progress in. I think I have fixed the flashing issue with boot.img, but I'm going to add a kernel logo to really see if it the compiled kernel works
The rom doesn't boot when compiled a system.img, so I'm going to try to compile it as an flashable zip to test again today
Would you mind posting link to boot.img to see if we can get it to work with the img files I've compiled Because rather than use the device files from sonydev github, I've used the ones from Google just to see if that would make a difference, but our testers couldn't flash the boot.img
[vertigo] said:
Would you mind posting link to boot.img to see if we can get it to work with the img files I've compiled Because rather than use the device files from sonydev github, I've used the ones from Google just to see if that would make a difference, but our testers couldn't flash the boot.img
Click to expand...
Click to collapse
ok didn't knew you were working on this?
I'm alone for this project now
I'll add the link to the second post
Yeah I've been having a go, but not having the device makes it really hard lol ... Also tried the fruits and veggies rom from Galaxy Nexus forum but I'm having the same problems with that as its also based on AOSP.
Edit: thanks for the kernel
Come on Krab
Sent from my Xperia S using xda premium
Ill even unlock my bootloader if this is a winner.
did you find a way to edit system.img?
Xperia S Tapatalk
system.img is simg, just do simg2img system.img system.ext4 then you can mount it.
Apology11 said:
did you find a way to edit system.img?
Xperia S Tapatalk
Click to expand...
Click to collapse
letama said:
system.img is simg, just do simg2img system.img system.ext4 then you can mount it.
Click to expand...
Click to collapse
Got that in the meantime
I made a flashable zip with the right permissions and symlinks now
Only thing left to do for now:
- Test it out and see if it boots!
Hi Krabappel2548,
Out of curiosity, are you following the instruction on their README to build a bootable image?
I agree that all the efforts from XDA devs should be concentrated on a single project.
I am no developer but it would be amazing if devs from XDA would collaborate with Sony devs to make this project develop into a working ROM.
Their code is all hosted on a public github where code can be contributed, forked and merged!
Good luck, keep up the good work and work together with Sony and other XDA devs! :victory: :fingers-crossed:
EDIT: Also, should this thread be in the development section maybe?
rent0n said:
Hi Krabappel2548,
Out of curiosity, are you following the instruction on their README to build a bootable image?
I agree that all the efforts from XDA devs should be concentrated on a single project.
I am no developer but it would be amazing if devs from XDA would collaborate with Sony devs to make this project develop into a working ROM.
Their code is all hosted on a public github where code can be contributed, forked and merged!
Good luck, keep up the good work and work together with Sony and other XDA devs! :victory: :fingers-crossed:
EDIT: Also, should this thread be in the development section maybe?
Click to expand...
Click to collapse
Yes I followed the instructions from Sony, but there is more then those instructions that needs to be done You need to setup ubuntu first
I know about the Sony github, I can't compile the AOSP rom without those files
The thread belongs here for now, as soon as the rom boots, I'll make a new thread in development section
Sent from my LT26i using xda app-developers app