Samsung Galaxy S5 Plus Rom Android 9 - Galaxy S 5 Android Development (Snapdragon)

Samsung Galaxy S5 LTE+, SM-G901F, codename kccat6
this is Mokee rom android 9 Rooted debloated gapps included
MoKee is based on the Android Open Source Project (AOSP). It has additional localised and personalised functionality while preserving the stock Android look by adhering to Material Design guidelines.
Unlike OEMs' slow and untimely updates, we closely follow Google to bring the latest updates to our users, and even prolonging support to devices that have been declared obsolete by OEMs.
Our ROMs' source code is open source, secure, stable and outstanding. Your experience using MoKee will be butter smooth with added convenience.
Hardware Info
CPU: Qualcomm® Snapdragon™ 805
RAM: 3GB
ROM: 32GB and 16GB
Battery: 2800 mAh
Display:: 5.0 inch, 1920x1080 pixel(441ppi)
CPU Arch: arm
all thanks goes to Mokee dev team i just moded it a bit and rooted
Download from:
click thanks if it helps
Mod edit:
Thread closed as placeholder.

Link is missing

Related

[PORTING DISCUSSION] Cherry picks from Exynos based devices on SGS4

Hi,
Everyone is shouting, we will not support Galaxy S4 (I9500) since it is having Exynos which lacks the documentation and sources. Yes, I know that sucks. I would say, we are not really getting super awesome ROMs like CM, MIUI anytime soon. But how if we think differently?
There are many Exynos based devices which have got pretty stable builds of CM and MIUI (e.g. Note 2).. Even Nexus 10 is based on Exynos.
Well, I am not that good but learning to port stuff from here and there.. How if we pick up some of the sources from Exynos devices like Nexus 10, Note 2 etc. and make them work on SGS4?
World will be beautiful again, isn't it?
I might be totally wrong so I expect you to explain stuff rather than ranting over this thread Let's help each other.. What say?
Regards,
Rahul Patil. :good:
It would be incredibly difficult and in my opinion, not worth the effort.
The Nexus 10 utilises Exynos 5250 while the Note 2 uses Exynos 4***(I forgot, 4410,I think), the S4 i9500 uses Exynos 5410 which is different as you can see.
However, some developers will doubtlessly pick up development for the Exynos variant (Faryaab already has an unofficial cm build for the i9500).
For all that effort, cm on the i9500 shall never be as stable and functional as that on the Snapdragon variants.
Well, yes.. Unless and until Samsung releases Exynos documentation and sources. Well, I don't know if there is any chance of getting documents. At least Samsung Exynos replied to one of my tweets regarding releasing sources. They said, they are working on licensing stuff and it should be resolved soon. But you know, their "soon" can be like 2-3 years more too.
warfareonly said:
It would be incredibly difficult and in my opinion, not worth the effort.
The Nexus 10 utilises Exynos 5250 while the Note 2 uses Exynos 4***(I forgot, 4410,I think), the S4 i9500 uses Exynos 5410 which is different as you can see.
However, some developers will doubtlessly pick up development for the Exynos variant (Faryaab already has an unofficial cm build for the i9500).
For all that effort, cm on the i9500 shall never be as stable and functional as that on the Snapdragon variants.
Click to expand...
Click to collapse
Intl GS2 and Note1 are Exynos 4210
Intl GS3 and Note2 are Exynos 4412
Nexus 10 is Exynos 5250 - Mali T604 GPU
I9500 is Exynos 5410 - PowerVR GPU and MANY other differences from the 5250
In short, almost none of the Exynos4 stuff is useful, and most likely neither is most of the Nexus10 stuff
Entropy512 said:
Intl GS2 and Note1 are Exynos 4210
Intl GS3 and Note2 are Exynos 4412
Nexus 10 is Exynos 5250 - Mali T604 GPU
I9500 is Exynos 5410 - PowerVR GPU and MANY other differences from the 5250
In short, almost none of the Exynos4 stuff is useful, and most likely neither is most of the Nexus10 stuff
Click to expand...
Click to collapse
A vast majority of IP blocks are the same as on the 5250 so there is a lot one can pick from there.
Stupid question; weren't most of the CM problems related with the 2D accelerator and not the GPU itself?
@Rahulrulez any status update on the porting?
vinandy said:
@Rahulrulez any status update on the porting?
Click to expand...
Click to collapse
cm team has officially announced that they have started working on cm10.1 for 9500 and they have a device in hand, who is handling the work and when will we see a flashable version in unknown

** Device Comparisons / Discussions / Rumors / News **

