I suppose this is more a general question rather than specific to the Captivate, but I'm not exactly following what the difference is. I've read entire firmwares referred to as ROMS. I've read individual programs referred to as ROMS. I thought Android programs were apps in the form of .apk files...
Could someone enlighten me on the difference?
maximus-dev said:
I suppose this is more a general question rather than specific to the Captivate, but I'm not exactly following what the difference is. I've read entire firmwares referred to as ROMS. I've read individual programs referred to as ROMS. I thought Android programs were apps in the form of .apk files...
Could someone enlighten me on the difference?
Click to expand...
Click to collapse
The answer is actually both. The standard android apps that you install from the market and internet and such are .apk files. New firmwares that you can install (like CyanogenMod, or Cognition, etc.) are called ROMs. However ROMs may also apply to the files used in emulators. For example if you get an NES emulator, it'll be a .apk, but the game file will be called a ROM. Hopefully that at least partially answered your question.
I hear you on the game roms... been playing with emulators and such for the last 10 years or so.
What I'm sort of thinking, the more thought I put into it... are ROMS (in the android sense) something that has to actually be flashed and modifies/replaces the firmware in someway?
maximus-dev said:
I hear you on the game roms... been playing with emulators and such for the last 10 years or so.
What I'm sort of thinking, the more thought I put into it... are ROMS (in the android sense) something that has to actually be flashed and modifies/replaces the firmware in someway?
Click to expand...
Click to collapse
Yes - that is what ROM Manager is for. So you can play with different ROMs - the different releases for different versions of our phone are ROMs, then there are custom ROMs like Cognition and CyanogenMod (not available for us yet). JH6 is our original factory ROM, there are i9000 ROMs for the international phone, and we can mix and match parts - 2.2 i9000 ROM with Captivate Kernel flashed back in.
APKs are individual apps. They are zip files similar to Jar files.
I have searched and looked everywhere for a good explanation but i haven't found it yet. Can some one be so kind to explain how you go about how to determine which Rom+Kernel+theme work together?
I have also read that people can choice between the captivate roms and the Samsung Galaxy S I9000 roms. What do you need to be able to do this?
Sorry about the question i am new and i hate ask the same question over and over, but i want to know.
Thanks.
Generally the devs package their roms with the kernels that work best together. For the theme, check the themes sections and in the title it will usually tell you what rom it is for.
To use an I9000 rom on the captivate you would need to flash a reoriented kernel so that all the buttons work properly.
the easiest option?
just flash whatever you want from the captivate dev section. all roms are already packaged with a kernel and modem, and most of them are already themed. if they arent, there is an entire theme and app section that contains themes, and they would be listed as being compatible with your specific rom.....
Trial and error. It is what makes XDA go round lol. We all must find what works best for each of us. There is no BEST combo. Just best for you and your device
Sent from the Bat Cave
Hey!
After looking through the G2X Forums, i see there is a hell of lot of roms out there. (Heck they even startet porting ICS!!) That's much more than the 3-4 we have. Is it possible to port a G2X rom to our O2X? Isn't it just a change of partitions?
'Off course we dont get radio, but how many of us actually use it
Oh, and BTW, i am not a developer... More of a dummy
+1
Sent from my LG-P990 using XDA App
sorry, i dont thing there's much chance of it happening.
& dont worry about ice cream sandwich, we will probably get it soon enough after google releases the source code
so what is real difference between both of them? i mean from the outside they look the same...i have a optimus 2x and i really would like to know
schölli said:
so what is real difference between both of them? i mean from the outside they look the same...i have a optimus 2x and i really would like to know
Click to expand...
Click to collapse
The phones are almost identical, though each of them have very different filesystems which is near impossible to change. plus i think it can run hspda 850mhz frequency i think. Other than that, they are exactly the same.
schölli said:
so what is real difference between both of them? i mean from the outside they look the same...i have a optimus 2x and i really would like to know
Click to expand...
Click to collapse
Different partition layout and different radio hardware.
It doesn't really have anymore ROMs then we do, just some minor changes, but they're based on 2-3 different roms like ours (Ok, they do have ICS port also). There just are more cooks, not that many devs. BUT, they do have a few more kernels and I don't see a reason why we couldn't use their CM-kernels on our phone if we wanted. But maybe we dont? Their stock probably won't work on LG stock, so.
Edit: I changed my mind, there isn't even more kernels. We don't need them.
But is there not a way to make ROM's able to work on each others devices?
Im thinking:
You flash a ROM for the G2X on our O2X.
Then you flash some G2X to O2X ROM Converter changing the partitions and HSPDA freq?
Badabim badabum.. lockscreen!
Possible or? If possible, then we have the 2x dev power
Balano said:
But is there not a way to make ROM's able to work on each others devices?
Im thinking:
You flash a ROM for the G2X on our O2X.
Then you flash some G2X to O2X ROM Converter changing the partitions and HSPDA freq?
Badabim badabum.. lockscreen!
Possible or? If possible, then we have the 2x dev power
Click to expand...
Click to collapse
This can be done. Although I don't know to which extent. You will need to have hardware checks on which drivers to load, config, partition schemes, etc. It's a actually a very neat idea. Good for experimentation
More like linux running on different hardware configurations I'd love to see the day when we have a generic Android base that works on all devices. Then for specialized drivers, you can get them from the vendors -- bliss!
That would actually be nice - But would the shared Rom then not be huge? 1gb+?
Maybe some developers would look in to it and maybe share a beta for us to test out on different Roms and types of 2X'es. .
Balano said:
That would actually be nice - But would the shared Rom then not be huge? 1gb+?
Maybe some developers would look in to it and maybe share a beta for us to test out on different Roms and types of 2X'es. .
Click to expand...
Click to collapse
Yep. It could be significantly bigger than today's roms since you will bundle generic drivers for all supported devices. But that's easy to fix. The bigger hurdle is to make it work.
Sent from my Optimus 2X using xda premium
Balano said:
Hey!
After looking through the G2X Forums, i see there is a hell of lot of roms out there. (Heck they even startet porting ICS!!) That's much more than the 3-4 we have. Is it possible to port a G2X rom to our O2X? Isn't it just a change of partitions?
'Off course we dont get radio, but how many of us actually use it
Oh, and BTW, i am not a developer... More of a dummy
Click to expand...
Click to collapse
+1
because there will be lot more of rom choices then
Sorry but what's code for g2x i mean alike p990
Sent from my LG-P990 using Tapatalk
spica1234 said:
Sorry but what's code for g2x i mean alike p990
Sent from my LG-P990 using Tapatalk
Click to expand...
Click to collapse
P999 i think.
Sent from my LG-P990 using Tapatalk
Yeah it's the P999 for the G2X and WIND Mobile O2X.
Ok thank you
Sent from my LG-P990 using Tapatalk
I have made a 2.3.4 rom for the G2X (based on an unreleased LG-L95G device) and planning on porting your new Italian rom to the G2X. If the flash is CWM compatible you don't have to worry about partitions as you only flash the system image and maybe a compatible kernel. The updater script just tells CWM to mount the system parition (the kernel knows which one) and you copy the files to the system. The kernel (at least for the G2X) is just a file called boot.img and you tell CWM to flash the boot image in a similar manner. I think it is just a matter of replacing the RIL files with the correct ones so the rom can talk to the radio, and swapping out drivers for other differences in the hardware. Other than the radio, as far as i can tell, the phones have virtually identical hardware. I think it would be a good project for someone and not that hard to port one of our G2X roms to your O2X devices.
jboxer said:
I have made a 2.3.4 rom for the G2X (based on an unreleased LG-L95G device) and planning on porting your new Italian rom to the G2X. If the flash is CWM compatible you don't have to worry about partitions as you only flash the system image and maybe a compatible kernel. The updater script just tells CWM to mount the system parition (the kernel knows which one) and you copy the files to the system. The kernel (at least for the G2X) is just a file called boot.img and you tell CWM to flash the boot image in a similar manner. I think it is just a matter of replacing the RIL files with the correct ones so the rom can talk to the radio, and swapping out drivers for other differences in the hardware. Other than the radio, as far as i can tell, the phones have virtually identical hardware. I think it would be a good project for someone and not that hard to port one of our G2X roms to your O2X devices.
Click to expand...
Click to collapse
Sounds good actually.
After you port the italian ROM to the G2X, tell us the difficulty and if you encountered any issues.
So, you are saying that a swap in radiodrivers and a modification to the updater script is all that is too it?
Balano said:
Sounds good actually.
After you port the italian ROM to the G2X, tell us the difficulty and if you encountered any issues.
So, you are saying that a swap in radiodrivers and a modification to the updater script is all that is too it?
Click to expand...
Click to collapse
That plus other stuff. The thing that is concerning me is that in the installer script for the P990 rom there is a volume called "dbdata" being mounted. We don't have a mount called this on the P999, so I need to know what this is used for. Maybe we have something similar but has a different name. I need someone who is knowledgeable about the P990 roms to tell me what this volume is used for. But the thing that makes no sense is that the installer script is simply mounting it, doing nothing with it and then accounting it, so maybe it's a non-issue. The rom itself looks surprisingly similar to the one for the L95G with the exception of the UI customizations. I really think the only difference between the two devices is the radio chip because TMO wanted faster 3G (21Mbps vs 7.2Mbps). I don't know why memory is partitioned differently but that should not be an issue for putting the rom together, as the kernel takes care of all that. We have to hope that everything works using the kernel from the L95G. Due to partitioning differences using the P990 kernel is not an option.
There is nothing on the O2X that corresponds to "dbdata" and it certainly can't be mounted in recovery as there is no entry for it in recovery.fstab
Hi Guys,
Is it possible to Run Boot2Gecko on Galaxy S I9000 like with Galaxy S II? ---> Article - http://www.xda-developers.com/developments/mozillas-boot-to-gecko-running-on-a-samsung-galaxy-sii/
Because I am very satisfied with S I9000 and I haven't got enough for S II.
So do Anyone know howto from SII Update.zip to S Update.zip convert?
Would like to try it too .
useful links
Hi Guys,
I've got some Links for People, which are interested like Trojan38
For Developers ---> https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko/Building_B2G_for_Samsung_Galaxy_S2 (This Tutorial is for I9100)
Official Wiki ---> https://wiki.mozilla.org/B2G
I am not clever enough to Understand the Developer's Tutorial, maybe it can be useful for other Guys
____
Yeah! Sounds interesting .
I will a Mozilla OS
that all sound really Great
so I have just to Say "D'accord avec mon ami Trojan38 "
I am either just a noob
I actually also wanted to make a topic about porting boot2gecko (for i9001).
Actually I think it could be done for sure, the original build is at SGS2, which has the same cpu category as the i9000 and i9001 (armeabi-v7a/armeabi)
Also the resolution is HDPI 480x800 which is also fortunate.
I've downloaded the SGS2 version and extracted it, any it's clearly built on the AOSP environment, actually it looks just like a copy of a AOSP GB rom with an other framework then usual. This is why I think we could actually succesfully port it.
I'm kinda afraid to try it tho, since I have zero knowledge about making kernels so i couldn't produce a working kernel, also I find it rather spooky that dalvik will be deleted.
@poster: it's really more then just converting the "update.zip" which is actually an odin image.
I think we have a pretty high change on succeeding when we just port it like we normally do, my concerns are the kernel tho. Really don't know how to fix that
Hello!
Firstawful sorry that im posting in the I9000 Q&A Forum (I'm coming from the I9001)
So my first question was: "Why aren't the sgs roms working on the sgs+ ??? "
Then i thought that's because of the different Hardware...
And now the big question is: "Would the i9000 roms work on the I9001, if I take a I9001 Kernel???
If not, why?
Would be happy if there will be some answers
Thanks in advance
android_smiley
Difference in libs framework and some drivers
Not only kernel can handle hardware changes
Sent from my GT-i9000 using xda premium
The first problem is the SoC which is different, but with a right kernel you should have not big problems.
The second problem are the components used. Since the 2 phones are from 2 different periods, they have different chips (Radio, GPU, sensors, camera, etc), so you need to replace / rebuild the libs and drivers for each different device you have in 9001 and not in 9000.
I never built a rom or kernel, but it seams better to start from 9001 source than modify a 9000 rom source :cyclops: