[Q] Difference between CDMA ROMs and GMS ROMs - HTC EVO 3D

Can someone tell me what´s the difference between CDMA ROMs and GMS ROMs. I have GSM Evo 3D. For CDMA there are many of ROMs but for GSM not. Why CDMA has a lot of possibilities like overclocking etc. and GSM not?

There are more CDMA roms simply because more people own a CDMA version, thus more people will develop roms for the CDMA version.
But the GSM version is getting some good attention lately, with a lot of new roms being developed at the moment.
You can overclock the CDMA version because HTC released the source code for the kernel.
They have not yet released the GSM kernel source code, so the GSM version can not yet be overclocked.
There are many differences between CDMA and GSM roms, so it requires quite a bit of work to port from one side to another.

Thanks
Thank you very much for explanation

Moonbloom said:
There are more CDMA roms simply because more people own a CDMA version, thus more people will develop roms for the CDMA version.
But the GSM version is getting some good attention lately, with a lot of new roms being developed at the moment.
You can overclock the CDMA version because HTC released the source code for the kernel.
They have not yet released the GSM kernel source code, so the GSM version can not yet be overclocked.
There are many differences between CDMA and GSM roms, so it requires quite a bit of work to port from one side to another.
Click to expand...
Click to collapse
Can't I port cdma ROM to my gsm EVO 3d and after that install gsm kernel and network drivers separately, there will be any problems?

darkblooded said:
Can't I port cdma ROM to my gsm EVO 3d and after that install gsm kernel and network drivers separately, there will be any problems?
Click to expand...
Click to collapse
Interesting concept .. Android is more similar to Linux than to windows in the sense that drivers are really just loaded up as needed but more so compiled into the kernel, although perhaps loaded through modules ..
Either way, the Android framework itself seems to be geared specifically on each device to support a certain type of radio, at least from what I've seen developers post. I.e. Android is either programmed/setup to expect and communicate with a CDMA radio or a GSM radio.
Of course, this could definitely appear as a short coming for anybody wishing to swap ROMs on the fly. I would hope, in the future, a ROM could provide dual support for both CDMA/GSM along with the kernel also providing dual support.
Although, on the contrary most people don't own a CDMA and a GSM version of the same device so they wouldn't be swapping their ROMs back and forth very often.
Hopefully some of that information is helpful!

Related

[Q] Beats Audio on Non Beats Rom for GSM