Hey Guys,
As @[I][COLOR="Purple"][B]Towle[/B][/COLOR][/I] buddy already mentioned that this thread is meant for Discussion over Comparisons & Rumors for Samsung Galaxy S4 variants & upcoming News.
Please note that we can only discussed about the devices which are going to release/released or not in XDA device list.
For making it quite readable, I will paste the link for the threads, Direct link of News, comparisons & rumors. You can also take part for this thread while pasting links or news in your post.
Upcoming Rumored Devices / News: -​
Samsung Posts GT-i9505G Kernel Source Files – Is This The Google Edition Galaxy S4?
Announcements:​
Samsung officially announces Samsung Galaxy S4 with Snapdragon 800 and LTE-A connectivity
Specifications:​
Samsung Galaxy S4 i9500 Specification - Gsm Arena
Samsung Galaxy S4 i9505 Specification - Gsm Arena
Samsung Galaxy S4 i9502 Specification - Gsm Arena
Samsung Galaxy S4 i9295 aka Active Specification - Gsm Arena
Samsung Galaxy S4 Zoom Specification - Gsm Arena
Samsung Galaxy S4 mini Specification - Gsm Arena
Comparisons:​Samsung I9500 Galaxy S4 vs Samsung I9505 Galaxy S4 - Gsm Arena
Side by Side specifications comparison i9505 vs i9500 - Gsm Arena
SGS4 i9500 vs. i9505 different camera sensors - XDA
Korea vs. US - Samsung Galaxy S4 - Evertic
Samsung Galaxy S4 Google Edition vs HTC One - Android Geek
Samsung Galaxy S4 vs HTC One: Which One Is Better? - Android Geek
Samsung Galaxy S4 Vs Nokia 3310 ( The true and funny one ) - Phone Arena
Samsung galaxy S4 Vs Sony Xperia Z Ultra - Phone arena
Showdown: Nvidia Tegra 4 vs Samsung Exynos 5 Octa - Android Authority
Device Comparisons / Discussions / Rumors
All new, released, rumored or announced devices should be discussed and compared here. Please keep it relevant to the Galaxy S4 with spec comparisons. All other threads that are created for this discussion will be closed. Thank you for your cooperation.
a big challenge is to compare i9500 with the i9505
i had both and tried both but sold my i9500 for an z10 to get BBM
however i think i9505 has its good aspects like
AUDIO(althought not noticeable)(plz dont trash talk abt wolfson chip i bet u all dnt know what is it just saying that )
4g LTE
and huge battery time
dev support
and last its gpu supports glse 3.0
HOwever the i9500 has ups also
like the preformance (not noticeable)
higher gpu(but stuck to glse 2.0)
better camera
well for now the exynos seems a bit unstable causing heat probs but am sure with updates it will be solved
also this is the first sammy-exynos device next devices will keep upgrading and the exynos will become more and more widespread (with other devices not this one)
i think it was a rushed move of samsung to go on with the exynos it needed more testing and development and plz cudnt samsung publish the development codes
for the i9500 its shameful as it aint getting any support by devs
for sure the double quad core is a great device but if u love 4g and developments and want ur device to last longer like for two years and still keep up the race take the i9505
qazmed said:
i had both and tried both but sold my i9500 for an z10 to get BBM
Click to expand...
Click to collapse
Isn't BBM coming to Android and iOS late this month?
MajorAly said:
Isn't BBM coming to Android and iOS late this month?
Click to expand...
Click to collapse
Rlly idk
---------- Post added at 07:10 PM ---------- Previous post was at 07:07 PM ----------
Ya it is late this summer.
OP updated. Soon major rumors / news / announcements will be updated.
Check the News & Rumor section. :good:
A new comparison added to OP. S4 vs Nokia 3310 & S4 Vs Sony X Z Ultra
Correct. BBM is expected to be released end of this month.
Android 4.3 update expected next month for "Google Edition" Samsung Galaxy S4
Android 4.3 update expected next month for "Google Edition" Samsung Galaxy S4​
The "Google Edition" of the Samsung Galaxy S4 is expected to soon receive an update to Android 4.3; quick updates are one of the features of the phone, which is powered by stock Android. Leaked images of the software running on the phone show that the update is build number JWR66N; the phone is now available for pre-orders from the Google Play Store and will be shipped by July 9th with Android 4.2.2 on board...
Source & full story: read here
Disturbed™ said:
Android 4.3 update expected next month for "Google Edition" Samsung Galaxy S4​
The "Google Edition" of the Samsung Galaxy S4 is expected to soon receive an update to Android 4.3; quick updates are one of the features of the phone, which is powered by stock Android. Leaked images of the software running on the phone show that the update is build number JWR66N; the phone is now available for pre-orders from the Google Play Store and will be shipped by July 9th with Android 4.2.2 on board...
Source & full story: read here
Click to expand...
Click to collapse
Damn exynos version
Sent from my GT-I9500 using Tapatalk 4 Beta
awesome thread!! definitely bookmarked for reference!
Thanks for bringing ur discussions here. Hope all will understand the motto of this thread and stop making related threads.
Sent from my Disturbed™ Galaxy S4 using Tapatalk 4 (VIP)
_________________________________________________
Wait for my Time, U gonna pay for what have U done. - Disturbed™
25899 antutu
Anygood
helped a lot
Awesome thread.
Linux kernel 3.10 gets big.LITTLE support, should help Ubuntu come to the Galaxy S4
Linux kernel 3.10 gets big.LITTLE support, should help Ubuntu come to the Galaxy S4​
Linux godfather Linus Torvalds has certified that the official Linux kernel 3.10 is now in its final state; and, as far as our audience is concerned, the big addition to the Linux kernel is with enhanced ARM processor support. Specifically, the Linux kernel 3.10 has added support for big.LITTLE processors, which should help developers port Ubuntu Touch to the Samsung Galaxy S4 and other devices.
Ubuntu 13.10 has been planned to run on the Linux kernel 3.10, and Ubuntu 13.10 is going to be the version number of the first set of Ubuntu Touch phones. This means that as soon as the final build of the 3.10 Linux kernel is folded into the Ubuntu dailies, work will be able to begin on finally bringing support for Ubuntu Touch to the international Samsung Galaxy S4, which runs on the Samsung Exynos Octa 5. As yet there hadn't been any work to bring Ubuntu Touch to Samsung's new flagship, because right now the daily builds of Ubuntu Touch are based on Ubuntu 13.04.
The addition of big.LITTLE support could also make it easier for future Android devices and even Chrome OS devices to run on big.LITTLE processors, because Android manufacturers won't have to build in support for the processors.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Linux kernel 3.10 arrives with ARM big.LITTLE support​
Thanks to Linus Torvalds' figurative stroke of the pen, the Linux kernel 3.10 is now final -- paving the way for its inclusion in a bevy of Linux distributions, and even offshoots such as Android and Chrome OS. The fresh kernel brings a good number of changes, such as timerless multitasking, a new caching implementation and support for the ARM big.LITTLE architecture. In simplistic terms, the new multitasking method should help improve performance and latency by firing the system timer only once per second -- rather than 1,000 times -- when tasks are running. Meanwhile, users with both traditional hard drives and SSDs will find performance benefits from bcache, which brings writeback caching and a filesystem agnostic approach to leveraging the SSD for caching operations. Also of significance, Linux kernel 3.10 enhances ARM support by including the big.LITTLE architecture, which combines multiple cores of different types -- commonly the Cortex-A7 and Cortex-A15 -- that focus on either power savings or performance. The full list of improvements is rather lengthy, but if you feel like nerding out with the changelog, just grab a caffeinated beverage and get to it.
Source: Engadget
i dont know if i will be happy or feel nothing about this 3.10 Linux update ... i9500 is so far to be updated
gdonanthony said:
i dont know if i will be happy or feel nothing about this 3.10 Linux update ... i9500 is so far to be updated
Click to expand...
Click to collapse
3.10 Linux kernel is specially designed for supporting Big.Little CPU. For sure, it will be beneficial to i9500.
Disturbed™ said:
3.10 Linux kernel is specially designed for supporting Big.Little CPU. For sure, it will be beneficial to i9500.
Click to expand...
Click to collapse
A newer linux kernel means somethings beneficial to kernels. But the stuff that you talked about is related to I9500's 5410's hardware. The 5410 silicon itself is lacking the interconnect hardware. In that case many is in doubt software cant do much. Lets see what the dev comes up about this.
thekoRngear said:
A newer linux kernel means somethings beneficial to kernels. But the stuff that you talked about is related to I9500's 5410's hardware. The 5410 silicon itself is lacking the interconnect hardware. In that case many is in doubt software cant do much. Lets see what the dev comes up about this.
Click to expand...
Click to collapse
Doubt will always be there until it get launched. Lets Hope for the best. Ubuntu Touch is like magic.
so....
Soo... it appears that as I'm assumed imbecile I must post 8-10 general posts before being allowed to post in the dev section (unless I misunderstood something in which case I am indeed imbecile). So here goes no#1.
But.. since I'm here anyway... any news on BBM for Android as mentioned above? As a year old BB user I would like to have BBM on my android.
Disturbed™ said:
Doubt will always be there until it get launched. Lets Hope for the best. Ubuntu Touch is like magic.
Click to expand...
Click to collapse

