Database Develop

[Q] Stock Froyo for Galaxy S

Hi folks,
This is a noob question. I am unable to find any post related to stock Froyo for Galaxy S. Is something like this out yet ?
By stock I mean, Android as Google release it, without any reseller trash on it.
Thanks in advance

there is no froyo for SGS yet, at least not officially
much less a stock froyo
there are tons of phone killing Beta froyos if you feel brave

Thanks for letting me know. I am not confident yet in any beta out there, although a lot of phones are using it without any issue...
Hoping that stock will be released soon.
Thanks

It won't (be released soon).
Currently there are community efforts going on to try and get stock 2.1 run on the SGS but they still have a way to go.
After that, once samsung releases the sources for 2.2 they can start trying to get a stock 2.2 running. They have to wait for Samsung because of drivers and such.
Hoping that what they've learned from 2.1 can largely be reused there's a good chance a stock/AOSP 2.2 ROM could make it's way relatively fast to the SGS but for now, don't hold your breath.

Ladduro said:
Hi folks,
This is a noob question. I am unable to find any post related to stock Froyo for Galaxy S. Is something like this out yet ?
By stock I mean, Android as Google release it, without any reseller trash on it.
Thanks in advance
Click to expand...
Click to collapse
I really don't think it can ever be called stock. All releases have to be configured and customised to the platform they are running on. With Linux or Windows it is all on the disk and web server, drivers etc etc. You cannot do this with phone firmware as the download would be huge.
And just like Windows or Linux there are some stock programs that each will install. So what can we call "stock"? Even the Nexux 2.2 has to be configured to it.

By stock/vanilla Android, I meant of course a modified one that includes drivers for SGS, but does not include any customer UI made by Samsung.
So stock UI, no additional garbage (iPhone garbage style in SGS case) would be what I really need to see on my phone.
Or maybe a faster way for this is to modify current Samsung ROM and remove TW and Samsung's apps.
Thanks

Ladduro said:
By stock/vanilla Android, I meant of course a modified one that includes drivers for SGS, but does not include any customer UI made by Samsung.
So stock UI, no additional garbage (iPhone garbage style in SGS case) would be what I really need to see on my phone.
Or maybe a faster way for this is to modify current Samsung ROM and remove TW and Samsung's apps.
Thanks
Click to expand...
Click to collapse
Have a look in the Dev threads. There are several Roms that do that.

Hi Tehpriest,
Can you route me to a ROM mentioned by you ? I searched but in vane... no result.
Thanks

+1. Have been seeking a stock UI-based ROM for i9000T for a while now, with no luck.
Cheers!

There seems to now be some skilled developers starting to get Cyanogen 6 (a vanilla version of Froyo) onto the Galaxy S. Assuming they get it running - which I think is likely when Samsung release the source for their spin on Froyo - it will take a while before it's stable and fully featured.
There's a steep learning curve for working out how to backup then flash your phone with a new rom. It took me three days to go through forum posts working it out, and I've now got a beta version of Froyo working fine. My advice is to get Samsung's official upgrade Froyo when it's out and wait until the devs get a chance to get something better running.
Also, use 'Launcher pro' from the market to replace Samsung's launcher, which makes things a whole lot more familiar.

official froyo is out, the wait should be shorter now

I am hoping too for this. I really like to benefit of OOB Android experience as Galaxy S is my first android phone.
Looking forward to see if it... hopefully soon.

wasnt CyanogenMod working on a release for the galaxy s?

[Q] AOSP ROM for Galaxy S?

Hey guys, been out of the loop for a while as I've been settled on JPY for a few weeks now. However, I saw a friend flash his Desire today with Oxygen, a gingerbread-based AOSP ROM. All the SGS ROMs I can find so far are based on the stock Samsung firmware - is there any work being done on a full AOSP ROM like Oxygen or Cyanogen? I can't find any details about this anywhere.

I am very curious about this question. Because if answer is simply no, it's time to sell Galaxy S. Gingerbread will be the last update from Samsung and AOSP could be the future of this phone then CM7 for SGS seems to have big problems and it's the only AOSP ROM for SGS which I'm aware of...

What big problems?
I'm using CM7 for a month right now and it's pretty stable if i can say. Yes, it lacks some features and some bugs are not fixed yet (theres a workaround tho), but if you follow it's thread the progress they make are great. They're already into mainline, so probably it will reach RC status in a month/maybe less, who knows.
After the devs are done, i think there will be a custom ROM based on CM7/AOSP.
~drz

CM7 is getting there. And with Gingerbread coming out, that should make things easier for the dev.

Yes, but with no source then there is nothing big. GB leak, only helped them with "less" important stuff (FM radio, etc.)
~drz

