Related
I already posted this in the Nexus dev forum, and I hate to clutter the boards, but I know that there are a bunch of talented devs here that may not see it on those forums. If we can bust the 30fps cap for good, and get the GPU overclocked, then we could see some serious gaming performance out of our Snapdragon devices.
I'm sure we all heard about being able to overclock the GPU on some of the old MSM devices, but the Snapdragon handles the graphics chip in a different way. The goal of this thread is to try and overclock the GPU on Snapdragon devices as well.
There is nothing GPU related in acpuclock-scorpion.c (the Snapdragon cpu clock settings) at least for setting gpu clock speed as far as I can tell.
In board-mahimahi.c (Nexus board file) and board-supersonic.c (Evo board file) there is some kgsl init code, but so far as I can tell it isn't setting the clock there, instead it seems to be pointing to PWR_RAIL_GRP_CLK to set the clock in both devices. It defines the variable in each of those files but I'm not sure where that variable is set, since it doesn't seem to be in any of the other board files as far as I can tell. I could be completely off here too though.
In drivers/video/msm/gpu/kgsl/kgsl.c there is a method called kgsl_clk_enable that seems to be called whenever the GPU is enabled. It looks like this:
Code:
/* the hw and clk enable/disable funcs must be either called from softirq or
* with mutex held */
static void kgsl_clk_enable(void)
{
//clk_set_rate(kgsl_driver.ebi1_clk, 128000000);
clk_set_rate(kgsl_driver.ebi1_clk, 245000000); // Looks like it sets the GPU clock, right? Wrong.
clk_enable(kgsl_driver.imem_clk); // Enable the clock
clk_enable(kgsl_driver.grp_clk); // Enable another clock, but why?
}
The line that's been commented out is the original value, I replaced it with my value on the line below it in a failed attempt to overclock it. Probably a stupid effort on my part, I doubt it's that simple, but it was worth a shot. The comments at the end of the line are also my additions.
According to the clk.h files in the standard linux kernel, clk_set_rate is obviously a method to set the clock rate. The first variable is a struct that tells it which clock to set, and the second variable is a long value that is the rate you want it set at. Is it setting the right clock there for Snapdragon chips? Or is it only the clock for older chips?
I'm in way over my head with this source, I'm but a lowly Java dev, but I really wanna solve this. Can anyone with a little more experience than me throw in a little more info? Sorry if it doesn't make much sense, if it isn't clear just ask me & I'll try to explain a little more.
Regards,
Jesse C.
EDIT: Okay I did a little more digging and those kgsl settings should work for QSD8x50 chips. In the config file, under Drivers, Graphics Support, it allows you to enable 3D accelleration for QSD8x50 & MSM7x27 chips. The tag for that is CONFIG_MSM_KGSL_MMU. If you check in kgsl.c it checks to see if that is enabled in the config, and if it is then it compiles and uses kgsl.c & all of the kgsl code. That tells me that the clock is either not being set, or the wrong clock is being set. I'm adding some debug code right now so I can see in dmesg what code is actually being run.
Dude I have no idea how to do this but bump and best of luck
Sent from my PC36100 using XDA App
Isn't this Helping ? http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=blobdiff;f=arch/arm/mach-msm/clock-7x00.c;h=ef178abfcd46cf78dd47962d75298691f887ebf2;hp=d68fea09d1996daeff99365ced9785d65b1cb001;hb=23ff83048726252bc785699fc749a3e364a3bdb0;hpb=110e73c591db3fd23d8558659f8a6a0dfe5ba912
It looks like here he sets the clock writel(grp,MSM_CLK_CTL_BASE+0x84); 0x84
And here is the Orginal topic http://forum.xda-developers.com/showthread.php?t=697673..
fstluxe said:
Isn't this Helping ? http://androidhtc.git.sourceforge.net/git/gitweb.cgi?p=androidhtc/kernel.git;a=blobdiff;f=arch/arm/mach-msm/clock-7x00.c;h=ef178abfcd46cf78dd47962d75298691f887ebf2;hp=d68fea09d1996daeff99365ced9785d65b1cb001;hb=23ff83048726252bc785699fc749a3e364a3bdb0;hpb=110e73c591db3fd23d8558659f8a6a0dfe5ba912
It looks like here he sets the clock writel(grp,MSM_CLK_CTL_BASE+0x84); 0x84
And here is the Orginal topic http://forum.xda-developers.com/showthread.php?t=697673..
Click to expand...
Click to collapse
Yeah I saw that, but that won't work for us, because it is for one of the old MSM7500 chips instead of the new QSD chips we have in Snapdragon devices.
I am working on a few things now and I recommend you check the Nexus forum since that thread is a lot more active.
Geniusdog254 said:
Yeah I saw that, but that won't work for us, because it is for one of the old MSM7500 chips instead of the new QSD chips we have in Snapdragon devices.
I am working on a few things now and I recommend you check the Nexus forum since that thread is a lot more active.
Click to expand...
Click to collapse
okey, But as far as I know that code is not standard... Becouse the Vugue msm7500 device is originally WM device.. so the Smart dzo managed this custom code.
I wil follow the nexus form .. This is Damn interesting !
i wish you guys the best of luck..wish i could help..i love xda..lol
I'm going to bump this, would be nice if more people were working on this.
Man... I absolutely love my phone. It really sux that this even needs to be asked. This device is so much more capable and I cannot understand why HTC would cripple it so badly. Look at the Samsung galaxy s or the Droid x. Or even a more similar phone like the nexus or incredible. They all stomp this phone when it comes to anything graphics wise even if it is just swiping home screens. It makes me sad. Lol
I love how it makes you sad, but you still lol. Lol (correctly placed)
This is big but first let's get a true cap fix!
Sent from my Evo 4G
How is there such little interest in this subject? This intergrated gpu will probably overclock like a beast... and maybe we can get actual fps.
jigglywiggly said:
How is there such little interest in this subject? This intergrated gpu will probably overclock like a beast... and maybe we can get actual fps.
Click to expand...
Click to collapse
I'm thinking this is also one of those things awaiting source. Even the overclocked kernals make my phone reset so I'm waiting for a more stable release myself. Since you're still posting here does that mean you decided to keep your evo?
psych2l said:
I'm thinking this is also one of those things awaiting source. Even the overclocked kernals make my phone reset so I'm waiting for a more stable release myself. Since you're still posting here does that mean you decided to keep your evo?
Click to expand...
Click to collapse
I don't know, yet I am in deep havoc lol. I activated my phone on the 20th. I have till 13th of July to pay my bill, so don't know.
I mean the locked bootloader of the Droid X is kind of lame. Also on the Evo, I have a 10$ discount because of the IO conference... unlimited texts too, and I bought two batteries for it with a charger(for 10$ lol, and they actually last a long time 1500ma, I put the 2 extras in my wallet)
Also I think I can upgrade my phone right away already if I read things right, so if Sprint gets an awesome phone I can upgrade to that whenever.
Verizon is more expensive, but I like how they let me do a 1 year contract. The Droid X is also nicer, I mean it has a better camera, and the mic quality when taking videos isn't piss, hopefully someone fixes that. It also has a real graphics card.
So yeah, it's hard to decide. A better phone, vs saving me some money. Though I plan to attend the IO conference once again. I'm still porting my distrubuted prime client onto Android, hopefully it will be high performance. So it's not like I just go there for a phone ^^. Hell I didn't even know about the phones till they said "Where do you want the Droid delivered" I lol'd. Though my time is limited, summer classes at UC Berkeley are tough : /
jigglywiggly said:
How is there such little interest in this subject? This intergrated gpu will probably overclock like a beast... and maybe we can get actual fps.
Click to expand...
Click to collapse
Yep, looks like til we get the kernel in our hands they're tied.
Also what's the point of overclocking if their is still a limit on FPS..
Eventually this will be the next thing on our todo list
some of the source for the OpenGL ES GPU core was announced as being released today
Qualcomm releases open-source 3D Snapdragon driver
http://www.androidcentral.com/qualcomm-releases-open-source-3d-snapdragon-driver
havent looked at it yet, but im sure in the very least this should at least help shed some more light on overclocking the GPU and add another piece to the puzzle!
git location -
https://www.codeaurora.org/gitweb/q...b819424af4be;hb=refs/heads/android-msm-2.6.32
topdnbass said:
Yep, looks like til we get the kernel in our hands they're tied.
Also what's the point of overclocking if their is still a limit on FPS..
Eventually this will be the next thing on our todo list
Click to expand...
Click to collapse
There isn't really a fps cap with the novatek kernel hack. It made the display much smoother for me and I am using it on EvolutionX. So beast.
Good news about the drivers, maybe we can actually see some overclocking now.
I want this to happen!
Nova runs pretty well on the Evo. Gameloft updated it recently.
I would just like for iphone ports to run well.
I hear the Palm Pixi has the same GPU. It is clocked at 190mhz. What about the Evo?
patelkedar91 said:
I hear the Palm Pixi has the same GPU. It is clocked at 190mhz. What about the Evo?
Click to expand...
Click to collapse
The Pixi doesn't have the same GPU, it has one of the low/mid-range MSM7227 (I think thats the model?) chips. It's similar as it's one of Qualcomms latest gen chips, but it is NOT a Snapdragon so it's different.
Also, the Snapdragon GPU's on HTC devices are clocked as follows:
GRP_CLK: The actual graphics clock, 256mhz
IMEM_CLK: The gpu memory clock, 256mhz
EBI1_CLK: As best I can tell, the bus that the GPU is on is EBI1, this is the clock for it, 128mhz
If you want more info, look here: http://forum.xda-developers.com/showthread.php?t=710850 since that thread is a lot more active, but please don't clutter it, there's actual devving going on there
Thanks for the info. I just wonder how they're going to get 3d games to work on the Pixi then... weird.
It was announced that the Pixi would get 3d gaming with the 1.4.5 update.
Much better (Y)
http://forum.xda-developers.com/and...ck-overclocking-tuning-snapdragon-s1-t2883708
I have to ask: Why does everyone want a dual core phone which cant even currently be used?
I say it cant be used because dual core processors cant be used on Android 2.3 Gingerbread/Linux kernel 2.6.35, there is only multi-core processor support in A3H/L2.6.36 (only avaliable (officially) on tablets). We will see problably support in in "A4I"/"L3.6.37" for both phones and tablets.
So whats everyones obsession? The only thing you are problably gaining is a SLIGHT speed boost (not even close when a kernal that supports it is released) and more battery drain.
On a counterside this could bring good marketing to Google: They release "A4I", current dual core phones get a HUGE speed boost and everyone praises Google. Could work good for them.
Interesting, I never knew Gingerbread couldn't support dual cores on phones. Good info, I guess I'll keep my Evo for another year.
It's pretty easy to compile the kernel to use multi core processors. The current one may not, but hold your judgement until it's actually released.
crazy25000 said:
It's pretty easy to compile the kernel to use multi core processors. The current one may not, but hold your judgement until it's actually released.
Click to expand...
Click to collapse
So true............. Currently 0.0000000000000000000000000000000000000000000001% of users AND developers of applications can and are willing to complie a custom kernel not used by the rest and use/make multi core supported applications with its multi core supported kernel.
I guess progress has to begin somewhere?
i don't think i'll ever need / want a dual core phone for my daily rutine, my SGS is perfect for me, what more could you need from a phone? don't think they'll be able to fit jet packs on them any time soon...
riahc3 said:
So true............. Currently 0.0000000000000000000000000000000000000000000001% of users AND developers of applications can and are willing to complie a custom kernel not used by the rest and use/make multi core supported applications with its multi core supported kernel.
Click to expand...
Click to collapse
What I'm saying is the kernel can easily be compiled by Google or Samsung and used as the stock kernel on the GSII.
maranello69 said:
i don't think i'll ever need / want a dual core phone for my daily rutine, my SGS is perfect for me, what more could you need from a phone? don't think they'll be able to fit jet packs on them any time soon...
Click to expand...
Click to collapse
Yeah its logical to think like that but 3 years ago who thought you need phone with such big screen and processor/RAM almost match PC speed?
As someone said somewhere they have to start but interesting thought by thread creator
ksavai said:
Yeah its logical to think like that but 3 years ago who thought you need phone with such big screen and processor/RAM almost match PC speed?
As someone said somewhere they have to start but interesting thought by thread creator
Click to expand...
Click to collapse
Honestly those arent needs either. But as of right now the only purpose of a dual core phone is to brag.
Ok so please forgive my noobness here but I'm dying to ask a few questions... I have been an android fan for years and always had lots of options for my phones, and now that I am switching phones I would like to help out more. I see that development is going slow on this phone and had a few questions...
What would it take to port over some roms from say the galaxy s (I'm thinking possibly CM7 or MIUI)? What is the closest phone to ours if not the galaxy?
If the kernel is open source (https://opensource.samsung.com) then is over/underclocking possible with much effort?
Is all I need to build a functioning rom available from the android sdk and the samsung open source website? (I understand this is no easy task, just wondering if I need more than this)
FM transmitter... I hear this phone has a FM transmitter, is this true? Oh man what I wouldn't give to get this working. I would love to hear any opinions/suggestions/comments on this subject as this interests me most.
I'm sorry once again for all the questions, I am looking forward to helping out however possible.
I suggest you look up the wiki's on cyanogenmod on building. You'll need some sorta POSIX environment (ie.. linux or OS X). Here's the one I used:
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S_II_(AT%26T):_Compile_CyanogenMod_(Linux)
The SGS family largely uses samsung components (CPU's, GPU's, etc). The Blaze uses the qualcomm snapdragon stuff. The blaze is using the msm8660 arch, which isn't really present in the cm7 sources. The only thing kinda there is the sgs2 for at&t (skyrocket). Finding other examples using similar hardware has not been easy for me. The audio subsystems for sgs2 seems to be yamaha based, where as ours isn't. You'll want to be VERY careful to make sure all the partitions are set up properly in your work as otherwise you may end up wiping the radio or other supporting partitions, and that would be very, very bad. And etc... etc... etc...
It would help to have a working knowledge of unix/linux. You'll definitely want to root your phone (obviously) and install busybox so you have a decent toolset to go poking around the OS.
I wish you luck and I hope this helped!
---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------
Oh, forgot about the Kernel.
The kernel itself is always open source (legally required). The changes and binary blobs for drivers aren't.
You apparently tweak the kernel seperately from a cm7 build. OC and UV are about playing with the timings inside the CPU and is not for the feint of heart. My understanding is that there is a whole series of equations and calculations you use to arrive to the frequency table for such things. Since other hardware uses our CPU, that's probably the place to start looking... i.e... the EVO 3D.
Thanks for quick reply! I currently dual boot ubuntu/win7 and have a small working knowledge of linux, so hopefully that helps there. I will start messing around with the phone in another week or so when my schedule allows, but will gladly help beta test until then! Please feel free to hit me up when you need something tested
Also, since you are the hardware man.... what about that FM transmitter? Is that only a receiver or is it a combo? I personally have never seen a FM transmitter in a phone and would love to have one.
dr4stic said:
The SGS family largely uses samsung components (CPU's, GPU's, etc). The Blaze uses the qualcomm snapdragon stuff. The blaze is using the msm8660 arch, which isn't really present in the cm7 sources. The only thing kinda there is the sgs2 for at&t (skyrocket). Finding other examples using similar hardware has not been easy for me. The audio subsystems for sgs2 seems to be yamaha based, where as ours isn't. You'll want to be VERY careful to make sure all the partitions are set up properly in your work as otherwise you may end up wiping the radio or other supporting partitions, and that would be very, very bad. And etc... etc... etc...
Click to expand...
Click to collapse
As far as being close to the Blaze, what about the Galaxy Note? It has a msm8660 while the Blaze has a msm8260. Both have the adreno 220 gpu, same ram, and release around the same time. I see there is a larger screen and a different camera, is there something we can use there?
I only ask as I ran across this thread: http://forum.xda-developers.com/showthread.php?t=1573568 and was wondering if maybe this phone would be the place to start a port.
Howdy all,
I am a bit new around here but I stay pretty busy on some other forums and I run a site called rockchipfirmare.com. I don't consider myself a developer in the true sense of the word but rather I mix-n-mash roms primarily without getting into too much actual coding.
So I have a question that is slightly out of my league and I am hoping someone with a bit more knowledge can lend a hand.
I have two chipsets in front of me.
One is the Samsung Exynost 4412 (Quad-Core A9 with Mali-400 MP4 gpu)
The other is a Rockchip RK3188 (Quad-Core A9 with Mali-400 MP4 gpu)
Basically, I have noticed that Exynos pretty much runs EVERYTHING just a little bit smoother than the RK3188 does, even though the RK3188 actually does better in most synthetic benchmarks.
I think it -might- be a driver optimization issue as I am sure Samsung does a heck of a lot more with their drivers than Rockhip. I also suspect that the Mali-400 GPU in the RK3188 is running at a lower clock than Rockchip claims. Thus far I haven't found a way to figure out what the GPU specifically is clocked at.
Anyhow, here is my question....
Would it be possible to get the Samsung Mali drivers from the Siyah kernel and import them into the RK3188 kernal for a specific device?
I think I have most of the tools to do so already as I can unpack and repack boot images for the RK3188. Although I never have gotten into the extracted kernel image.
I guess I am asking if I should spend time on the above or whether it is a fools errand and if I do spend time on it what exactly am I looking to get from the SIyah kernel once I get into it?
Any thoughts our help someone would like to throw my way are most welcome.
Kind Regards,
Roman
Would be wonderful if someone can do this
Well, that is what I am try to learn, how to combine different modules drivers.
If the module is compile with the same kernel version (Linux 3.0.36), then maybe it could work.
How is going so far? I really would like to learn about that to be able to recollect all the modules for different RK3188 tablets and the be able to recompile new version of the kernel.
I am going to start playing with a PIPO M6 but any help will be much appreciated.
Note: If the GPU driver are integrated in the kernel I don't know you are going to be able to use them, as you cannot build a complete kernel for your RK8188 tablet.
For mali, the source code is open source and it can be found at http://malideveloper.arm.com/develo...source-mali-gpus-linux-kernel-device-drivers/
So i've got my phone like lets say 5months running thought 30non-caf roms..
But is there any difference at all between caf and non ? and what are the wins and lose against those 2 things ?
can someone explain in a short story ? and how do i flash for example CAF on a non caf phone?
Kcetin20 said:
So i've got my phone like lets say 5months running thought 30non-caf roms..
But is there any difference at all between caf and non ? and what are the wins and lose against those 2 things ?
can someone explain in a short story ? and how do i flash for example CAF on a non caf phone?
Click to expand...
Click to collapse
Bless your heart, I found out what the difference between hammerhead and hammerheadcaf by doing a Google search on my phone. It's something that I was wondering about myself because I had been seeing both the CAF and non-CAF versions of ROMs. If you have CPU-Z installed on your phone, you can find out which version you have when you run it. If you don't have it installed, go to the Google Play Store and get it. Just put CPU-Z in the search field and it should bring it up. It's a free download and a very helpful app to have on your phone. Just a word to the wise, flashing hammerheadcaf ROMs on a hammerhead phone is not a good idea at all unless you want to deal with unexpected issues with your phone.
Hammerhead phones have a Qualcomm processor. Hammerheadcaf phones have a Snapdragon processor.
I hope that I was able to help you out here.
Cindy
Sent from my Nexus 5 using Tapatalk
cindylike24 said:
Bless your heart, I found out what the difference between hammerhead and hammerheadcaf by doing a Google search on my phone. It's something that I was wondering about myself because I had been seeing both the CAF and non-CAF versions of ROMs. If you have CPU-Z installed on your phone, you can find out which version you have when you run it. If you don't have it installed, go to the Google Play Store and get it. Just put CPU-Z in the search field and it should bring it up. It's a free download and a very helpful app to have on your phone. Just a word to the wise, flashing hammerheadcaf ROMs on a hammerhead phone is not a good idea at all unless you want to deal with unexpected issues with your phone.
Hammerhead phones have a Qualcomm processor. Hammerheadcaf phones have a Snapdragon processor.
I hope that I was able to help you out here.
Cindy
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You are annoyingly wrong!!! Snapdragon is the SOC lineup of Qualcomm!
cindylike24 said:
Bless your heart, I found out what the difference between hammerhead and hammerheadcaf by doing a Google search on my phone. It's something that I was wondering about myself because I had been seeing both the CAF and non-CAF versions of ROMs. If you have CPU-Z installed on your phone, you can find out which version you have when you run it. If you don't have it installed, go to the Google Play Store and get it. Just put CPU-Z in the search field and it should bring it up. It's a free download and a very helpful app to have on your phone. Just a word to the wise, flashing hammerheadcaf ROMs on a hammerhead phone is not a good idea at all unless you want to deal with unexpected issues with your phone.
Hammerhead phones have a Qualcomm processor. Hammerheadcaf phones have a Snapdragon processor.
I hope that I was able to help you out here.
Cindy
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I can totally understand that you just wanted to help, but....duuuuuude, I'm so sorry, but do you even google?
To clarify a few things here (and get that topic done): I will try to stay clear and simple (probably even oversimplifying, but whatever)
1. Qualcomm Inc. makes (mobile) processors based on designs by ARM. They have certain lineups, with Snapdragon Processors being their consumer-grade line of mobile processors.
The SoC (system on a chip, meaning CPU, GPU and co-processors being combined on one chip) in the Nexus 5 is a Snapdragon 800. It's got 4 Krait-400 Cores as it's main processing cores (CPU), an Adreno 330 GPU (graphics processor) and a Hexagon DSP (digital signal processor, enables, amongst other things, audio processing from digital to analogue). Furthermore you have things like an ISP (image signal processor) and certain modems, but that's rather unrelevant.
So every single Nexus 5 in the world runs on a Qualcomm Snapdragon 800 processor. No difference.
2. To get to the OP's question:
To explain the difference between CAF and non-CAF, you first have to understand what CAF even means.
CAF stand for Code Aurora Project. It is a consortium which acts as a Linux Foundation Collaborative Project. It has a widespread range of projects, of which Android for MSM being a part of those projects. "MSM" is basically Qualcomms way of labeling it's Snapdragon Processors (the Snapdragon 800 is codenamed MSM8974).
Android for MSM concentrates on bringing enhancements specifically made for Qualcomms Processors to the Linux Kernel. Whenever a manufacturer decides to use a Snapdragon Processor in his Phone/Tablet/Whatever, he forks from the Android Open Source Project and then uses the Code Aurora Forum to get the processor-specific code. So, whenever you have a Qualcomm Snapdragon Processor in you device, it will have at least some parts of code sourced from Android for MSM, and therefore the Code Aurora Forum.
Now, whenever a developer decides to build a ROM for a certain device, he will also fork from the Android Open Source Project. To build a kernel, he will most likely use the kernel source from the manufacturer (if available). As for the Nexus 5, we have AOSP and Google's own kernel source specifically for the Nexus 5. To build it's kernel, Google uses patches from CAF, as they are processor-specific and optimized.
Most ROMs for the Nexus 5 are based on AOSP and Google's kernel source. (A few are based on factory images, but we can neglect that for now).
CAF ROMs however are (mostly) based on the code from CAF. This means it may be better optimized, since the code is very processor-specific, but it's also more on the bleeding-edge-side, since it gets constantly updated (and therefore can contain some bugs here and there). Google only uses parts of it's code from CAF and carefully selects those parts, so it's more on the stable-proofed side.
I hope that kind of answers the question(s) in this thread.
Mods: please close if you think everything is answered and done.
9h0s7 said:
lmfao this thread is pure gold. gotta be trolling
Click to expand...
Click to collapse
I'm definitely not trolling on the forum. I was trying to help the OP out with his question.
milestone2mod said:
I can totally understand that you just wanted to help, but....duuuuuude, I'm so sorry, but do you even google?
To clarify a few things here (and get that topic done): I will try to stay clear and simple (probably even oversimplifying, but whatever)
1. Qualcomm Inc. makes (mobile) processors based on designs by ARM. They have certain lineups, with Snapdragon Processors being their consumer-grade line of mobile processors.
The SoC (system on a chip, meaning CPU, GPU and co-processors being combined on one chip) in the Nexus 5 is a Snapdragon 800. It's got 4 Krait-400 Cores as it's main processing cores (CPU), an Adreno 330 GPU (graphics processor) and a Hexagon DSP (digital signal processor, enables, amongst other things, audio processing from digital to analogue). Furthermore you have things like an ISP (image signal processor) and certain modems, but that's rather unrelevant.
So every single Nexus 5 in the world runs on a Qualcomm Snapdragon 800 processor. No difference.
2. To get to the OP's question:
To explain the difference between CAF and non-CAF, you first have to understand what CAF even means.
CAF stand for Code Aurora Project. It is a consortium which acts as a Linux Foundation Collaborative Project. It has a widespread range of projects, of which Android for MSM being a part of those projects. "MSM" is basically Qualcomms way of labeling it's Snapdragon Processors (the Snapdragon 800 is codenamed MSM8974).
Android for MSM concentrates on bringing enhancements specifically made for Qualcomms Processors to the Linux Kernel. Whenever a manufacturer decides to use a Snapdragon Processor in his Phone/Tablet/Whatever, he forks from the Android Open Source Project and then uses the Code Aurora Forum to get the processor-specific code. So, whenever you have a Qualcomm Snapdragon Processor in you device, it will have at least some parts of code sourced from Android for MSM, and therefore the Code Aurora Forum.
Now, whenever a developer decides to build a ROM for a certain device, he will also fork from the Android Open Source Project. To build a kernel, he will most likely use the kernel source from the manufacturer (if available). As for the Nexus 5, we have AOSP and Google's own kernel source specifically for the Nexus 5. To build it's kernel, Google uses patches from CAF, as they are processor-specific and optimized.
Most ROMs for the Nexus 5 are based on AOSP and Google's kernel source. (A few are based on factory images, but we can neglect that for now).
CAF ROMs however are (mostly) based on the code from CAF. This means it may be better optimized, since the code is very processor-specific, but it's also more on the bleeding-edge-side, since it gets constantly updated (and therefore can contain some bugs here and there). Google only uses parts of it's code from CAF and carefully selects those parts, so it's more on the stable-proofed side.
I hope that kind of answers the question(s) in this thread.
Mods: please close if you think everything is answered and done.
Click to expand...
Click to collapse
I'm a lady not a dude here. Yes I did use Google to try and answer the OP's question. I just didn't want to go into the detail that you went into in your post. I was trying to keep it as simple and to the point as I possibly could. Thank you for going into detail on this. Maybe someone will glean something useful out of this in the future.
Mods: Please close this thread if you feel like everything has been answered for this OP.
I've read, that CAF means that this special hammerhead is a chinese clone of the original LG hammerhead. So NEVER flash a hammerheadcaf-rom an a hammerhead-device or vice versa - it could brick your device totally.
But how to find out if i have an original hammerhead or just a chinese hammerheadcaf? What if i accidently flash the wrong rom? I'm scared of what i just found out!!
lol
cindylike24 said:
I'm definitely not trolling on the forum. I was trying to help the OP out with his question.
I'm a lady not a dude here. Yes I did use Google to try and answer the OP's question. I just didn't want to go into the detail that you went into in your post. I was trying to keep it as simple and to the point as I possibly could. Thank you for going into detail on this. Maybe someone will glean something useful out of this in the future.
Mods: Please close this thread if you feel like everything has been answered for this OP.
Click to expand...
Click to collapse
I'm sorry, didn't want to offend you
But, and again, I'm really sorry, but your statement was just completely wrong:
. Just a word to the wise, flashing hammerheadcaf ROMs on a hammerhead phone is not a good idea at all unless you want to deal with unexpected issues with your phone.
Hammerhead phones have a Qualcomm processor. Hammerheadcaf phones have a Snapdragon processor.
Click to expand...
Click to collapse
EVERY Nexus 5 is a "hammerhead" device, since hammerhead is just Google's internal codename for this device (such as volantis for Nexus 9 (volantisg for Nexus 9 4G), shamu for Nexus 6, angler for Nexus 6P, bullhead for Nexus 5X and so on...)
So every "hammerhead" phone (read: every Nexus 5) has got a Qualcomm Snapdragon 800 processor. No difference, again.
CyanogenMOD uses hammerhead as their main ROM-branch and hammerheadcaf as the codename for their CAF-based ROM. So whenever you see "hammerheadcaf" it just means that this ROM is based mainly on code from the Code Aurora Forum.
Of course you can flash such a ROM on every Nexus 5, you would just need a CAF-Recovery. So for most people I'd recommend to just stick with "regular" ROMs, if you don't exactly know what you're doing.
I can understand that you wanted to keep it simple, but it wasn't simple, just wrong, I'm afraid. Again, I'm trying not to be rude (and apologies for the dude, mylady). I just don't want false statements floating around here.
---------- Post added at 06:58 PM ---------- Previous post was at 06:56 PM ----------
McFlypants said:
I've read, that CAF means that this special hammerhead is a chinese clone of the original LG hammerhead. So NEVER flash a hammerheadcaf-rom an a hammerhead-device or vice versa - it could brick your device totally.
But how to find out if i have an original hammerhead or just a chinese hammerheadcaf? What if i accidently flash the wrong rom? I'm scared of what i just found out!!
lol
Click to expand...
Click to collapse
Absolutley wrong, my friend. EVERY Nexus 5 is a "hammerhead". Read my posts above: http://forum.xda-developers.com/showpost.php?p=65995231&postcount=7
There is no special chinese clone of the Nexus 5. Please don't spread false statements.
If CAF roms were for some special clone they would never get posted on the N5 forums of XDA. I live in China and have seen many clones, but none that resemble a nexus 5. The phone is cheap enough no one would bother cloning it. They like to clone samsungs and iphones.
Wowwww. Awesome. Informatie. Lol. I'm just reading this thread with using hammerheads rom. Just felling guilty with Nexus 5.
Thanks. All tacky. Guys. Newer try to use hammerheadcaf. Moving to hammerhead right now ....?????
Sent from my Nexus 5 CAF using XDA-Developers mobile app
milestone2mod said:
1. Qualcomm Inc. makes (mobile) processors based on designs by ARM. They have certain lineups, with Snapdragon Processors being their consumer-grade line of mobile processors.
Click to expand...
Click to collapse
Don't want to Split the hair a lot here. But just to clarify.
Advanced RISC Machine (ARM) is a Architecture for CPUs similar to Intel's P Series Architecture. This is owned by the Corporation of the same name and licensed to All the manufacturers. Qualcomm and Samsung are one of them. Allwinner, RockChip and AMLogic are some of the others based in China.
milestone2mod said:
"MSM" is basically Qualcomms way of labeling it's Snapdragon Processors (the Snapdragon 800 is codenamed MSM8974).
Android for MSM concentrates on bringing enhancements specifically made for Qualcomms Processors to the Linux Kernel. Whenever a manufacturer decides to use a Snapdragon Processor in his Phone/Tablet/Whatever, he forks from the Android Open Source Project and then uses the Code Aurora Forum to get the processor-specific code. So, whenever you have a Qualcomm Snapdragon Processor in you device, it will have at least some parts of code sourced from Android for MSM, and therefore the Code Aurora Forum.
Click to expand...
Click to collapse
Phone Makers tend to use Google's Mainline Kernel from the AOSP Codebase per Agreement. AOSP is a Project sponsored primarily by Google and they do use that for all Nexus platforms. This is a Fork of Linux.
CAF on the other hand, is a Qualcomm's own Fork and is heavily customized with specific Drivers and Middle layer Code that takes advantage of the CPU's features. Of Course this will not work on Non-Qualcomm SoCs.
FOOTNOTE - I have done some light cleaning in this thread. Thread remains open as this legitimate question does baffle many people. And Alas Google isn't good help unless you know what you're looking for. Please don't make personal Attacks. Thank you.
What a load of nonsense about chinese nockoffs?!?!
ROMs for "hammerhead" are AOSP-based
ROMs for "hammerheadcaf" use code specifically optimized for the Nexus 5 SoC from Code Aurora
Perseus said:
Don't want to Split the hair a lot here. But just to clarify.
Advanced RISC Machine (ARM) is a Architecture for CPUs similar to Intel's P Series Architecture. This is owned by the Corporation of the same name and licensed to All the manufacturers. Qualcomm and Samsung are one of them. Allwinner, RockChip and AMLogic are some of the others based in China.
Phone Makers tend to use Google's Mainline Kernel from the AOSP Codebase per Agreement. AOSP is a Project sponsored primarily by Google and they do use that for all Nexus platforms. This is a Fork of Linux.
CAF on the other hand, is a Qualcomm's own Fork and is heavily customized with specific Drivers and Middle layer Code that takes advantage of the CPU's features. Of Course this will not work on Non-Qualcomm SoCs.
FOOTNOTE - I have done some light cleaning in this thread. Thread remains open as this legitimate question does baffle many people. And Alas Google isn't good help unless you know what you're looking for. Please don't make personal Attacks. Thank you.
Click to expand...
Click to collapse
Pretty much Amen.
Perhaps you should do a sticky with all that information (my posts plus your additions) as a go-to source for any interested forum members. This could hold the chance to clarify questions before they're asked (again).
I tested CM14.1 for several days both versions (hammerhead and hammerheadcaf). I didn't notice any difference. Neither in battery life, nor in performance. Am I missing something?
focus-pocus said:
I tested CM14.1 for several days both versions (hammerhead and hammerheadcaf). I didn't notice any difference. Neither in battery life, nor in performance. Am I missing something?
Click to expand...
Click to collapse
How did you switch between the caf- and non-caf version of CM14.1?
From what I've googled and deduced so far, you'd first need to flash the appropriate caf- oder non-caf version of TWRP-recovery, boot into the new recovery and wipe system, data and cache and then flash the matching caf- oder non-caf version of CM14.1. Right?
i have a question on this topic.
so on the security side of things, one of the problems using the nexus 5 with an up to date (security-patched) custom rom is that qualcomm does not update the drivers for their old chips anymore. so even if the open source part (aosp) is patched, there will still be bugs in those proprietary drivers which aren't fixed. does the code aurora project help with this problem?
@ kintrupf -- the newest version of twrp for the nexus 5 supports caf as well as standard roms!
kintrupf said:
How did you switch between the caf- and non-caf version of CM14.1?
From what I've googled and deduced so far, you'd first need to flash the appropriate caf- oder non-caf version of TWRP-recovery, boot into the new recovery and wipe system, data and cache and then flash the matching caf- oder non-caf version of CM14.1. Right?
Click to expand...
Click to collapse
On latest caf builds (any of it) don't need hammerheadcaf TWRP, it installs now normally on hammerhead recovery.
cindylike24 said:
Hammerhead phones have a Qualcomm processor. Hammerheadcaf phones have a Snapdragon processor.
Click to expand...
Click to collapse
I fkined loled hard. Thanks dude. xD
fr3quency said:
I fkined loled hard. Thanks dude. xD
Click to expand...
Click to collapse
I'm a lady not a dude.
Cindy
Sent from my Nexus 5 using XDA Labs
cindylike24 said:
I'm a lady not a dude.
Cindy
Click to expand...
Click to collapse
I think it's cool that you're into this kinda stuff. Hobbies like this are usually sausage parties.
Regardless, like the others have said, Snapdragon is a brand owned by Qualcomm. There are no hammerheadcaf devices, just hammerhead devices. There are, however, hammerheadcaf recoveries, kernels, and ROMs, and then there are regular hammerhead recoveries, kernels, and ROMs. The problem is that is that the parts aren't interchangeable: You need to go everything-CAF or nothing-CAF.
Probably better to just own the mistake, and to ignore that people are speaking to you as if you were a guy (although 'dude' can be a unisex term).
Does no one have a link to a performance test comparing CAF to AOSP? So far, everything I've read has been either subjective or speculative. It's exhausting.