797 replies to this topic

[t0mm13b]

sm4tik, on 10 April 2012 - 07:49 PM, said:

You didn't get the reply in CM7 thread?

Haven't checked whether there are patches for ics also?

@sm4tik:

As a fyi - I have posted the resolved issue to the broken gcc toolchain with 4.7, The post is found here on archlinux forum. Have successfully reverted back to the last good known version and all compiles well

[sej7278]

sm4tik, on 10 April 2012 - 07:11 PM, said:

sej, can you check if the apk's still have all the unnecessary mdpi/xhdpi/etc.. stuff in them. I see those in 04/07 CFX, so I guess device_blade.mk has been updated after that build to include

+PRODUCT_AAPT_PREF_CONFIG := hdpi
+PRODUCT_AAPT_CONFIG := normal hdpi

Just curious because this has been something bugging me since the first AOSP build.
Thanks.

no its just the hdpi in the build i did yesterday.

i just flashed my build (took 54mins to compile) and noticed a couple of odd things:

first off setting debug.sf.nobootanimation=1 in device/zte/blade/cm.mk doesn't work i still get the bootanimation (it doesn't echo 1 > /data/property/persist.sys.nobootanimation)

i'm not sure if its related to that, but my boot animation is now shrunk to about half its size.

oh and you're better off loading oi file manager from market as if you use the zip it seems to be uninstalled when you reflash.

also noticed that changing ro.modversion in vendor/cm/config/common.mk doesn't change the filename of the resulting zip (update-cm-9.0.0-RC0-blade-UNOFFICIAL-signed.zip) or the info shown in settings->about phone->cyanogenmod version, it does seem to change the string that rommanager reports though. i guess now they're using ro.cm.version ?

 PRODUCT_PROPERTY_OVERRIDES += \
   ro.cm.version=$(CM_VERSION) \
-  ro.modversion=$(CM_VERSION)
+  ro.modversion=$(CM_VERSION)-sej$(shell date +%Y%m%d)

 Screenshot_2012-04-11-14-42-13.png   70.21K   12 downloads

Edited by sej7278, 11 April 2012 - 01:13 PM.

[sm4tik]

sej7278, on 11 April 2012 - 09:41 AM, said:

no its just the hdpi in the build i did yesterday.

Ok, thanks. That should be enough to fit 160MB with mini-gapps withouth having to delete anything, am I right?

[asm19]

sej7278, on 10 April 2012 - 10:19 PM, said:

bit odd that, its nothing to do with extract-files.sh, are you sure you're using a cyanogenmod repo and not pure google or something - although i repo init'ed using aosp and i have that directory. should be about 14 gigs in total.

it definitely should be there: https://github.com/C...droid_vendor_cm

github has been up and down a bit tonight, maybe you didn't fetch it?

Hi sej7278,

I was now seeing the directories and I think that your directory is wrong, I have the file in envsetup.sh /coldfusionx/vendor/cm/ not in /coldfusionx/cm9/vendor/cm
I'm just doing a backup and see if I compile compiles without problems.

Edited by asm19, 11 April 2012 - 05:47 PM.

[sej7278]

asm19, on 11 April 2012 - 05:47 PM, said:

Hi sej7278,

I was now seeing the directories and I think that your directory is wrong, I have the file in envsetup.sh /coldfusionx/vendor/cm/ not in /coldfusionx/cm9/vendor/cm
I'm just doing a backup and see if I compile compiles without problems.

the cm9 subdirectory is where the cm9 sourcecode should be checked out into.

the coldfusionx directory above that is where tilal's githubs go.

you then merge them using the rsync commands.

looks like you've got the githubs and cm9 in the same directory, but even then build.sh shouldn't be in vendor/cm/ it should be in build/

you should have:

 dirstructure.png   10.52K   3 downloads

Edited by sej7278, 11 April 2012 - 06:18 PM.

[asm19]

sej7278, on 11 April 2012 - 07:01 PM, said:

just a bit of moving directories, shouldn't be too hard.

note the bootanimation is shrunk using the mini confg, so in android_device_zte_common/BoardConfigCommon.mk you probably want to add the line (not tested yet, doing a rebuild now):

TARGET_BOOTANIMATION_NAME := vertical-480x800

anyone know how we set CM_NIGHTLY - is it just an environment variable?

Nice, thanks for the tip.
I'm new at this building "roms" but I like it!

[asm19]

I have an error early on in the compilation of the rom:

build/core/base_rules.mk:166: *** device/zte/common/libaudio: MODULE.TARGET.SHARED_LIBRARIES.audio_policy.blade already defined by device/zte/blade/libaudio.  Stop.


Does anyone know how to fix?

[sej7278]

asm19, on 11 April 2012 - 08:28 PM, said:

I have an error early on in the compilation of the rom:

build/core/base_rules.mk:166: *** device/zte/common/libaudio: MODULE.TARGET.SHARED_LIBRARIES.audio_policy.blade already defined by device/zte/blade/libaudio.  Stop.


Does anyone know how to fix?

update android_device_zte_common using "git pull" that was fixed a couple of days ago.

also my bootanimation fix got merged by tilal (github) so an update will pull that down too.hmm, although it doesn't seem to have worked with my test build......

Edited by sej7278, 11 April 2012 - 08:36 PM.

[asm19]

sej7278, on 11 April 2012 - 08:33 PM, said:

update android_device_zte_common using "git pull" that was fixed a couple of days ago.

also my bootanimation fix got merged by tilal (github) so an update will pull that down too.hmm, although it doesn't seem to have worked with my test build......

:~/coldfusionx/android_device_zte_common$ git pull


Updating a160769..f1451fa
error: Your local changes to 'BoardConfigCommon.mk' would be overwritten by merge.  Aborting.
Please, commit your changes or stash them before you can merge.

Is it normal?

Edit: Still the same error even after git pull in: android_device_zte_common

Checking build tools versions...
build/core/base_rules.mk:166: *** device/zte/common/libaudio: MODULE.TARGET.SHARED_LIBRARIES.audio_policy.blade already defined by device/zte/blade/libaudio.  Pare.

Edited by asm19, 11 April 2012 - 08:55 PM.

[sej7278]

asm19, on 11 April 2012 - 08:47 PM, said:

:~/coldfusionx/android_device_zte_common$ git pull


Updating a160769..f1451fa
error: Your local changes to 'BoardConfigCommon.mk' would be overwritten by merge.  Aborting.
Please, commit your changes or stash them before you can merge.

Is it normal?

Edit: Still the same error even after git pull in: android_device_zte_common

Checking build tools versions...
build/core/base_rules.mk:166: *** device/zte/common/libaudio: MODULE.TARGET.SHARED_LIBRARIES.audio_policy.blade already defined by device/zte/blade/libaudio.  Pare.

yes you have to delete your local changes before git pulling using e.g. "git reset --hard HEAD" in each directory.

[tilal6991]

Why have you got libaudio in device/zte/blade? Delete the blade folder and try and clone the repo again.

[asm19]

sej7278, on 11 April 2012 - 09:48 PM, said:

no its not the same - you've got libaudio in common but not blade - which is correct.

i don't want to sound elitist, but if you're going to be building roms you need some understanding of git and attention to detail.

i really don't mean that to sound like an ass lol

sej7278, I did not say it was because I realized the differences. What I meant was that I continue with the same compile error after deleting the folders blade and common and have done clone repo again...

build/core/base_rules.mk:166: *** device/zte/common/libaudio: MODULE.TARGET.SHARED_LIBRARIES.audio_policy.blade already defined by device/zte/blade/libaudio.  Stop.

[sej7278]

asm19, on 11 April 2012 - 09:57 PM, said:

sej7278, I did not say it was because I realized the differences. What I meant was that I continue with the same compile error after deleting the folders blade and common and have done clone repo again...

yes but you've not run the rsync commands again to copy the changes from the github directories into the cm9 directory.

what you have there is an updated android_device_zte_common/ but still the old files in cm9/device/zte/common/

its not like cm7 where everything is in one git structure. we have to merge together tilal's git into the cm9 git.

Edited by sej7278, 11 April 2012 - 10:04 PM.

[asm19]

sej7278, on 11 April 2012 - 09:59 PM, said:

yes but you've not run the rsync commands again to copy the changes from the github directories into the cm9 directory.

what you have there is an updated android_device_zte_common/ but still the old files in cm9/device/zte/common/

its not like cm7 where everything is in one git structure. we have to merge together tilal's git into the cm9 git.

Already the build. sej7278, thanks for your help and patience. Let's see if just to compile without errors Now this is to study more"background".
How long it takes +/-, 45min?

[sej7278]

asm19, on 11 April 2012 - 10:24 PM, said:

Already the build. sej7278, thanks for your help and patience. Let's see if just to compile without errors Now this is to study more"background".
How long it takes +/-, 45min?

so the instructions aren't that clear yet i guess, but at least we got you there!

i've had varying compile times between 45-57mins.

[asm19]

sej7278, on 11 April 2012 - 11:49 PM, said:

so the instructions aren't that clear yet i guess, but at least we got you there!

i've had varying compile times between 45-57mins.

Is still compile but should be finished. I had a problem at the beginning webrtc related, but I resolved soon.
Thanks again!


PS: "p.s. TARGET_BOOTANIMATION_NAME := vertical-480x800 seems to work in android_device_zte_common/device_zte.mk not BoardConfigCommon.mk"

It worked?

Edited by asm19, 11 April 2012 - 11:59 PM.

[sej7278]

asm19, on 11 April 2012 - 11:56 PM, said:

Is still compile but should be finished. I had a problem at the beginning webrtc related, but I decided soon.
Thanks again!


PS: "p.s. TARGET_BOOTANIMATION_NAME := vertical-480x800 seems to work in android_device_zte_common/device_zte.mk not BoardConfigCommon.mk"

It worked?

webrtc problems are fixed with the arm6 patch step.

yes boot animation in device_zte.mk works fine, so we need to get tilal to update that in his github. for now you can manually move the line out of BoardConfigCommon.mk and into device_zte.mk

[asm19]

sej7278, on 12 April 2012 - 12:00 AM, said:

webrtc problems are fixed with the arm6 patch step.

yes boot animation in device_zte.mk works fine, so we need to get tilal to update that in his github. for now you can manually move the line out of BoardConfigCommon.mk and into device_zte.mk

Yes, I now compiled without changes to see if a concession to build is successful. Then immediately add the line
It appears that the bluetooth is already fixed, right?

[sej7278]

asm19, on 12 April 2012 - 12:06 AM, said:

Yes, I now compiled without changes to see if a concession to build is successful. Then immediately add the line
It appears that the bluetooth is already fixed, right?

well yes but you'd either have to compile a new kernel with that patch added, or wait for tilal to put a new blob in android_device_zte_blade

[asm19]

sej7278, what better way to compile the kernel in order to make a "patch"?
I was watching this and your post CM7 seems interesting to me: http://blog.the-jedi...android-kernel/

Edited by asm19, 12 April 2012 - 01:09 PM.