[UNOFFICIAL] [ROM] CodeAuroraICS (Android 4.0.4 - .35 kernel - CAF-based)
- Thread starter Bytecode
- Start date
andy572
Inactive Recognized Developer
Hmmm.know the cause of framework base incompatibility: I got GB branch instead of master branchlet's see now.
hehe, why you not use the repo tool?
1) repo init -u http://....... -b ics
2) edit manifest.xml to remove unwanted ****
3) repo sync
using the "-b [Branch_Name]" allows you to select a special branch instead of all.
than you have all needed files and less problems to configure all things
andy572
Inactive Recognized Developer
btw:
if you can wait until my holiday i can try again to accelerate the graphic through the CPU
in hwcomposer - than users have at least a some faster UI (but without 3D effects/rendering), its better than complete without accel
_Arjen_ can use the hwcomper too in his CM9 build, its the same technical ****.
its because i'm trying currently to use the hwcomposer for phoenix, i asked franco
he meant the same as me: accelerate the UI through pmem (2D accel) can be very useful
if you can wait until my holiday i can try again to accelerate the graphic through the CPU
in hwcomposer - than users have at least a some faster UI (but without 3D effects/rendering), its better than complete without accel
_Arjen_ can use the hwcomper too in his CM9 build, its the same technical ****.
its because i'm trying currently to use the hwcomposer for phoenix, i asked franco
he meant the same as me: accelerate the UI through pmem (2D accel) can be very useful
Last edited:
Too bad you can't thank 10 times
Greets
____________
mDroid - Tapatalk
Phone: LG-P500
ROM: Ciaox' openOptimus
Kernel: franco .35
Theme: HoneySandwich (by me)
Tweaks: Turbocharged and Supercharged!
Wishlist: Galaxy Nexus
Greets
____________
mDroid - Tapatalk
Phone: LG-P500
ROM: Ciaox' openOptimus
Kernel: franco .35
Theme: HoneySandwich (by me)
Tweaks: Turbocharged and Supercharged!
Wishlist: Galaxy Nexus
Wow,I'm getting mad here. Andy "committed" lots of stuffs,just finished fixing hardware_msm7k and hardware_qcom. Only framework base left
Have to study now
Anyway LOL,I fixed a lot of stuff in copybit and gralloc,then saw a commit from andy: Import the whole tree from CAF,so I struggled only for replacing my work later?!?
Stuff left to fix:
SOo finally I found my way. If it doesn't build,I'll probably... you tell me
Have to study now
Anyway LOL,I fixed a lot of stuff in copybit and gralloc,then saw a commit from andy: Import the whole tree from CAF,so I struggled only for replacing my work later?!?
Stuff left to fix:
- Frameworks base
- Dalvik VM
- Build (actually CAF did by moving ARMv6k-VFP stuff here)
- Bionic (libc etc.)
- MSM7K Hardware (Android.mk) libcopybit remove,CAF code helped here too)
- QCOM Hardware (import libgralloc/libcopybit from CAF: Remove libgenlock)
SOo finally I found my way. If it doesn't build,I'll probably... you tell me
Last edited:
andy572
Inactive Recognized Developer
Wow,I'm getting mad here. Andy "committed" lots of stuffs,just finished fixing hardware_msm7k and hardware_qcom. Only framework base left
Have to study now
Anyway LOL,I fixed a lot of stuff in copybit and gralloc,then saw a commit from andy: Import the whole tree from CAF,so I struggled only for replacing my work later?!?
Stuff left to fix:
Stuff I did;
- Frameworks base
- Dalvik VM
- Build (actually CAF did by moving ARMv6k-VFP stuff here)
- Bionic (libc etc.)
- MSM7K Hardware (Android.mk) libcopybit remove,CAF code helped here too)
- QCOM Hardware (import libgralloc/libcopybit from CAF: Remove libgenlock)
SOo finally I found my way. If it doesn't build,I'll probably... you tell me
i'm not finished fixing hardware drivers - as i sayed: we need a new hwcomposer
thats supports compositing between cpu and mdp because we cant accelerate the HW through the gpu
my commits was only the begin of the work - i think nothing of the commits in the msm7k folder can work^^
andy572
Inactive Recognized Developer
... and its some faster than the CM9 one:
if you look through the code, i dont copied only the armv5 files - i have declared
the target as armv6 too, cm wasnt doing that and there are now some missing pieces of speed and memory management^^
andy572
Inactive Recognized Developer
WTF That means I can replace the whole framework dir with yours?yes, you can replace dalvik. its a "standalone" project without dependencies, other like bionic or the framework or system/core
No, you can replace dalvikvm directory
Actually I replaced the whole dalvik folder
BTW,there's one problem bothering me since CM6 which I'm able to solve but probably not in the right way:
Code:
build/core/base_rules.mk:166: *** hardware/msm7k/libaudio: MODULE.TARGET.SHARED_LIBRARIES.libaudiopolicy already defined by device/lge/thunderg/libaudio. Stop.Same happens with liblights. For solving it should I delete MSM7K lib or proprietary lib? Or what else?
Will code framework tomorrow,can't tonight
will have to check lots of your commits andy )
andy572
Inactive Recognized Developer
add a switch in boardconfig:
in the msm7k audio folder add to Android.mk as first line
do the same with your liblights, you can use all variable names, even "asshole"
Code:
TARGET_PROVIDES_LIBAUDIO := truein the msm7k audio folder add to Android.mk as first line
Code:
ifneq ($(TARGET_PROVIDES_LIBAUDIO),true)
..... a lot of defines
##### and this at last
endifdo the same with your liblights, you can use all variable names, even "asshole"
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
13Hello there,while working on OMFGB and CM6,I decided to take ICS CAF sources and build them since andy is working at AOSP,arjen is working at CM9 and now I'm working at CAF. I opened this since I can handle various projects at a time,infact I'm developing for other stuff also.
Current status: Fixing build errors2@Bytecode, maybe this small info can be helpful:
you need to change a lot of configs in CAF to build - its like the AOSP configs.
the most pro on this project is, its made for MSM devices, possible you can get more
things to function (if things are fixed by CAF) as in CM9 or AOSP ... good luck2
in hope for better compatibility with ICS some things are needed, as example a
newer kernel which supports the new OpenGL things, done in KGSL drivers in kernel,
and its needed for some improvements in filesystems.
New posts
-
-
Development [UNOFFICIAL] Paranoid Android Uvite - Xiaomi Pad 6 Pro- Latest: accelerator_top
-
