Hey guys! The title says it all. I have read some topics about caf and I've understood that it has better support of qualcomm hardware but at the same time has no off opo libraries? Can you please tell me all of the difference between these versions? Thanks!
Related
Hi guys first sorry for post in this forum, i no have permission for write in the dev forum.
recently i get this terminal and i know it have a omap4430 and sgx540, so this hardware its similar to the galaxy nexus but jellybean 4.1.2 and 4.2.2 for my works horrible lag and unresponsive, and also something related to a fps issue that make the ui super slow.
so im working and trying to make a updated and revamped device tree for the lge p920 for jb 4.2.2, that include updated powervrsgx 540 modules and propietary drivers update to the lasted 4AJ.2.5, hwc, gralloc, libionpower, domx, libion, bltsville, etc etc. from omapzoom
at this moment i manage to get the updates for the omap44x from omapzoom, and also update the boardconfig for the new sources, its fully buildeable but at this time its not booteable and for my side adb no works for debug it.
so i have propose to all devs here for work together and try to make this work, im not a kernel dev, and my pc its so slow take 5 hours to compile the source. so for all devs here want to help and compile it for trying
this its de device tree:
github.com/samuaz/android_device_lge_p920
and also you need the updated propietary vendor:
github.com/samuaz/proprietary_vendor_lge
it can be buildable with cm10.1, aokp, pacman or whatever 4.2.2 rom
this week i try to rebuild it with a other pvrsources and boardconfig for try to make it booteable
and sorry for my english im spanish
thanks to all
it would be much easier to help you if you would fork a repo and then update the files with a new commit per file
so we can see what you've changed to what
eduzvargas said:
Hi guys first sorry for post in this forum, i no have permission for write in the dev forum.
recently i get this terminal and i know it have a omap4430 and sgx540, so this hardware its similar to the galaxy nexus but jellybean 4.1.2 and 4.2.2 for my works horrible lag and unresponsive, and also something related to a fps issue that make the ui super slow.
so im working and trying to make a updated and revamped device tree for the lge p920 for jb 4.2.2, that include updated powervrsgx 540 modules and propietary drivers update to the lasted 4AJ.2.5, hwc, gralloc, libionpower, domx, libion, bltsville, etc etc. from omapzoom
at this moment i manage to get the updates for the omap44x from omapzoom, and also update the boardconfig for the new sources, its fully buildeable but at this time its not booteable and for my side adb no works for debug it.
so i have propose to all devs here for work together and try to make this work, im not a kernel dev, and my pc its so slow take 5 hours to compile the source. so for all devs here want to help and compile it for trying
this its de device tree:
github.com/samuaz/android_device_lge_p920
and also you need the updated propietary vendor:
github.com/samuaz/proprietary_vendor_lge
it can be buildable with cm10.1, aokp, pacman or whatever 4.2.2 rom
this week i try to rebuild it with a other pvrsources and boardconfig for try to make it booteable
and sorry for my english im spanish
thanks to all
Click to expand...
Click to collapse
how far did you get with this.
in relation to hwc the ics kernel will not cut it there stuff missing i attempted to merge P920 with 3.0.31 kernel from P760
https://mega.co.nz/#!VQQw3BDS!OaeDOEaGSNE36-2ZylQVexGKqIEyrVXMSOBzH7JO2Is
need to fix errors
changes need to happen in
kernel/sound/soc/omap/omap-mcbsp.c
kernel/sound/soc/omap/omap-abe.c
kernel/include/linux/muic/muic.h
kernel/include/linux/fuel_gauge_max17043.h
kernel/include/linux/i2c/twl.h
kernel/include/linux/input/lge_touch_core.h
kernel/include/linux/i2c.h
kernel/include/linux/input.h
kernel/include/linux/cosmo/cosmo_muic.h
kernel/include/video/dsscomp.h
kernel/include/video/omapdss.h
kernel/include/net/ip6_fib.h
kernel/include/config/auto.conf
kernel/include/generated/mach-types.h
kernel/include/generated/autoconf.h
kernel/arch/arm/mach-omap2/hsmmc.c
kernel/arch/arm/mach-omap2/include/mach/lpddr2-elpida.h
kernel/arch/arm/mach-omap2/remoteproc.c
kernel/arch/arm/mach-omap2/prm44xx.c
kernel/arch/arm/mach-omap2/omap4_ion.c
kernel/arch/arm/mach-omap2/gpio.c
kernel/arch/arm/mach-omap2/lpddr2_elpida_data.c
kernel/arch/arm/mach-omap2/omap4_ion.h
kernel/arch/arm/mach-omap2/omap4-reboot-reason.c
kernel/arch/arm/mach-omap2/pm44xx.c
kernel/arch/arm/mach-omap2/lge/include/lge/board/cosmo.h
kernel/arch/arm/mach-omap2/lge/include/lge/board.h
kernel/arch/arm/mach-omap2/lge/Makefile.board
kernel/arch/arm/mach-omap2/lge/lge-common.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_i2c.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_keypad.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_cmdline.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_pdev.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_display.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo_mmc.c
kernel/arch/arm/mach-omap2/lge/cosmo/cosmo.c
kernel/arch/arm/configs/cyanogenmod_p920_defconfig
kernel/arch/arm/configs/cosmo_su760_defconfig
kernel/arch/arm/configs/cosmo_p920_defconfig
kernel/arch/arm/plat-omap/Makefile
kernel/fs/proc/base.c
kernel/kernel/timer.c
kernel/drivers/omap_hsi/hsi_driver.h
kernel/drivers/omap_hsi/xmd-tty.c
kernel/drivers/omap_hsi/xmd-hsi-ll.c
kernel/drivers/omap_hsi/hsi_driver_int.c
kernel/drivers/omap_hsi/xmd-hsi-ll-cfg.h
kernel/drivers/omap_hsi/Makefile
kernel/drivers/omap_hsi/xmd-ch.h
kernel/drivers/omap_hsi/hsi_driver.c
kernel/drivers/mmc/core/sd.c
kernel/drivers/video/omap2/displays/panel-lh430wv4-sd02.c
kernel/drivers/video/omap2/displays/panel-lh430wv2-sd01.c
kernel/drivers/video/omap2/dsscomp/dsscomp_adapt.c
kernel/drivers/video/omap2/dsscomp/gralloc.c
kernel/drivers/video/omap2/dsscomp/queue.c
kernel/drivers/video/omap2/dsscomp/device.c
kernel/drivers/video/omap2/vram.c
kernel/drivers/video/omap2/dss/dispc.c
kernel/drivers/video/omap2/dss/hdmi.c
kernel/drivers/video/omap2/dss/hdmi_panel.c
kernel/drivers/video/omap2/dss/gammatable.h
kernel/drivers/video/omap2/dss/core.c
kernel/drivers/input/touchscreen/lge_touch_core.c
kernel/drivers/input/touchscreen/touch_synaptics.c
kernel/drivers/input/touchscreen/lghdk_tm1709_ts.c
kernel/drivers/input/misc/twl6030-pwrbutton.c
kernel/drivers/input/keyboard/omap4-keypad.c
kernel/drivers/usb/gadget/f_mass_storage.c
kernel/drivers/rpmsg/rpmsg_omx.c
kernel/drivers/power/twl6030_bci_battery_ap_fuel.c
kernel/drivers/lge/subpmic/Makefile
kernel/drivers/lge/misc/Makefile
kernel/drivers/lge/Makefile
kernel/drivers/gpu/ion/omap/omap_tiler_heap.c
kernel/.config
kernel/.config.old
Click to expand...
Click to collapse
https://github.com/Pesach85/lge-kernel-omap4/search?p=1&q=CONFIG_MACH_LGE_COSMO&source=cc
i dunno if it would be easier to backport dsscomp to 3.0.21
Hi, I've just received my OPO on the 27th. I was really interested in Android development when I had my Nexus 5 and started building my own AOSP ROM, I've been looking into doing the same for the OPO but am unable to find an actual way of building AOSP with Google's code. I know OPO released their AOSP kernel source here: https://github.com/OnePlusTech/android_kernel_oneplus_one and CyanogenMod has thiers here: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974 but I'm unable to work out a way of including these into my AOSP build and I would prefer to not build CM.
Note: I'd like to build AOSP myself, I'm fully aware that there is a current official OPO build available.
Thanks in advance,
Lewis
LewisD94 said:
Hi, I've just received my OPO on the 27th. I was really interested in Android development when I had my Nexus 5 and started building my own AOSP ROM, I've been looking into doing the same for the OPO but am unable to find an actual way of building AOSP with Google's code. I know OPO released their AOSP kernel source here: https://github.com/OnePlusTech/android_kernel_oneplus_one and CyanogenMod has thiers here: https://github.com/CyanogenMod/android_kernel_oneplus_msm8974 but I'm unable to work out a way of including these into my AOSP build and I would prefer to not build CM.
Note: I'd like to build AOSP myself, I'm fully aware that there is a current official OPO build available.
Thanks in advance,
Lewis
Click to expand...
Click to collapse
It's advisable that you create your own tree from the CAF MSM8974 using CM GPS and other drivers and build CAF AOSP. Otherwise, it's close to impossible/very difficult. Pure AOSP is again near impossible/very difficult for non nexus devices.
Thank you very much for the reply, so building AOSP is pretty much impossible then?
I was having a look around on the internet last night and came across this: http://developer.sonymobile.com/kno...uild-aosp-kitkat-for-unlocked-xperia-devices/
Would there be a way of adapting this guide to allow for an easier build process of AOSP for our device? The other confusion that I face is if it's impossible to build AOSP for the OPO then how are ROMs such as this available?
LewisD94 said:
Thank you very much for the reply, so building AOSP is pretty much impossible then?
I was having a look around on the internet last night and came across this: http://developer.sonymobile.com/kno...uild-aosp-kitkat-for-unlocked-xperia-devices/
Would there be a way of adapting this guide to allow for an easier build process of AOSP for our device? The other confusion that I face is if it's impossible to build AOSP for the OPO then how are ROMs such as this available?
Click to expand...
Click to collapse
VanirAOSP uses CM trees as of now. Again, CAF AOSP is basically AOSP for non nexus Qualcomm devices., and any experienced dev can whip up a tree and get it working. Also, reaally good devs can/may be able to port AOSP if they wanted. It's a matter of whether they want to do it or not.
That link is for Sony devices only because Sony already provides CAF trees as an OEM so devs can build.
rudi_j7 said:
VanirAOSP uses CM trees as of now. Again, CAF AOSP is basically AOSP for non nexus Qualcomm devices., and any experienced dev can whip up a tree and get it working. Also, reaally good devs can/may be able to port AOSP if they wanted. It's a matter of whether they want to do it or not.
That link is for Sony devices only because Sony already provides CAF trees as an OEM so devs can build.
Click to expand...
Click to collapse
Ah yes, I see what you're saying now. Thanks for clearing this up for me! I just noticed when I looked at the VanirAOSP ROM thread that it states CM for it's credits, haha. I apologize for my ignorance.
Hello
I would like to create my first rom for oneplus one but without modification from OMNI or CM, basically vanilla rom. but I have some doubts.
Can I create a rom based on AOSP with device tree from OMNI/CM right?
Thanks!
Hello Everyone. I'm just N5 nomal user during 2years and I had question so write this text.
I googled about AOSP / Caf and understood like this.
AOSP was handling by google, have some feature.
Caf was handling by qualcomm, more performand and seek stabilization.
Question is, Pure AOSP+Caf rom is possible?
Developers offfer to us CM-Based Caf (hammerhead-caf) but I didn't heard about AOSP + Caf.
Did I have wrong thinking?
As I told, I'm just commly n5 user Please expain easily.
Have a nice day.
kwjhgjh said:
Hello Everyone. I'm just N5 nomal user during 2years and I had question so write this text.
I googled about AOSP / Caf and understood like this.
AOSP was handling by google, have some feature.
Caf was handling by qualcomm, more performand and seek stabilization.
Question is, Pure AOSP+Caf rom is possible?
Developers offfer to us CM-Based Caf (hammerhead-caf) but I didn't heard about AOSP + Caf.
Did I have wrong thinking?
As I told, I'm just commly n5 user Please expain easily.
Have a nice day.
Click to expand...
Click to collapse
I think we cannot. CAF and AOSP are in two different line. If they can be combined, there must be a version of android like that now
Moto g 2014 has an aosp caf http://forum.xda-developers.com/moto-g-2014/development/aosp-caf-6-0-t3284309
muitenphale said:
I think we cannot. CAF and AOSP are in two different line. If they can be combined, there must be a version of android like that now
Click to expand...
Click to collapse
But we already use CAF lines rom, like CM-Caf.
Dev. said, Basement is AOSP-CM and put in CAF source to it.
I had more curious why Dev. are don't use AOSP, just connect with cm
CataHd said:
Moto g 2014 has an aosp caf http://forum.xda-developers.com/moto-g-2014/development/aosp-caf-6-0-t3284309
Click to expand...
Click to collapse
oh... Already annouced in MOTO G! thread . Even they have a little bug, impressive.
If I have 1 excellent computer, maybe try to build...refer other people's post T_T
Anyway THX for your link
HI,
does anybody know what is the current status of mainline msm8960 support? Do I see it right that there was some effort (https://groups.google.com/forum/#!topic/linux.kernel/QpU5DZc915k), but this wasn't applied? But there seems to be a bit of support in arch/arm/mach-qcom?
Best regards,
mifritscher
I would advise getting in touch with kabaldan, as he is the primary maintainer for our Photon Q
I beg u guys to please open a thread for Mi4i nightly build on Cyanogenmod forums and discuss problems with the build over there coz the devs won't come here to see what the problems are. :fingers-crossed:
I beg u guys to please open a thread for Mi4i nightly build on Cyanogenmod forums and discuss problems with the build over there coz the devs won't come here to see what the problems are.
Click to expand...
Click to collapse
The people who make CyanogenMOD are not the ones supporting this device
Cyanogenmod forums are even less visible and it is a hassle to keep track of two forums at once
The Official Builds are currently of CM13
An [OFFICIAL] thread for CM13 will be made by @Rohan purohit soon.
News about CM14 will be out when it will be. Rule #1 of custom ROM development, NO ETA.
And finally, VoLTE can NOT be enabled without updated modem firmware, from Xiaomi, with VoLTE support. No VoLTE unless Xiaomi wants to give us VoLTE. The End of Discussion.
If not me, listen to the guy who started CyanogenMOD itself: https://twitter.com/cyanogen/status/790674207369678848
Code:
</rant>