Jump to content


Photo

[ROM][beta]CyanogenMod 9

* * * * * 8 votes

  • Please log in to reply
681 replies to this topic

#121
VJftw

VJftw

    Regular

  • Members
  • PipPip
  • 60 posts
  • Gender:Male
  • Devices:Acer Liquid Mt
Lens, sorry I keep asking you for help ah but i'm learning slowly!
for compiling CM9, i've followed the instructions from your GIT repo, but when running Apply-Patch.sh, I'm getting issues

vj@vj-Inspiron-1525:~/android-ics/system/device/acer/a4/dev$ ./Apply-Patch.sh
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/external/mesa3d/src/glsl/linker.cpp b/external/mesa3d/src/glsl/linker.cpp
|index f8b6962..f31e5b5 100644
|--- a/external/mesa3d/src/glsl/linker.cpp
|+++ b/external/mesa3d/src/glsl/linker.cpp
--------------------------
File to patch: 

So i've tried running
diff --git a/external/mesa3d/src/glsl/linker.cpp b/external/mesa3d/src/glsl/linker.cpp
on it's own in terminal but I get this output

diff: unrecognised option '--git'
diff: Try `diff --help' for more information.

so i'm guessing that i'm missing the --git option? but after googling around I can't find any answers :s

any ideas?

  • 0

#122
Lens_flare

Lens_flare

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,504 posts
hey guys stop flaming, you forgot why we are here..

for compiling CM9, i've followed the instructions from your GIT repo, but when running Apply-Patch.sh, I'm getting issues

ok I'll see if it is broken.. damn so many patch errors :D
btw, updated repo with some build fixes.

btw2: the right cmd is git diff :P
but it just finding differencies on your local repo with remote, to patch a diff file use patch -p1

Edited by Lens_flare, 12 April 2012 - 02:48 AM.

  • 0

#123
n0tBad

n0tBad

    Newbie

  • Members
  • Pip
  • 4 posts
  • Devices:Acer Liqui Metal S120
Hey Lens thanks for your work!!!

  • 0

#124
VJftw

VJftw

    Regular

  • Members
  • PipPip
  • 60 posts
  • Gender:Male
  • Devices:Acer Liquid Mt

vj@vj-Inspiron-1525:~/android-ics/system$ . build/envsetup.sh
including device/acer/a4/vendorsetup.sh
including device/acer/paso/vendorsetup.sh
including device/advent/vega/vendorsetup.sh
including device/bn/encore/vendorsetup.sh
including device/geeksphone/one/vendorsetup.sh
including device/htc/ace/vendorsetup.sh
including device/htc/bravoc/vendorsetup.sh
including device/htc/bravo/vendorsetup.sh
including device/htc/buzz/vendorsetup.sh
including device/htc/click/vendorsetup.sh
including device/htc/desirec/vendorsetup.sh
including device/htc/dream_sapphire/vendorsetup.sh
including device/htc/espresso/vendorsetup.sh
including device/htc/glacier/vendorsetup.sh
including device/htc/heroc/vendorsetup.sh
including device/htc/hero/vendorsetup.sh
including device/htc/inc/vendorsetup.sh
including device/htc/legend/vendorsetup.sh
including device/htc/leo/vendorsetup.sh
including device/htc/liberty/vendorsetup.sh
including device/htc/mecha/vendorsetup.sh
including device/htc/passion/vendorsetup.sh
including device/htc/saga/vendorsetup.sh
including device/htc/speedy/vendorsetup.sh
including device/htc/supersonic/vendorsetup.sh
including device/htc/vision/vendorsetup.sh
including device/htc/vivo/vendorsetup.sh
including device/htc/vivow/vendorsetup.sh
including device/huawei/u8150/vendorsetup.sh
including device/huawei/u8220/vendorsetup.sh
including device/lge/p999/vendorsetup.sh
including device/malata/smb_a1002/vendorsetup.sh
including device/malata/smb_b9701/vendorsetup.sh
including device/motorola/droid2/vendorsetup.sh
including device/motorola/droid2we/vendorsetup.sh
including device/motorola/jordan/vendorsetup.sh
including device/motorola/morrison/vendorsetup.sh
including device/motorola/motus/vendorsetup.sh
including device/motorola/olympus/vendorsetup.sh
including device/motorola/shadow/vendorsetup.sh
including device/motorola/sholes/vendorsetup.sh
including device/motorola/zeppelin/vendorsetup.sh
including device/samsung/captivatemtd/vendorsetup.sh
including device/samsung/cooper/vendorsetup.sh
including device/samsung/crespo4g/vendorsetup.sh
including device/samsung/crespo/vendorsetup.sh
including device/samsung/epicmtd/vendorsetup.sh
including device/samsung/fascinatemtd/vendorsetup.sh
including device/samsung/galaxys2att/vendorsetup.sh
including device/samsung/galaxys2/vendorsetup.sh
including device/samsung/galaxysbmtd/vendorsetup.sh
including device/samsung/galaxysmtd/vendorsetup.sh
including device/samsung/mesmerizemtd/vendorsetup.sh
including device/samsung/showcasemtd/vendorsetup.sh
including device/samsung/sidekick4g/vendorsetup.sh
including device/samsung/tass/vendorsetup.sh
including device/samsung/vibrantmtd/vendorsetup.sh
including device/zte/blade/vendorsetup.sh
including device/zte/v9/vendorsetup.sh
including vendor/cyanogen/vendorsetup.sh
vj@vj-Inspiron-1525:~/android-ics/system$ lunch cm_a4-userdebug
build/core/product_config.mk:196: *** _nic.PRODUCTS.[[device/acer/a4/device_a4.mk]]: "build/target/product/full_base_telephony.mk" does not exist. Stop.
Device a4 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for a4 not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:196: *** _nic.PRODUCTS.[[device/acer/a4/device_a4.mk]]: "build/target/product/full_base_telephony.mk" does not exist. Stop.

** Don't have a product spec for: 'cm_a4'
** Do you have the right repo manifest?

the device tree should be device/acer/a4 right? :s

  • 0

#125
Lens_flare

Lens_flare

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,504 posts
log stands you don't have full_base_telephone.mk, search for it in repo :/

  • 0

#126
VJftw

VJftw

    Regular

  • Members
  • PipPip
  • 60 posts
  • Gender:Male
  • Devices:Acer Liquid Mt

log stands you don't have full_base_telephone.mk, search for it in repo :/


i don't :s

Just resynced the repo with repo sync. Still doesn't find it :s

The only thing i haven't done is the Apply-Patch.sh because It still gives me those errors i messaged about before, but it's not completely necessary?

  • 0

#127
Lens_flare

Lens_flare

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,504 posts
will see today if it is not present anymore, also I promised apply-patch fix :P

  • 0

#128
Lens_flare

Lens_flare

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,504 posts
VJftw
there is no full_base_telephony.mk in my configs, seems you have reposynced cm7 ,not cm9((for example see devices list, there are no htc-s in cm9. about apply-patch.sh,I've fixed it, just redownload files that I lately commited.
to reposync cm9 you should change branch from gingerbread to ics when you are doing repo init

Edited by Lens_flare, 13 April 2012 - 02:23 PM.

  • 0

#129
VJftw

VJftw

    Regular

  • Members
  • PipPip
  • 60 posts
  • Gender:Male
  • Devices:Acer Liquid Mt

VJftw
there is no full_base_telephony.mk in my configs, seems you have reposynced cm7 ,not cm9((for example see devices list, there are no htc-s in cm9. about apply-patch.sh,I've fixed it, just redownload files that I lately commited.
to reposync cm9 you should change branch from gingerbread to ics when you are doing repo init


ohhh, ok i'll do that :) thanks!

  • 0

#130
VJftw

VJftw

    Regular

  • Members
  • PipPip
  • 60 posts
  • Gender:Male
  • Devices:Acer Liquid Mt
so close now :s

Apply-Patch.sh works perfectly, extracted from phone fine again.. lunch went good, just the making :s

vj@vj-Inspiron-1525:~$ . build/envsetup.sh
including device/acer/a4/vendorsetup.sh
including device/moto/wingray/vendorsetup.sh
including device/samsung/maguro/vendorsetup.sh
including device/samsung/toro/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including sdk/bash_completion/adb.bash
vj@vj-Inspiron-1525:~$ lunch cm_a4-userdebug

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.0.4
TARGET_PRODUCT=cm_a4
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=IMM76D
============================================

vj@vj-Inspiron-1525:~$ make -j4
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.0.4
TARGET_PRODUCT=cm_a4
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=IMM76D
============================================
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/bionic/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/dalvik/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/development/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/common/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/ace/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/click/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/common/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/desirec/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/dream_sapphire/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/espresso/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/glacier/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/hero/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/heroc/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/inc/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/leo/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/liberty/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/mecha/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/passion-common/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/passion/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/saga/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/speedy/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/supersonic/CleanSpec.mk: No such file or directory
build/core/cleanspec.mk:68: .local/share/Trash/files/android: No such file or directory
build/core/cleanspec.mk:68: (copy)/system/device/htc/vision/CleanSpec.mk: No such file or directory
.........SNIP SEE ATTACHED FILE FOR FULL.........
build/core/main.mk:528: .local/share/Trash/files/android: No such file or directory
build/core/main.mk:528: (copy)/system/vendor/tmobile/apps/ThemeChooser/Android.mk: No such file or directory
build/core/main.mk:528: .local/share/Trash/files/android: No such file or directory
build/core/main.mk:528: (copy)/system/vendor/tmobile/libs/com.tmobile.themes/Android.mk: No such file or directory
build/core/main.mk:528: .local/share/Trash/files/android: No such file or directory
build/core/main.mk:528: (copy)/system/vendor/tmobile/providers/ThemeManager/Android.mk: No such file or directory
build/core/main.mk:528: .local/share/Trash/files/android: No such file or directory
build/core/main.mk:528: (copy)/system/vendor/tmobile/themes/Androidian/Android.mk: No such file or directory
build/core/main.mk:528: .local/share/Trash/files/android: No such file or directory
build/core/main.mk:528: (copy)/system/vendor/tmobile/themes/Cyanbread/Android.mk: No such file or directory
build/core/base_rules.mk:78: *** Module name: apriori
build/core/base_rules.mk:79: *** Makefile location: .local/share/Trash/files/android-ics/system/build/tools/apriori
build/core/base_rules.mk:80: * 
build/core/base_rules.mk:81: * Each module must use a LOCAL_MODULE_TAGS in its
build/core/base_rules.mk:82: * Android.mk. Possible tags declared by a module:
build/core/base_rules.mk:83: * 
build/core/base_rules.mk:84: * 	optional, debug, eng, tests, samples
build/core/base_rules.mk:85: * 
build/core/base_rules.mk:86: * If the module is expected to be in all builds
build/core/base_rules.mk:87: * of a product, then it should use the
build/core/base_rules.mk:88: * "optional" tag: 
build/core/base_rules.mk:89: * 
build/core/base_rules.mk:90: *    Add "LOCAL_MODULE_TAGS := optional" in the
build/core/base_rules.mk:91: *    Android.mk for the affected module, and add
build/core/base_rules.mk:92: *    the LOCAL_MODULE value for that component
build/core/base_rules.mk:93: *    into the PRODUCT_PACKAGES section of product
build/core/base_rules.mk:94: *    makefile(s) where it's necessary, if
build/core/base_rules.mk:95: *    appropriate.
build/core/base_rules.mk:96: * 
build/core/base_rules.mk:97: * If the component should be in EVERY build of ALL
build/core/base_rules.mk:98: * products, then add its LOCAL_MODULE value to the
build/core/base_rules.mk:99: * PRODUCT_PACKAGES section of
build/core/base_rules.mk:100: * build/target/product/core.mk
build/core/base_rules.mk:101: * 
build/core/base_rules.mk:102: *** user tag detected on new module - user tags are only supported on legacy modules. Stop.


looks like i'm missing something

  • 0

#131
Lens_flare

Lens_flare

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,504 posts
seems you switched branch without erasing all files in folder android-ics/system. I hardly recommend you to erase whole android-ics/system (yesterday' the build was fine, should fine for you too).

And why are you trying to build it, want new beta? _-

  • 0

#132
VJftw

VJftw

    Regular

  • Members
  • PipPip
  • 60 posts
  • Gender:Male
  • Devices:Acer Liquid Mt
mostly out of interest, I'm trying to learn so that I can contribute something back to this community eventually

  • 0

#133
hughfollett

hughfollett

    Newbie

  • Members
  • Pip
  • 8 posts
  • Devices:Galaxy SII
Hi guys! Really appreciating this hard work!! Just a quick question: will this rom be compatible with 128k H3G sim? I can't use miui roms because I can't save APNs..
Thanks in advance!

  • 0

#134
ltpitt

ltpitt

    Diehard

  • Members
  • PipPipPipPip
  • 476 posts
  • Devices:Acer Liquid Metal

Hi guys! Really appreciating this hard work!! Just a quick question: will this rom be compatible with 128k H3G sim? I can't use miui roms because I can't save APNs..
Thanks in advance!


Only a complete RIL implementati on would solve the problem.
All my fingers are crossed but I think it won't be easy.
Sent from my Liquid MT using Tapatalk

  • 0

#135
Lens_flare

Lens_flare

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,504 posts

will this rom be compatible with 128k H3G sim?

ics&cm seems resolved some usim bounds.. let's see when mobile data will be done..

  • 1

#136
hughfollett

hughfollett

    Newbie

  • Members
  • Pip
  • 8 posts
  • Devices:Galaxy SII

ics&cm seems resolved some usim bounds.. let's see when mobile data will be done..


Really thanks for your answer Lens! My father is impatiently waiting for cm9! He's tried MIUI and he likes it, but he is on H3G Italy:(

Edited by hughfollett, 15 April 2012 - 05:56 PM.

  • 0

#137
fabiorino

fabiorino

    Regular

  • Members
  • PipPip
  • 141 posts
  • Gender:Male
  • Devices:Acer Liquid Metal (S120)
Will your rom support AD2SDX by Technolover?

Edited by fabiorino, 16 April 2012 - 08:34 AM.

  • 0

#138
Lens_flare

Lens_flare

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,504 posts

Will your rom support AD2SDX by Technolover?


I don't actually know if that is kernel-related.. let's forget about old kind techno, meet new one - hopefully standing on cm kernels way.

  • 0

#139
Skynet94

Skynet94

    Newbie

  • Members
  • Pip
  • 34 posts
  • Devices:Acer Liquid Metal

I don't actually know if that is kernel-related.. let's forget about old kind techno, meet new one - hopefully standing on cm kernels way.


Len's but you can improve Technolover's kernel performance?? With his kernel our Liquid Metal can do 53 FPS and everything it's more fluid... You can do this?

  • 0

#140
Lens_flare

Lens_flare

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,504 posts
don't also forget that I'm always on step over -___-
as I stand before, mine kernel has near the same features, except of controls.. other is placebo.
please don't ever mention kernel.. just keep in mind that it is improving from day to day ;]

Edited by Lens_flare, 16 April 2012 - 03:00 PM.

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users