Develop Bugs

30/Jun r1 (JFB) - MoDaCo Custom ROM for Samsung Galaxy S with Online Kitchen

I'm pleased to present my MoDaCo Custom ROM for the Samsung Galaxy S! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know. wink.gif
This ROM is the 'starting point' for my Galaxy S custom ROMs.
About MoDaCo Custom ROMs
MoDaCo Custom ROMs are based on official ROMs - either shipping or leaked. A MCR release is designed to feel as far as possible like a stock ROM, with optimisations, tweaks and complimentary additions that enhance the user experience. The aim of a MCR is to be ultra reliable for use on an everyday device.
Requirements
In order to use this ROM on your device, YOU MUST ALREADY BE RUNNING THE JFB ROM FROM HERE. Do NOT use this ROM with any other base, unpredictable things will happen, the most likely being you'll have to reflash your device via Odin.
Features Included
* Based on the JFB release
* Rooted with Superuser 2.1 by ChainsDD
* Built with the MCR build process which reduces the size and boosts the speed of the ROM
* busybox with Droid Explorer support
* Updated Google Maps
* MCR version displayed in 'About' screen
* Optional Google Voice Search
* Optional Google Voice Dialer
* Optional Fancy Widget
* Optional Beebplayer
* Optional baked in Wavesecure via the online kitchen (installed to system partition for maximum security)
Changelog
Please see 2 posts below this one for the changes in each release.
Installation
To install this ROM:
* Ensure you have the JFB ROM installed (linked above)
* Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card named 'update.zip'
* Restart your device in recovery mode by running 'adb reboot recovery' (download adb if you do not have it already, use adb-windows, adb-mac or adb-linux as appropriate)
* Select the option to apply an update zip, and select the zip file you copied to your memory card
Upgrading
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Downloads
This ROM is currently only available in the online kitchen - prebakes to follow.
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
And finally...
If you would like to show your appreciation for the ROM, please consider supporting MoDaCo by signing up for a MoDaCo Ad Free or MoDaCo Plus account, both of which also give you early access to Beta ROM releases and access to the the online kitchens.
Enjoy!
http://android.modaco.com/content/s...rom-for-samsung-galaxy-s-with-online-kitchen/

Does this ROM fix the ram issue so that all 512MB of ram is utilized?
Congrats on being the first custom rom here.

Congratulations! I don't have a phone yet but I am very pleased to see a custom rom already!

woohoo custom ROMs already. Guess I'll be getting myself the phone after all.

umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?

Perrosky said:
umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?
Click to expand...
Click to collapse
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.

Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?

Javalu said:
Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?
Click to expand...
Click to collapse
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean

psychoace said:
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.
Click to expand...
Click to collapse
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.

Papa_I said:
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.
Click to expand...
Click to collapse
No it doesn't rule out plain vanilla android rom. Yes they will all be based on Samsung but rom makers can take out all the touchwiz garbage and throw in another launcher like adw or Launcherpro.

That's what I wanted to hear. Thanks for the help. Now if I only could decide if I should keep the Nexus One or purchase this phone..... Decisions, Decisions.

psychoace said:
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean
Click to expand...
Click to collapse
How lame. Have other handsets had similar problems?

what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.

Javalu said:
How lame. Have other handsets had similar problems?
Click to expand...
Click to collapse
Yes the Behold 2, the original Galaxy, and the Moment all made by Samsung have only had Samsung roms on them.
lgkahn said:
what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.
Click to expand...
Click to collapse
So they can easily be decompiled? If it's source code why is it already compiled?

dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?

raspdeep said:
dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?
Click to expand...
Click to collapse
What about s3clcd? Here is a little copy and paste of some of the garble that was in the compiled file
screen width=%d height=%d va=0x%x pa=0x%x
I would go out on a limb and say those are video drivers. The one's that have been encrypted on all other samsung phones.
Also in s3cbc there is some code at the bottom
PVRSRV_PIXEL_FORMAT_YUY2 PVRSRV_ERROR_FIFO_SPACE char ui32ByteStride psDevInfo PVRSRV_PIXEL_FORMAT_PAL1 PVRSRV_PIXEL_FORMAT_PAL2 pfnOpenBCDevic
If you don't know the Galaxy's gpu is PowerVR SGX540 and YUY2 is a colol format for video screens
http://www.fourcc.org/yuv.php#YUY2 and Pal is of course a European video standard.