[Q] Stock Android

Hi guys,
I am really interested in figuring out the steps that should be followed in order to compile a stock android rom for i9000.
I find the phone amazing but really hate touchwiz and all samsung's applications.
Thanks in advance

compile a stock android rom for i9000.
Stock as in stock rom supplied by Samsung or do you mean a Custom Rom .
Custom roms are in the development section as are the guys that build them .
jje

JJEgan said:
compile a stock android rom for i9000.
Stock as in stock rom supplied by Samsung or do you mean a Custom Rom .
Custom roms are in the development section as are the guys that build them .
jje
Click to expand...
Click to collapse
I meant vanilla android, i am aware of resources where you can find stock samsung compilations (namely samfirmware -sorry but as a new user i cannot post links- although there's also an updated list in a thread somewhere in xda forums) and i also follow some of the custom made roms (currently i'm using Darky's v9.3).
I would like to get to know how to get my custom rom compiled and packged so i9000 can load it, the reason: i really dislike samsungs additions to android (touchwiz) and i haven't found a custom rom similar to what i am seeking.
For the first steps i suppose i should grab the code from aosp but i just don't know if i need some drivers (i suspect i do), and if so... where can i get these?
Then... once all that stuff is compiled, what are the steps that should be followed to make the compiled image flasheable?
Thanks.

I really thought that the custom ROMS in the dev section could be built as custom as you like via the kitchen. First take the bare Android 2.2.1 JPY/JS5 system and add the Gingerbread launcher as well as the market then off you go. Can't get anymore vanilla than that ?

[Q] Most reliable, yet visually fun TW based custom ROM (preferably JB, or ICS)?

First off-hold your guns!
I know JB as such isn't out yet, and can't be expected to be as stable as ICS... But, still- after watching video reviews of some custom ROMs, one asks themselves, if they should give it a go...
Ok, so I am running stock (LAME!!!, I know ) GB, rooted and couple of launchers make it more interesting, sure... However, after browsing through this lovely and extremely helpful forum, I noticed that there are people who are already enjoying the benefits of running JB ROMs, or very good and matured TW based ICS custom ROMs...
1. So, I know ICS stock kernel has been a bit of a problem, what that just 4.03, or did 4.04 fix that?
2.Kill be for being so easily pleased, but I do find my Note and its current ROM already pretty smooth... I know all the bits that ICS makes it better and even more so JB, but considering all the things ICS brought, is there a point of trying JB, except for experimenting?
3. One thing I am so after, is that bit where from the lock screen you have like 3, or 4 options, one of them being going straight into the camera mode. I don't know if that is only JB, but I could really use it, as the old way (press the menu button, swipe to unlock, then press the camera icon) so many times made me miss the scene I wanted to take a photo of. So, any info on that would be much appreciated.
4.So much hype around GN II, but seeing that so many features are being ported to GN I custom ROMs, I am only after a ROM which will have those new and useful S III and GN II bits sawn onto the old(er) jacket.
5. I am in no rush, so do you think that in 3-4 weeks something more stable JB based will be available(official JB update should be rolling out soon, no)?
Big thanks to all you guys here, not just for answering the questions, but also all the tutorials and topics we noobs can find here... Keep up the good work.

See custom jb roms are stable like cm10 aosp liquidsmooth etc.you will feel smooth quality on it and butter project.
Ics 4.0.4 is very stable and has many mods and a good battery life too.
So lastly its your choice which one to flash.
Hit thanks button pleass
Sent from my GT-N7000 using xda app-developers app

Answering the title of your thread, there are no TW-based JB roms yet. All the TW-based ROMs are ICS. So if you are looking for smooth and reliable TW-based ROMs I would go for Kingdroid (ICS). If you want Jelly Bean you have ParanoidAndroid, Liquidsmooth, but these are not TW-based.
And answering the 5 questions in the contents of your post:
1. The problem is not with the kernel, the problem is with the chip itself, the *workaround* is using a modified kernel that does not use the MMC_CAP_ERASE command, so to answer your question, no the problem isn't solved and it won't be solved unless Samsung recalls all the units and gives out new ones without the bug. You will have to be careful when upgrading to ICS/JB because you will need to use safe kernels.
2. Jelly bean is definitely smoother than ICS, it is worth upgrading IMO.
3. That is the ICS/JB unlock screen that comes in stock android, and it is also available in most AOSP/AOKP ROMs. It is not available by default in Touchwiz but you can download that lockscreen from the Play Store as a standalone app and replace it.
4. Not all the Note2 features have been ported to the Note1, for instance the multi-window view is not available on any ROM yet as far as I know.
5. I have made the switch because I can't stand the look of Touchwiz, the complete disregard of Google's Holo design is for me a reason enough to switch to AOSP/AOKP, that said even when official JB ROMs start rolling out I probably won't come back to Touchwiz.

I think that you need a stock ICS TW rom, maybe RocketRom or Alliance v2.1 rom. I have tried a couple JB roms, but it feels like you have giant nexus insted of a great note.
If you want stock, pick up a last 4.0.4 xxlrt or ddlr9 or something similar, depends where you live but it's not too important. After that, just flash PhilZ kernel and you are safe, disable all aplications that you dont need, and thats it.
Or if you want a custom rom which is great like stock and cool like custom, choose rocketrom v12 or alliance v2.1
Hope that helps!

Ooooohhh-dann so...
Well, that clears so many things...
I mean, am no Samsung fan boy. It is just that I edit many pdf docs on the go, and other TW apps are very useful as they bring the functionality and the precision of the S Pen... As I said. I even find stock GB smooth, so I believe ICS should feel like heaven for me.
BIG QUESTION = so, since the problem was the chip, not the stock kernel itself, and the only solution is a modification of kernel, surely Google will include the workaround in a new JB update, no?
I haven't updated OTA to ICS, because I was scared of bricking the phone, or something.... Are the updates incremental, or so I need to update to official ICS and then to JB, or will I be able to go straight to JB (official one)?
I think I might go for Kingdroid (ICS), or Sweet ROM... Though, I from reading their respective threads, I get the idea that less people have issues with Sweet ROM....
Thanks again...

Ota update from GB ROM is safe because GB kernel is safe. Or can download stock ICS from Dr Ketan and flash with pc odin. Then flash appropriate Philz kernel (can do it from stock recovery). You will then be on safe stock kernel (only brick bug is disabled) with advanced CWM recovery. Once on Phils u can backups/restores and flash any ROM u like. Just have to do full wipe before flashing new ROMs.
Sent from my GT-N7000 using xda app-developers app

cmick30 said:
Ooooohhh-dann so...
Well, that clears so many things...
I mean, am no Samsung fan boy. It is just that I edit many pdf docs on the go, and other TW apps are very useful as they bring the functionality and the precision of the S Pen... As I said. I even find stock GB smooth, so I believe ICS should feel like heaven for me.
BIG QUESTION = so, since the problem was the chip, not the stock kernel itself, and the only solution is a modification of kernel, surely Google will include the workaround in a new JB update, no?
I haven't updated OTA to ICS, because I was scared of bricking the phone, or something.... Are the updates incremental, or so I need to update to official ICS and then to JB, or will I be able to go straight to JB (official one)?
I think I might go for Kingdroid (ICS), or Sweet ROM... Though, I from reading their respective threads, I get the idea that less people have issues with Sweet ROM....
Thanks again...
Click to expand...
Click to collapse
You could try ics stock rom with non stock kernel, i my self use notecore and hydracore kernel while i am using ics rom.
This will give you another experience..
Sent from my GT-N7000 using Tapatalk 2

Samsung S2/S3 Rom on Captivate

Hello ,
few days ago i updated my gf's s2 to new JB that was leaked offical samsung but from odin, then i got an idea, cuz i have Captivate Armani I9010 and i was using Remics JB as last rom, cuz it was look rly nice likly s3 rom, but i didn't like aops dialer layout and some more staff and i got idea of porting S2 or even S3 rom to captivate, and i was playing with some tutorials and android kitchen but without lucky, as I have rly bad knowledge of programing thinks , but I'm trying and want to learn more, my point was that maybe its posible to use some custom aops rom as base(ofc if developer agree) and port s2 rom over, i know that to port stock apk's form s2 that i like i need to port aslo framework, but what else?
Is someone with knowledge are up to help me or take this project if it interesting?
Or if this is totally wrong , what is real way to go of port s2 rom to captivate? I'm sure that its posible i saw some video of s2 rom on i9000 with is pritty much same as capativate. (it was GB i think because video is old) but if it able to port one rom there is no difference but what is good way to start.
I am really sorry about my English , its not my main language, and I am interesting in learning as much as i can about android dev.
Ps. OR mabye it would be easy to just port some of apk instead of porting whole rom. (secphone seclaucher secmms seccontacts systemui etc etc)
Greetings.

bg.stefan90 said:
Hello ,
few days ago i updated my gf's s2 to new JB that was leaked offical samsung but from odin, then i got an idea, cuz i have Captivate Armani I9010 and i was using Remics JB as last rom, cuz it was look rly nice likly s3 rom, but i didn't like aops dialer layout and some more staff and i got idea of porting S2 or even S3 rom to captivate, and i was playing with some tutorials and android kitchen but without lucky, as I have rly bad knowledge of programing thinks , but I'm trying and want to learn more, my point was that maybe its posible to use some custom aops rom as base(ofc if developer agree) and port s2 rom over, i know that to port stock apk's form s2 that i like i need to port aslo framework, but what else?
Is someone with knowledge are up to help me or take this project if it interesting?
Or if this is totally wrong , what is real way to go of port s2 rom to captivate? I'm sure that its posible i saw some video of s2 rom on i9000 with is pritty much same as capativate. (it was GB i think because video is old) but if it able to port one rom there is no difference but what is good way to start.
I am really sorry about my English , its not my main language, and I am interesting in learning as much as i can about android dev.
Ps. OR mabye it would be easy to just port some of apk instead of porting whole rom. (secphone seclaucher secmms seccontacts systemui etc etc)
Greetings.
Click to expand...
Click to collapse
The best way to go about porting a ROM would be to ask one of your fav dev and read one hell of a lot!
Theming is fairly easy, you open the app with something like apktool and work your way through (or can use kitchen). As far as porting apps, it would mainly be the framework but you gotta keep in mind functionality that the Cappy doesn't have.
Reading and guides are really your best friends here. It can all be self learnt but it requires a lot of patience, gotta expect some good old headbanging lol
Here's a thread that could help you: http://forum.xda-developers.com/showthread.php?t=916814

Thanks,
I will probably start with port some apks but, as its not that hard job, but should like to learn how to port rom really i was reading some guides with was like its ok for any phone from same generation cpu like armv7 ported and base rom need to be same version, used same manifecture of device . and what i did used deo-dexed s2 rom JB 4.1.1 official one (aslo found one slimed s2 rom 4.1.1 aslo) and tryed few different as base CM10 for cappy was one of them its 4.1.2 but i think there is no big difference i tryed some 4.1.1 roms as base with was work on phone ok but when i made rom trought those guides its stack on bootanimation and logcat just spam that like every apk die
That was one of guides where it's says that it will work for all stock/cm/aokp roms ICS and JB updated.
There are few really easy steps and what i expected is that phone will boot and will be buggy as **** till a lot of tweaks but it didnt even boot ((
PS. I was looking around and i found that there are some custom rom (this was for s2 ) that are based on samsung base not aokp or cm. And they have all features of custom rom with all stock samsung look witch i like and stock phone/dialer/contact/tw/systemui/ etc etc/
My questions is there mabye that kind of rom for captivate or at least i9000 since i think its easier job to port from i9000 then from s2. And what would be base because last fw for cappy or galaxy s is GB, is there any posiblilty to get ISC or JB samsung based rom on this device?

bg.stefan90 said:
Thanks,
I will probably start with port some apks but, as its not that hard job, but should like to learn how to port rom really i was reading some guides with was like its ok for any phone from same generation cpu like armv7 ported and base rom need to be same version, used same manifecture of device . and what i did used deo-dexed s2 rom JB 4.1.1 official one (aslo found one slimed s2 rom 4.1.1 aslo) and tryed few different as base CM10 for cappy was one of them its 4.1.2 but i think there is no big difference i tryed some 4.1.1 roms as base with was work on phone ok but when i made rom trought those guides its stack on bootanimation and logcat just spam that like every apk die
That was one of guides where it's says that it will work for all stock/cm/aokp roms ICS and JB updated.
There are few really easy steps and what i expected is that phone will boot and will be buggy as **** till a lot of tweaks but it didnt even boot ((
PS. I was looking around and i found that there are some custom rom (this was for s2 ) that are based on samsung base not aokp or cm. And they have all features of custom rom with all stock samsung look witch i like and stock phone/dialer/contact/tw/systemui/ etc etc/
My questions is there mabye that kind of rom for captivate or at least i9000 since i think its easier job to port from i9000 then from s2. And what would be base because last fw for cappy or galaxy s is GB, is there any posiblilty to get ISC or JB samsung based rom on this device?
Click to expand...
Click to collapse
They can all be ported, it's mostly framework. Although, I never ported a ROM so I'm not the best one to guide you through this. If I'm not mistaken, there are guides in XDA-U. Also, there are quite a few nice Devs around here that could help you through it.

Thanks, I saw some of those guides some are generic some are on example but i for porting samsung (s2) based rom i need to use some jb base for captivate cm or aokp but there some difference when porting roms even if both base and port are same version JB . Cuz they are not on same base. And i hope it is not difficult to make. If it's not hard I would please ask some od dev to give me some guide. On what i have to take care . What to do and i will gief all effort and time to make it working.