Why is source for 4.4 phone app invisible?
I can see 4.3 source fine, but 4.4 is empty.
Because the package was moved/renamed in 4.4
Related
if there is a way to build custom roms(completely usable) from samsung's open source?
wooooooo thats a loaded question.
In short - not really the only thing that is "open" is the kernel and whats left of Android it self....
The rest of the OS has been haggard up by touchwiz and is closed source.
This is essentially what the CyanogenMod project is.
Does anyone here have the link for Huawei's source tree? What I'm looking for is the 2.6.35 kernel source code and the tarball which has extract-files.sh inside (android_device_huawei_u8800 I think?) I could only find modified ones for Cyanogenmod and ICS. I'm in a big need for them. I can't even download the source code for the kernel from Huawei's site because it just throws "Service currently unavailable" for me.
I actually tried using some device tree from github, but it resulted in these errors.
What I'm looking for are the non modified source files which I could use to build AOSP (Gingerbread).
Thanks in advance.
Hey there!
Are there any devs that want to built KitKat from source for our find5?
Thanks in advance.
I believe all 3rd party roms for Find 5 will upgrade to 4.4. At least the active ones who keep getting updates.
brakke97 said:
Hey there!
Are there any devs that want to built KitKat from the source for our find5?
Thanks in advance.
Click to expand...
Click to collapse
As soon as aosp Master branch is being updated to kitkat, cfxe will go for it hopefully it will come soon so we can get started
A side node: omni rom uses branch :android-4-4_r1 , whats diffrent from master branch is , that is the first release, and master branch is the dev branch. If we use 4-4_r1 99% sure nothing is being merged to aosp, but when we use master branch , changes is being merged to aosp sources.
AOSP reviews by synergy
aosp now has sources for android l preview. anyone up for the challenge? it's going to be buggy as hell but should be better than porting a rom. lets see if the latest incarnation of art is better.
www.androidpolice.com/2014/07/01/an...ve-aosp-includes-support-nexus-4-5-7-2013-10/
I want to build a stable 4.4.2 omni, but omni codes in github had updated to 4.4.4, and I do not know how to roll back.
In CM, there is always a build-manifest.xml in its rom and I can easily roll back to the status defined by build-manifest.xml (http://wiki.cyanogenmod.org/w/Doc:_Using_local_manifests#The_local_manifest).
Then I wonder how can I get the xml file to obtain the same repos as you guys in a stable release?