they are not encrypted, they are object codes in machine language for arm.. and why we need that again for custom roms?

Wanted to test modaco ROM but they are not free.. Any kind souls upload and share ?

well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here

Ferdimage said:
well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here
Click to expand...
Click to collapse
How much free ram have you got? Considering flashing and rooting, but not sure if it's worth it right now. Meh 10£ isn't that much think I'm gonna give it a try.
EDIT: Just flashed, but now I don't have root access(says access denied when I try to access the /data/data folder). Thought this included the rooted PDA file or do I have to flash that again with odin?
EDIT2: Scratch that I forgot to press the allow-button on my phone after sending the Super-user request..

Modifying Android's built-in apps

Hi guys!
I'm wondering what I'd have to do if I wanted to modify the built in apps inside Android..
I've got a HTC Hero running FroydVillain 1.5.0. Let's say... I want to modify the messaging app that's included, MMS.apk. I wouldn't know how to go about this, and I have a few questions...
Firstly, what sources exactly are used for building the built in apps for a given ROM? The source code link in the FroydVillain post, for example, is just for the kernel. The rest of the OS isn't there.
Secondly, I hear that in order to modify a built in app, you need to build the entire OS. If I just download all the code from Google official repo, and compile that, will it just... work on my phone, provided I use a kernel that is specific to my phone?
Lastly, are there any tips anyone has for someone who just wants to modify a couple of the built in apps? Is it possible to build them as standalone apps? Or import them into Eclipse?
I've had a search around the forum and the internets in general, and people have asked similear questions, but I've yet to find a good answer. This thread comes to mind: http://forum.xda-developers.com/showthread.php?t=635197
If anyone could help me, or point me in the direction of any help, that'd be awesome! Thanks!!

FunkTrooper said:
Hi guys!
I'm wondering what I'd have to do if I wanted to modify the built in apps inside Android..
I've got a HTC Hero running FroydVillain 1.5.0. Let's say... I want to modify the messaging app that's included, MMS.apk. I wouldn't know how to go about this, and I have a few questions...
Firstly, what sources exactly are used for building the built in apps for a given ROM? The source code link in the FroydVillain post, for example, is just for the kernel. The rest of the OS isn't there.
Secondly, I hear that in order to modify a built in app, you need to build the entire OS. If I just download all the code from Google official repo, and compile that, will it just... work on my phone, provided I use a kernel that is specific to my phone?
Lastly, are there any tips anyone has for someone who just wants to modify a couple of the built in apps? Is it possible to build them as standalone apps? Or import them into Eclipse?
I've had a search around the forum and the internets in general, and people have asked similear questions, but I've yet to find a good answer. This thread comes to mind: http://forum.xda-developers.com/showthread.php?t=635197
If anyone could help me, or point me in the direction of any help, that'd be awesome! Thanks!!
Click to expand...
Click to collapse
1) The whole sources for everything are there
http://github.com/ninpo
2) You can import the sources to eclipse, but I think you will need to build the entire tree, as opposed to just what you change
3) Apktool lets you do smali and resource edits on an APK. Without knowing what you aim to do, it's hard to guide you specifically.

Most apps are based on the sources provided by google. I assume you are talking about Froyo Hero ROMs (i.e. FroydVillain), which apps are generally built from the source of CyanogenMod. Specifically for FroydVillain, if you look around ninpo github you will see some packages with some changes to their code, although it does seem that many of the changes in recent releases are not there. I have actually PMed ninpo about this and hopefully this is only a technicality.... I assume that the other packages and apps (most of them) he just compiled off the CM sources without changes.
In any case, if you compile an app either from the CM source or from google's original sources, it should work just to copy the apk file - just make sure you use an appropriate ROM (i.e. Froyo ROM if you built it from Froyo sources). The reason to want the CM sources, is that if they have incorporated further fixes (over the google sources) you may want them.
Finally, some more practical advice: I would start with the google sources: http://source.android.com/source/index.html since I have found these instructions and explanations easier to begin with - it should be quite straight forward to build these sources on a linux machine (or VM).
Then you can also try to tackle the cyanogen source: http://wiki.cyanogenmod.com/index.php?title=Building_from_source currently missing instructions on how to build for hero. But if you only want to copy apks out of it, you can just build a generic build (like in the google souce).
If you have specific problems, ask and I'll try to help you.
Good luck.