Hi developers, I was wondering if anyone has the skill and free time to port this mod: http://forum.xda-developers.com/showthread.php?t=1308993
to the GSM evo 3d. i am aware that there are gsm roms with beats already incorporated however my phone came with a newer ruu (1.22.707.2)and crypt0`s rom is the only rom supported. i know this is possible because people have already started porting CDMA roms to GSM. Thanks in advance

[Q] Porting an Inspire ROM to the Rezound

Can anyone port this ROM or if it's simple help me do it?
http://forum.xda-developers.com/showthread.php?t=1383258
Unfortunately porting a ROM is not as easy as swapping a few files.
allchannels99 said:
Can anyone port this ROM or if it's simple help me do it?
http://forum.xda-developers.com/showthread.php?t=1383258
Click to expand...
Click to collapse
1) wrong resolution....inspire/dhd are wvga screens (if it was bigger you could typically resize down with m10 tools...not gonna really work the other way)
2) lte...as witnessed by the thunderbolt porting is significantly more difficult to an lte device from a non lte rom...data is often a no-go (especially for sense 3.5 +)...really erishasnobattery was about the only person capable of it and he no longer has a rezound....as more lte phones on other carriers with similar resolutions come out, porting may become easier/more prevalent
3) its never "simple" unless porting from a nearly identical device ie: inspire - dhd - desire s or og inc - evo 4g (or inc2 to inc s to an extent by gsm to cdma involves a few more files than gsm to gsm)
4) since thats an aosp rom, it could be built on a stable base for this phone...but afaik that doesnt exist atm...
nitsuj17 said:
1) wrong resolution....inspire/dhd are wvga screens (if it was bigger you could typically resize down with m10 tools...not gonna really work the other way)
2) lte...as witnessed by the thunderbolt porting is significantly more difficult to an lte device from a non lte rom...data is often a no-go (especially for sense 3.5 +)...really erishasnobattery was about the only person capable of it and he no longer has a rezound....as more lte phones on other carriers with similar resolutions come out, porting may become easier/more prevalent
3) its never "simple" unless porting from a nearly identical device ie: inspire - dhd - desire s or og inc - evo 4g (or inc2 to inc s to an extent by gsm to cdma involves a few more files than gsm to gsm)
4) since thats an aosp rom, it could be built on a stable base for this phone...but afaik that doesnt exist atm...
Click to expand...
Click to collapse
Hey man!, do you have a Rezound??
also I know this may sound weird, but what about the Thunderbolt sense 3.0 leak ROMS, could that be ported to the Rezound?
andybones said:
Hey man!, do you have a Rezound??
also I know this may sound weird, but what about the Thunderbolt sense 3.0 leak ROMS, could that be ported to the Rezound?
Click to expand...
Click to collapse
nope, no rezound...was just passing through and thought id answer
tbolt is still wvga so it would look awful (though id think radio/data stuff would be alright)

[Q] Question about kernels

So my current understanding is that a kernel is essentially the software that connects android with the hardware of the phone. Somewhat of a driver in terms of Windows?
Now I understand that different versions of Android will require different kernels even if the phone is the same (is this true?). For instance ICS for say... Phone X will have a kernel of X.Y.Z while Gingerbread for Phone X will be A.B.C.
Now would the kernel be the same for say gingerbread 2.3.3 and 2.3.5 and 2.3.7?
Also... Would it be possible to take a "shotgun" approach so to speak with the kernels for the Android phones?
For instance write one kernel that covers all android phones. The kernel file itself would be HUGE, but would it be possible or is there too much variation within the hardware. I know a lot of people are currently waiting for the HTC Desire HD's ICS rom to be released by HTC in order to get that ICS Kernel Source code.
The reason I ask is because having one universal kernel could potentially solve a lot of problems especially for the less popular phones. With this combined with the Easy Development Studio (being developed: http://forum.xda-developers.com/showthread.php?t=1446233) this could be pretty beneficial in my opinion at least.
I'm not a programmer and recently got into Android so that's why I'm asking. I just figured ask and learn more. So any opinions and even teachings that you have that you guys are willing to share with me would be awesome.
I think there is to many problems with writing kernel for all hardware... This is just linux kernel compiled for Android platform... Linux kernel is free but hardware specification not always free, there is already two different ways to write code for this hardware:
1. Write some code which would works on your device (but it does not mean that it would works on all devices which the same model).
2. Or you can go to hardware manufacturer and tell something like 'Hi guys, could you give me specifications of Phone X?' - (as i know it is commercical secret...maybe i am mistaken here)
Linux kernel (~Android kernel) is commonly support a lot of devices (include TV, Routers etc), but i think that enhance code of this kernel for each group device or for each manufacturer it is only one way to get stable and fast work with your gadget...
wlfpck said:
So my current understanding is that a kernel is essentially the software that connects android with the hardware of the phone. Somewhat of a driver in terms of Windows?
Now I understand that different versions of Android will require different kernels even if the phone is the same (is this true?). For instance ICS for say... Phone X will have a kernel of X.Y.Z while Gingerbread for Phone X will be A.B.C.
Now would the kernel be the same for say gingerbread 2.3.3 and 2.3.5 and 2.3.7?
Also... Would it be possible to take a "shotgun" approach so to speak with the kernels for the Android phones?
For instance write one kernel that covers all android phones. The kernel file itself would be HUGE, but would it be possible or is there too much variation within the hardware. I know a lot of people are currently waiting for the HTC Desire HD's ICS rom to be released by HTC in order to get that ICS Kernel Source code.
The reason I ask is because having one universal kernel could potentially solve a lot of problems especially for the less popular phones. With this combined with the Easy Development Studio (being developed: http://forum.xda-developers.com/showthread.php?t=1446233) this could be pretty beneficial in my opinion at least.
I'm not a programmer and recently got into Android so that's why I'm asking. I just figured ask and learn more. So any opinions and even teachings that you have that you guys are willing to share with me would be awesome.
Click to expand...
Click to collapse
"Now I understand that different versions of Android will require different kernels even if the phone is the same (is this true?). For instance ICS for say... Phone X will have a kernel of X.Y.Z while Gingerbread for Phone X will be A.B.C"
The kernel is basically a collection of device drivers and services which needs to be loaded to work as a mediator between the OS (ROM) and the phone hardware and it is off course device specific. And kernel does not depend on ROM rather ROM depends on kernel. The different kernel available for same device will have almost same structure excepts some specific drivers and services may be different . Same kernel may work with different roms if the rom is ported to or complied to work with that kernel. So even a GB kernel may work in ICS.
hm... I see.
I guess then that leads to another question of...
What about a universal kernel for each phone manufacturer? I believe that there is a way to find out the specific hardware within a phone. If that's the case, targeting just HTC or just Samsung, could allow for the shotgun approach to work since the overall target is smaller.
Wouldn't it also be possible to say to take a HTC Inspire 4G existing kernel and the rest of HTC's existing phones and consolidate the kernels?
I'm not a programmer so I'm just trying to learn but maybe I am over simplifying things.
@sos1g3: I see what you are saying as well but couldn't the hardware specifications be obtained from the existing kernels?
wlfpck said:
hm... I see.
I guess then that leads to another question of...
What about a universal kernel for each phone manufacturer? I believe that there is a way to find out the specific hardware within a phone. If that's the case, targeting just HTC or just Samsung, could allow for the shotgun approach to work since the overall target is smaller.
Wouldn't it also be possible to say to take a HTC Inspire 4G existing kernel and the rest of HTC's existing phones and consolidate the kernels?
I'm not a programmer so I'm just trying to learn but maybe I am over simplifying things.
@sos1g3: I see what you are saying as well but couldn't the hardware specifications be obtained from the existing kernels?
Click to expand...
Click to collapse
"Wouldn't it also be possible to say to take a HTC Inspire 4G existing kernel and the rest of HTC's existing phones and consolidate the kernels?"
Not exactly, it is only possible if the hardware is same . But off course a part of it will be same.
hardware specification can be obtained from a kernel source only . Not from the compiled kernel.
musarraf172 said:
"Wouldn't it also be possible to say to take a HTC Inspire 4G existing kernel and the rest of HTC's existing phones and consolidate the kernels?"
Not exactly, it is only possible if the hardware is same . But off course a part of it will be same.
hardware specification can be obtained from a kernel source only . Not from the compiled kernel.
Click to expand...
Click to collapse
If I am not mistaken, HTC and Samsung provide their source codes for their kernels.
"Not exactly, it is only possible if the hardware is same . But off course a part of it will be same. "
So then it's not possible to create a kernel that covers say a Snapdragon processor and a Nvidia Tegra 2?
I really wish the android world was more consolidated... of course that wouldn't do well for the phone manufacturers.
wlfpck said:
If I am not mistaken, HTC and Samsung provide their source codes for their kernels.
"Not exactly, it is only possible if the hardware is same . But off course a part of it will be same. "
So then it's not possible to create a kernel that covers say a Snapdragon processor and a Nvidia Tegra 2?
I really wish the android world was more consolidated... of course that wouldn't do well for the phone manufacturers.
Click to expand...
Click to collapse
Well , to make it more clear you should know that a full linux kernel ( desktp / server ) does have support for different hardware, peripherals, gpu etc, even for different cpu. Only limitation is that the processor architecture should be same i.e various x86 processor can be supported by a single kernel but a single kernel will not support both x86 , x64 or ppc , ARM architecture . (By the word architecture I mean the instruction sets on which they work). It is called a generic kernel.But for mobile devices the kernel is trimmed down to the specific set of hardwares and peripherals because of resource limitations. A full generic kernel will size will be much bigger approx 80 to 120 MB. But a kernel for mobile device is arround 5 to 6 MB. So make an universal kernel for all mobiles , the size will be bigger which won't fit in the current device setup. So theoretically we can write a kernel which will support both Snapdragon processor and Nvidia Tegra 2 as they both uses ARMv7 instruction set.

I have to ask

Hi 2all guys in here i have to ask why there is no miui developmenting
after the new source code of 4.0.3 released
and we have already cm9 with working cam why this is not ( http://forum.xda-developers.com/showthread.php?t=1679727 ) in progress just asking not barking or anything else
thnx anyway
about gsm
I'm curious about it too. Maybe is hard to make stable build for shooter_u. You know. because of 3D, two cameras on back etc... Unfortunatelly back cameras for Evo aren't the same in all models. CDMA version has 5+2, GSM 5+5,...
BTW I can recomend you to look at this thread
http://forum.xda-developers.com/showthread.php?t=1551746
Kali (one of CyanogenMod developers) and agrabren are hardly working on stable build of CM9 for shooter_u and it looks, that Evo can be officialy supported by CM team.
There is on the CDMA side: http://forum.xda-developers.com/showthread.php?p=24187418
Sent from my ICS 3VO with Tapatalk 2

Been wondering this for a while.....

Please help me to understand this..........
If android runs on top of lunix
and all android versions eclair gb, ics etc start off as basically aosp then get maufacturer specific things like blur and sense.
Why is it so hard for CM9 and 10 to fully work on the E3D when CM7 worked perfectly on the Evo4g which are both htc phones?
Its a random question and even though I just recently became a member here, ive been with XDA since i hade the original moto click which was 2 yrs ago.
Also,
What do I need to do to create themes? Ive been wanting to for a while.
Thx in advance
Deep breath. It basically comes down to the huge variety of hardware. Linux has to support hardware in it's kernel (basically a software layer that tells the operating system how to use that hardware) and each new variant of the kernel is supposed to be backward compatible (though support for very old hardware is dropped so the kernel doesn't get out of control). Now Android is a completely different branch of linux (at the moment), and each manufacturer further branches aosp and creates a different kernel for every mobile phone with different hardware. The manufacturers have to release the kernel back to the community after they upgrade but this is slow and even when they do the kernel only supports the variant of android (in this case sense). Finally if they don't release an OS upgrade at all then the kernel becomes outdated and won't support features in the new OS.
Devs feel free to correct me...
Sent from my Evo 3D GSM using xda app-developers app
CM7 is by now quite old, meaning developers have had A LOT of time to test, modify, run and perfect it, even several years ago a lot of phones had perfect CM7 ports/builds.
Both CM9 and CM10 are still quite new, and thus developers have not had that much time to modify it to run as well as CM7, but in time it'll get there, no doubt about it.
And it also depends on which developers are actively working on developing for a specific phone. As for example we now have Agrabren working on a CM10 build (GSM side) doing amazing work, while other phones do not have such developers, thus it will take longer time for those phones to get perfected.
As for the themes, it depends on what ROM you're using. There are several different ways to theme something, and they're very different if you're running either Sense 3, Sense 3.6, Sense 4, CM7, CM9, CM10 or MIUI 2.3 or MIUI 4 (etc.), so you'll have to be more specific. But it would be a good start to look in the "Themes and Apps" sub forum.
grrratt said:
Deep breath. It basically comes down to the huge variety of hardware. Linux has to support hardware in it's kernel (basically a software layer that tells the operating system how to use that hardware) and each new variant of the kernel is supposed to be backward compatible (though support for very old hardware is dropped so the kernel doesn't get out of control). Now Android is a completely different branch of linux (at the moment), and each manufacturer further branches aosp and creates a different kernel for every mobile phone with different hardware. The manufacturers have to release the kernel back to the community after they upgrade but this is slow and even when they do the kernel only supports the variant of android (in this case sense). Finally if they don't release an OS upgrade at all then the kernel becomes outdated and won't support features in the new OS.
Devs feel free to correct me...
Sent from my Evo 3D GSM using xda app-developers app
Click to expand...
Click to collapse
Moonbloom said:
CM7 is by now quite old, meaning developers have had A LOT of time to test, modify, run and perfect it, even several years ago a lot of phones had perfect CM7 ports/builds.
Both CM9 and CM10 are still quite new, and thus developers have not had that much time to modify it to run as well as CM7, but in time it'll get there, no doubt about it.
And it also depends on which developers are actively working on developing for a specific phone. As for example we now have Agrabren working on a CM10 build (GSM side) doing amazing work, while other phones do not have such developers, thus it will take longer time for those phones to get perfected.
As for the themes, it depends on what ROM you're using. There are several different ways to theme something, and they're very different if you're running either Sense 3, Sense 3.6, Sense 4, CM7, CM9, CM10 or MIUI 2.3 or MIUI 4 (etc.), so you'll have to be more specific. But it would be a good start to look in the "Themes and Apps" sub forum.
Click to expand...
Click to collapse
Hey thx guys, I got a better understanding now. I appreciate you taking the time to explain that to me.
As far as themes, i will look into that thread.
BTW this site is awesome. You guys have done a great job making all of this accessible for people who refuse to hampered by the limits of a locked s-on phone.

Categories

Resources