CAF vs NON CAF ?

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.

Android m/n 64 bit octa-core 100% opensource desktop computer!!!???

Hello! I had absolutely no idea where to put this thread so please direct me if need be, but I HAVE AN IDEA!!! So with the launch of 64bit Marshmallow with now Integrated Multi-Window and seeing countless phones and tablets with 2 ARM Quad-Core Processors and 3 GB of RAM, this has got my brain thinking... Isn't that enough Giddie Up for a full Desktop Computer!? I know me as a person an the only thing I'm not liking very much is the progress and lack of feature in the Linux World of Desktop Open Source. SO WHY NOT MAKE IT ANDROID!!!??? Just think. All we would have to do is develop a completely Desktop Custom ROM that runs Android 6 and 7!!! So with all of that said I NEED HELP! How would I go about learning the ins and outs of Creating Source Code? I already know how to build from source so now I need to create source.

Galaxy A7 (2018) Camera/Performance on Android 10/9/8

Hello! Here you can post some sample pictures, performance benchmarks, reviews or pros and cons for the A7 running on any of the official android versions (10/9/8) not GSI.
I'm making this post for guys like me/you, who want to choose the best official android version for making photos and awesome performance on this device. :laugh:
P.S. I've attached my Geekbench 5 and Antutu 8 score running on Android 9 Pie (A750FNXXS4BTB1).

Categories

Resources