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.
Related
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
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 ?
Hi friends,
I am proud to join the SGN community. currently my phone is rooted, running on Ginger Bread, kernel version Abyssnote 4.2. Everything just works fine thankful to the developers for their great job and clear instructions. Well, let me not drag it anymore. Has any developer made MIUI ROM based on ICS designed for Galaxy Note? Because previously I used to own a Samsung I9000 and for that model, there was (and still is)a whole bunch of different ROMs with different modifications and tweaks and the list included some MIUI ROMs too which were really cool to look at and fun to use. I just love the themes and those animations on MIUI.After buying this new Samsung Galaxy Note I really hoped I could flash a MIUI based on ICS but unfortunately could't find one here on the forum. I hope my thread sparks some interest in all developers' minds and they come out with a cool ROM for all of us. Thank you for reading my thread patiently. Cheers
Try this link..
http://forum.xda-developers.com/showthread.php?t=1521630
Hi Ranjan.Alva,
Thanks for the link to MIUI based on ICS. I am going to flash and see how it works on Galaxy Note.
I tried that ROM too...well, everything looks fine except that the inbuilt player won't play anything from the external memory card. Funny isn't it? What is the use of flashing a ROM if you have to depend on the internal memory all the time?....Any suggestions???
Why nobody wants to complete the ICS port from SGS II to SGS? There are themes that imitate well stock ROMs, but the biggest drawback is that you can not use sliding left right to call or send messages. There Ex dialer but does not compare to feeling of Samsung dialler. Escuse my bad English!
I totally agree with you.
I tried some ICS roms and finally I came back to stock rom just for the feeling and the easy of use it provides.
Every new rom of ICS or JB for the SGS comes from Nexus S or other phones and it doesn't have the appearance or the functionality of stock GB roms.
Apart from that, every custom ICS or JB rom is worth and the developers deserve every credit and thank you in the world but I also wonder...
Is it so difficult to take the original SGS II rom for ICS and adjust it for our beloved SGS???
I'd like to have Samsung experience with an ICS or JB ROM.
Ifind Touchwiz very user friendly and efficient for all the basic tasts, and I don't find something equivalent in ICS "nude" ROMS.
It exists some ICS ROM with some parts of Touchwiz, but you don't have the full integration you can find in stock ROMS.
I think it's impossible to directly port SGS2 or SGS3 tou our old SGS.
Source code is not available for stock ROMS, so it's very difficult to modify it to adapt it to another device.
The only way is to mix binairies and edit some config files.
rbart said:
I'd like to have Samsung experience with an ICS or JB ROM.
Ifind Touchwiz very user friendly and efficient for all the basic tasts, and I don't find something equivalent in ICS "nude" ROMS.
It exists some ICS ROM with some parts of Touchwiz, but you don't have the full integration you can find in stock ROMS.
I think it's impossible to directly port SGS2 or SGS3 tou our old SGS.
Source code is not available for stock ROMS, so it's very difficult to modify it to adapt it to another device.
The only way is to mix binairies and edit some config files.
Click to expand...
Click to collapse
I can't understand why is it so easy to make a Nexus ICS rom work quite good on a SGS and is not the same for the SGS II rom.
Maybe a developer of ICS can provide more information.
szapco said:
I can't understand why is it so easy to make a Nexus ICS rom work quite good on a SGS and is not the same for the SGS II rom.
Maybe a developer of ICS can provide more information.
Click to expand...
Click to collapse
Because Nexus S has the same hardware as Galaxy S and it's very easy to take a binary or a driver from one to install it on the other one.
Android source code is available, but not Touchwiz and Samsung add ons code. You can't modify or recompile Samsung stuff, so it's harder to port.
I was looking into Jelly Bean ROMs here, and I couldn't find anything that's working as I had hoped for.
Or I just didn't look through stuff on here in more detail.
So I was looking at some 'light' ROMs and found SlimBean, but it only seems to support i9000 (as listed here) whereas I'm running i9001.
Here comes the stupid question - would it work or not?
I kind of want to test that out, because the ROMs I used previously didn't have a working microphone (which I kind of needed for making calls) so I'm thinking this one would have a working one and would have a decent amount of Project Butter.
So anyway, what JB ROM would you recommend? It doesn't have to be 'slim', as long as most stuff works on it.
Hi,
most or nearly all roms wont work on your device. I found a nice JB Rom called Mackay Rom for my Samsung Galaxy S.
Its fast and stabil. If you find this Rom for your device, you could try it, he is updating this rom fast and the changes are nice.
Most JB Rom use CM10 as basis so the difference wont be that huge^^
None of the i9001 Jelly Bean ROMs are fully functional at the moment, as you have noticed. i9000 ROMs will not work on i9001, as it is a totally different phone. Only things we have similar is the screen, battery size and the form of the phone, CPU & GPU being different makes it impossible to use the same ROMs.
There is a lot of work to be done and a few talented people doing the work. Just keep on looking in the Galaxy S Plus I9001 Android Development, all progress will be posted in there. Pretty much the only JB rom we have is DoomNEXUS by Doomsday94.
There also is the I9001 Q&A section that these questions should be directed to.
Slim Bean Best one