pulser_g2 said:
1) The whole sources for everything are there
http://github.com/ninpo
Click to expand...
Click to collapse
For example where are all the changes to the dalvik code? I do not follow closely enough the changes in Froyd to point out other things which might be missing (if at all), but there are relatively few committed changes to the CM code. Specifically the dalvik code, ninpo mentioned hundreds of changes which caught my interest and are definitively not there.
The kernel sources do seem to be up to date always - been following that one closely .

Thanks for the advice I love this forum!
What I'm trying to do, in case you're wondering, ultimately, is to modify the built-in messaging application to give the user the option of sending a message by the normal method, or by using their provider's free webtext service, something that all the carriers seem to offer here in Ireland.
So, for example, you'd press the Send button, and you'd be able to select one of those methods. (of course, you'd have to have a data connection for the webtext). There's also be an interface for entering your login credentials for your carrier's website.
I'm doing this party because it would be very useful. I also feel that it would give me a good introduction to how you'd go about modifying Android. I mean, from a programming point of view, it shouldn't be *too* hard to do. I already have a simple standalone app that I made which can send a text message via an Irish carrier's webtext service. But it's all good experience to try to modify other people big codebases.
I have a good bit of experience with web application development, but my experience with other programming is a little more limited. I usually use PHP, where there's none of this compiling nonsense. You just write scripts and off they go!
So I'm gonna go off and see if I can set up an environment where I can build.. the OS, I guess.
If I was to take the vanilla official Google sources, would they work on my phone? Or would I have to use an official Google developer phone... or the emulator? Or maybe if I stopped writing here and investigated those links you've provided, I'd know that by know.
Brb, investigating

Yeh investigating and just trying to do it is usually the best way
To clarify what I was trying to say above: All the java code is obvious very portable - one of the big advantages of java. In the case of android it is compiled to an .apk file and this file should be, at the very least, portable to all android "devices" running this android version. So the apk you build (for example from the vanilla 2.2 sources) should work on the emulator (good for initial debugging) and any 2.2 ROMs.

erasmux said:
For example where are all the changes to the dalvik code? I do not follow closely enough the changes in Froyd to point out other things which might be missing (if at all), but there are relatively few committed changes to the CM code. Specifically the dalvik code, ninpo mentioned hundreds of changes which caught my interest and are definitively not there.
The kernel sources do seem to be up to date always - been following that one closely .
Click to expand...
Click to collapse
I'm currently on "vacation" from any and all Android development for a week. I'll be back after the weekend, at which time my modifications will be cleaned up and committed to git. The kernel is always current with my latest kernel release due to GPL obligations. The extra time away has also highlighted some changes I need to make both to the kernel and to my Android modifications when I get back.

Hacre said:
I'm currently on "vacation" from any and all Android development for a week. I'll be back after the weekend, at which time my modifications will be cleaned up and committed to git. The kernel is always current with my latest kernel release due to GPL obligations. The extra time away has also highlighted some changes I need to make both to the kernel and to my Android modifications when I get back.
Click to expand...
Click to collapse
Thanks Ninpo

[App] 2BOrange - Install any kernel (Voodoo, SpeedMode, Infusion...) without computer

____________________________________
2BOrange
____________________________________​
Hi everybody,
I have made a free application to install any kernel on your SGS very easily.
The idea is that there is a website where kernel are uploaded with a script and an application to:
- search
- download
- install it on your phone.
The application and the website are not limited to install kernell but I think it is a good way to try it.It can execute any script in the android shell.
So I have made some script for some kernel, there are so much that I have not the time to make one for each of them.
To make a script is very easy, I have attached an example of one I have uploaded on the website. If you need to attach a file, put it in a zip and upload both (the script and the zip) through the upload form on the website,
The address of the website is:
http://www.2borange.com/
A general thread on XDA (not dedicated to kernel on SGS) about the application:
http://forum.xda-developers.com/showthread.php?p=14875954#post14875954
You need to create an account to upload but it is not mandatory to just search, download and install a kernel.
Please keep me informed if everything work or not. I have only test it on my phone.
For the author of the kernels: I am sorry to have not yet informed you of the sharing of your great work, I will do it for sure when I will have done enough test to offer you an interesting way to share your work.
For the user: if you have time, don't hesitate to upload some scripts, it is free and easy to do...
Thank you for everything,
Michael
LIST OF KERNEL AVAILABLE AS OF JUNE, 27:
- Galaxian
- Infusion Kernel Faster Fusion Reaction
- Semaphore Kernel JVH - JVP
- SpeedMod Gingerbread
- TalonDEV
- TEGRAK lagfix- Voodoo kernel installer
- Voodoo kernel JVP
Don't hesitate to upload some new firmware. A model of script is provided below as attachment

niceee something to look foreward to

Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000

O-T said:
Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000
Click to expand...
Click to collapse
This allows you to actually find a kernel, download it and flash it as well. The Kernel Flasher is just for kernels already on your sd card.

O-T said:
Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000
Click to expand...
Click to collapse
Thank you for your message.
I did not know about this application. I have read the description and I can tell you the purpose of mine is totally different.
I have understood that Nedar application is to install a Kernel that you have already downloaded and copy on your SDCARD.
The purpose of my application is to download automatically a script and a zip file, and execute the script.
So there are 2 main differences between these two applications:
- my application get files you need directly from the cloud (Internet), so it is like a deposit of files
- my application is not limited to kernel installation, it is just a usefull example to show people how it works, but it can do more, really lot more tasks.
However, because the application of Nedar is dedicated to one particular task, it has option I have not yet implemented in mine. By example, I have not yet construct a script to backup the kernel in an update.zip file, which could be very usefull.
So they are really very different. I hope I will be able to construct more script, but may be the biggest difference with any dedicated application is that anyone can participate to my project without any knowledge in Java programation.
You just have to know a little bit about shell to be able to share your work with others.
THAT IS THE REAL PURPOSE OF THIS APPLICATION : SHARING!

Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!

Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.

omzworld said:
Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!
Click to expand...
Click to collapse
lttldvl said:
Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.
Click to expand...
Click to collapse
Thank you for your interest.
The thing I need now is not money, donation,etc... but report of test and ideas of improvment.
By the way, I only have a samsung phone, and I am wondering if there are possibilities to install kernel in other phone only by using the shell, have you an idea ?
Second question: have you an idea how to proceed to install an entire ROM through the shell ? I suppose the phone has to be rebooted before installation begin and lauche in a recovery mode, but how to make it automatic like in ROM Manager?
Thank you for your help!

omzworld said:
Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!
Click to expand...
Click to collapse
What is the way it should take for you?
I need ideas

lttldvl said:
Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.
Click to expand...
Click to collapse
I have already included a kind of filter based on brand, model of phone and firmware version plus sdk version, do you think it could be more precise?

Fixed script on server, should work on every phone now

Hey snoopy33, why do you have not yet updated this page?

[wip][rom][aosp] ns2

Change of plans, hopefully with the help of anyone who is willing I'd like to compile an aosp build for the Sprint GS2 from source instead of trying to hack a port together, as suggested in this thread and other places, it just feels like it will be a lot more of a fruitful experience for all involved and have a better end result.
(a big thank you to everyone who so far have been super encouraging and friendly with noob questions, it's much appreciated!, I hope that if you wanted to help with the port you'll help with this build as well!)
This is a WIP. Starting out with Samsung's open source platform and kernel instructions on how to build from aosp and I'll take it from there.
I've setup some repos to get this all started in one place:
Samsung SPH-D710 platform source - https://github.com/thefredelement/sph-d710_platform_source
Samsung SPH-D710 kernel source - https://github.com/thefredelement/sph-d710_kernel_source
Team Hacksburg kernel source - https://github.com/thefredelement/android_kernel_samsung_c1spr
Stock kernel initramfs (thanks buddy323!) - https://github.com/thefredelement/stock-initramfs-eg30-epic-4g-touch
https://github.com/thefredelement/Samsung-Galaxy-S2-Sprint-Epic-4G-Touch-AOSP-Build - will be where the build will live after I push over Samsung's platform make and upload it!
--- old stuff that will make your head spin ---
If anyone wants to continue working on this, feel free.
This is my attempt to get get a pure aosp build of android 2.3.5 for the Sprint Galaxy S2. I've never done anything like this before and it's mostly hacked together pieces of two different ROMs. I guess you can call this a "learning" experience.
THIS ROM JUST BOOTS AND NOTHING ELSE REALLY WORKS, THIS IS A WORK IN PROGRESS AND I POSTED IT HERE TO SEE IF ANYONE CAN HELP, THIS IS NOT A DAILY DRIVER, NOT EVEN CLOSE.
THIS HAS ONLY BEEN RUN ON MY PHONE, EVERYTHING IS FINE ON MY PHONE AND I CAN RESTORE A NANDROID BACK TO STOCK AND EVERYTHING STILL WORKS FINE BUT I MAKE NO GUARANTEES FOR YOUR PHONE. IF YOU DO NOT KNOW WHAT YOU'RE DOING I WOULD STOP READING NOW
This rom is based on AdamG's devnull-test aosp rom for the Euro Galaxy S2. (post: http://forum.xda-developers.com/showthread.php?t=1183063)
Credit must be given to AdamG for his rom in the first place, bubby323 for his help on IRC and kpkimmel at ACS for the Gerbal V1 beta ROM (post: http://www.forums.acsyndicate.net/showthread.php/2734-ROM-Gerbal-v1-beta-ROM) which I used for guidance for the build.prop and updater script.
I am not trying to steal anyone's work or take credit for anything, I really just want a pure AOSP rom for the Sprint GS2 and would love anyone's help as far as guidance, code, a guide I haven't found, anything would be great, thanks.
Known bugs:
- No radios
- No Wifi
- When wifi is on (or trying to turn on) the screen turns on/off as if a process is restarting
- Orientation sensor is out of whack (disable auto rotate so it doesn't drive you crazy)
- Home button & search button do not work
- Something FCs real fast on first boot but android setup starts
- Distortion on the touch screen occasionally
Known positives:
- No real FCs
- I added the Nexus S boot animation
- Calculator, gallery, etc. all work fine
What I've done so far:
Based on buddy323's advice in IRC, I've brought over vendor, firmware, wifi, vold, egl and hw from the Gerbal v1 rom to the devnull rom.
I used the wipe partition section of the Gerbal update script and then the symlinks/permissions from the devnull script (I removed the kernel installation as this rom doesn't come with a kernel). My approach has been to go through as much as I can on devnull and change out anything that's platform specific to the sph-d710.
I'm sure there's a bunch of noob happening in this rom and I'd appreciate it if you can call me out on it and tell me where to look to make it right.
Installation:
Install via clockworkmod, this will wipe /system /data so I'd erase your user data before flashing.
I've been booting this with the stock kernel.
Link: you don't want this...

Reserved for changelog, when hopefully it gets that far

Awesome to see a project like this, good luck in the port!
Sent from my SPH-D710 using XDA App

O_OMG <3 :-!
Sent from my SPH-D710 using xda premium

Good luck! Looking forward to this.

What kernel did you use theres? Or did you build an aosp one for our phone?
Sent from my SPH-D710 using XDA App

deano0714 said:
What kernel did you use theres? Or did you build an aosp one for our phone?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
This boots using the stock Sprint/Samsung kernel.

xploPR said:
Waste my time with this crap... it does not even work, why upload something that does not
work? Smh
Click to expand...
Click to collapse
What kernel are you using?

thefredelement said:
What kernel are you using?
Click to expand...
Click to collapse
im using stock

xploPR said:
im using stock
Click to expand...
Click to collapse
Did you wipe all of your user data before installation?
Do you get to the boot animation?

Constructive criticism would be for me to point out you must not have read the OP because it clearly said nothing works because we don't have a aosp kernel yet but you are just rude.
Sent from my SPH-D710 using xda premium

xploPR said:
Waste my time with this crap... it does not even work, why upload something that does not
work? Smh
Click to expand...
Click to collapse
ehusidic said:
The title clearly states its not ready or stable so chill out while the devs do what they do
Click to expand...
Click to collapse
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic or infractions and/or mandatory vacations will be handed out.

I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.

jerdog said:
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic ore infractions and/or mandatory vacations will be handed out.
Click to expand...
Click to collapse
Sorry for the horrid insults I aimed at the complaining member. Too uncouth.
Sent from my SPH-D710 using xda premium

Hacre said:
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
Click to expand...
Click to collapse
Thanks for the heads up. I agree this is a much better idea.

jerdog said:
You are under no obligation to install anything posted on XDA. If it doesn't work, report. If you don't like it, don't use it. Help, don't hinder. If you have nothing to contribute, then sit down, shut up and wait for someone to do it and allow you to participate. It's that simple folks.
Now keep this on topic or infractions and/or mandatory vacations will be handed out.
Click to expand...
Click to collapse
i like that mandatory vacations with paid vacations to hawaiii, can xda hook it up or what?

thefredelement , good luck. glad to see new devs... i hope to be there one day but i'm way off...
Thanks!

thefredelement said:
This is my attempt to get get a pure aosp build of android 2.3.5 for the Sprint Galaxy S2. I've never done anything like this before and it's mostly hacked together pieces of two different ROMs. I guess you can call this a "learning" experience.
THIS ROM JUST BOOTS AND NOTHING ELSE REALLY WORKS, THIS IS A WORK IN PROGRESS AND I POSTED IT HERE TO SEE IF ANYONE CAN HELP, THIS IS NOT A DAILY DRIVER, NOT EVEN CLOSE.
THIS HAS ONLY BEEN RUN ON MY PHONE, EVERYTHING IS FINE ON MY PHONE AND I CAN RESTORE A NANDROID BACK TO STOCK AND EVERYTHING STILL WORKS FINE BUT I MAKE NO GUARANTEES FOR YOUR PHONE. IF YOU DO NOT KNOW WHAT YOU'RE DOING I WOULD STOP READING NOW
This rom is based on AdamG's devnull-test aosp rom for the Euro Galaxy S2. (post: http://forum.xda-developers.com/showthread.php?t=1183063)
Credit must be given to AdamG for his rom in the first place, bubby323 for his help on IRC and kpkimmel at ACS for the Gerbal V1 beta ROM (post: http://www.forums.acsyndicate.net/showthread.php/2734-ROM-Gerbal-v1-beta-ROM) which I used for guidance for the build.prop and updater script.
I am not trying to steal anyone's work or take credit for anything, I really just want a pure AOSP rom for the Sprint GS2 and would love anyone's help as far as guidance, code, a guide I haven't found, anything would be great, thanks.
Known bugs:
- No radios
- No Wifi
- When wifi is on (or trying to turn on) the screen turns on/off as if a process is restarting
- Orientation sensor is out of whack (disable auto rotate so it doesn't drive you crazy)
- Home button & search button do not work
- Something FCs real fast on first boot but android setup starts
- Distortion on the touch screen occasionally
Known positives:
- No real FCs
- I added the Nexus S boot animation
- Calculator, gallery, etc. all work fine
What I've done so far:
Based on buddy323's advice in IRC, I've brought over vendor, firmware, wifi, vold, egl and hw from the Gerbal v1 rom to the devnull rom.
I used the wipe partition section of the Gerbal update script and then the symlinks/permissions from the devnull script (I removed the kernel installation as this rom doesn't come with a kernel). My approach has been to go through as much as I can on devnull and change out anything that's platform specific to the sph-d710.
I'm sure there's a bunch of noob happening in this rom and I'd appreciate it if you can call me out on it and tell me where to look to make it right.
Installation:
Install via clockworkmod, this will wipe /system /data so I'd erase your user data before flashing.
I've been booting this with the stock kernel.
Link: http://www.multiupload.com/OF1HXSSOCJ
Click to expand...
Click to collapse
hit me up i can get ur rom working with wifi/3g/4g/whatever. zedomax at gmail dot com

Hacre said:
I would highly recommend you get to grips with the aosp source and learn to build them for the device instead of cobbling a mix of aosp and stock Samsung roms together. You will also need an aosp compatible kernel and stock kernel is not. There is a list of patches to the aosp kernel in the SGS2 section and on team hacksung's github. Good luck.
Click to expand...
Click to collapse
I recall rumor about samsung sending a GS2 to Cyanogen so that he could "get to work". Guess that never materialized - or they gave him something else to do once they hired him...
Sent from my SPH-D710 using xda premium

it was one of the cyanogen devs that got a galaxy2 & they have nightlies for the gs2 now.... It should not be hard to get it ported over
....
One of the devs on teamhacksung was asking for people with the phone to help with it ..he ask on twitter like the 16th so they are probably working on it....
Sent from my SPH-D710 using xda premium

I need a smart Dev to dummy something down for me...

I have been in love with all things Android for years but there is a certain level of proficiency that I don't think I'll ever reach. I'm reaching out to anyone who can provide me with some assistance in this issue. I have a Nexus (my wife's) that constantly crashes the Talk and Camera apps. I've tried dozens of solutions posted online but I think the only one that actually addresses my issue is provided in the link below. Unfortunately, when it comes to compiling Android source code I get in over my head.
Could someone please give me instructions on how to implement this fix? I would like to run AOKP JB Milestone 1. It appears I need to swap out the binaries before compiling and flashing this ROM but that's about as much as I can tell.
Please help!
Link describing the fix -------------> http://anders.com/cms/435

Is there a reason you don't just flash the aokp rom that is already compiled? You do need to get some of the closed source proprietary files if you are compiling yourself (though I would have thought that aokp would already have everything set up in a vendor folder for your device). Talk is not part of aosp and you should be able to get it working by flashing a gapps package. It sounds like you are missing the talk libs (.so file) that goes in /system/lib. Look for libgtalk_initial.so and libgalk_stabilize.so. For the camera, make sure you have the ducati-m3.bin in /system/vendor/firmware. You can get these files from the factory images provided by Google or download a stock rom.
If you are compiling source yourself, the easiest way to see if anything is missing is to extract the factory image or a stock rom and use a program like beyondcompare to see the differences between your rom and one from Google.
Sent from my Nexus 7 using xda premium

mwalt2 said:
Is there a reason you don't just flash the aokp rom that is already compiled? You do need to get some of the closed source proprietary files if you are compiling yourself (though I would have thought that aokp would already have everything set up in a vendor folder for your device). Talk is not part of aosp and you should be able to get it working by flashing a gapps package. It sounds like you are missing the talk libs (.so file) that goes in /system/lib. Look for libgtalk_initial.so and libgalk_stabilize.so. For the camera, make sure you have the ducati-m3.bin in /system/vendor/firmware. You can get these files from the factory images provided by Google or download a stock rom.
If you are compiling source yourself, the easiest way to see if anything is missing is to extract the factory image or a stock rom and use a program like beyondcompare to see the differences between your rom and one from Google.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
See, this is where I'm confused. I'm not compiling the ROMs or any of the gapps myself. I'm flashing a copy of AOKP that I used on other nexus devices and had zero issues. For some reason this phone won't work quite right. I've wiped, clear data, fixed permissions, blah blah blah.
From hefty googling I have found a decent number of other threads with my exact problem but none of the threads actually have a solution.

mwalt2 said:
Is there a reason you don't just flash the aokp rom that is already compiled? You do need to get some of the closed source proprietary files if you are compiling yourself (though I would have thought that aokp would already have everything set up in a vendor folder for your device). Talk is not part of aosp and you should be able to get it working by flashing a gapps package. It sounds like you are missing the talk libs (.so file) that goes in /system/lib. Look for libgtalk_initial.so and libgalk_stabilize.so. For the camera, make sure you have the ducati-m3.bin in /system/vendor/firmware. You can get these files from the factory images provided by Google or download a stock rom.
If you are compiling source yourself, the easiest way to see if anything is missing is to extract the factory image or a stock rom and use a program like beyondcompare to see the differences between your rom and one from Google.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
ANY AOSP rom should have these binary files.
http://forum.xda-developers.com/showthread.php?t=1386615

So in other words, it doesn't sound like this will solve my problems then, huh?

cartisdm said:
So in other words, it doesn't sound like this will solve my problems then, huh?
Click to expand...
Click to collapse
Check logcat/dmesg right after you reproduce the issue. (ref: http://forum.xda-developers.com/showthread.php?t=1812959)
We need more insight/details as to why it is failing.
Your wife's phone currently runs:
carrier: ______
rom: _____
rom build number: _____
kernel: _____
bootloader: ______
radio: ______
Have you tried starting fresh, flashing nexus factory image through fastboot, as per (ref: http://forum.xda-developers.com/showthread.php?t=1626895) ?