• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

[ROM][beta]CyanogenMod 9

682 posts in this topic

Posted

Has audiolib (this for call micro) been repaired?

why not to ask privately? :D

ok, I don't know, just reverted to source that I might compiled with alpha..

0

Share this post


Link to post
Share on other sites

Posted

When there is a new beta?

0

Share this post


Link to post
Share on other sites

Posted

When there is a new beta?

when its ready... see lens' signature.

0

Share this post


Link to post
Share on other sites

Posted

why not to ask privately? :D

ok, I don't know, just reverted to source that I might compiled with alpha..

any news about the last fixes?

i'm very impress of your work!!!wink.gif

0

Share this post


Link to post
Share on other sites

Posted

see lens signature -__-

no updates on it-no time for it, or just no updates for it :P

0

Share this post


Link to post
Share on other sites

Posted

see lens signature -__-

no updates on it-no time for it, or just no updates for it :P

so... can you win the war?tongue.gif

0

Share this post


Link to post
Share on other sites

Posted

first I should have an exterminatus possibility :P

0

Share this post


Link to post
Share on other sites

Posted

first I should have an exterminatus possibility :P

lol... i'm impatient to see your next work!!!laugh.gif

could you tell me something about mobile data?

thanks!

0

Share this post


Link to post
Share on other sites

Posted (edited)

there are no ril class that flawlessly matches our device now.. so seems I should rewrite lgeqc ril class to make data work.

Edited by Lens_flare
0

Share this post


Link to post
Share on other sites

Posted

there are no ril class that flawlessly matches our device now.. so seems I should rewrite lgeqc ril class to make data work.

I'll send a couple of Chianti bottles for that :)

Sent from my Liquid MT using Tapatalk

0

Share this post


Link to post
Share on other sites

Posted (edited)

I'll send a couple of Chianti bottles for that :)

Sent from my Liquid MT using Tapatalk

amarone is much better :P

Edited by chemicalbuz
0

Share this post


Link to post
Share on other sites

Posted

amarone is much better

Why not brunello di Montalcino or a fine taurasi?

The only problem would be that I'd have to sell the liquid metal to buy it :P

Sent from my Liquid MT using Tapatalk

0

Share this post


Link to post
Share on other sites

Posted

For lens, a good lambrusco is better! lol

0

Share this post


Link to post
Share on other sites

Posted

I'm writing to you because I'm an embedded GNU/Linux & Android developer and I'd like to help in porting ICS to the Liquid Metal.

if so I'm hiring you to make gingerbread camera opensource(now using whole acer camera libs). Gingerbread source is on my github: http://github.com/Nikolas-LFDesigns .

it seems the only way to make camera work on ics, coz needed wrapper is just found, but desire z camera hal can't construct preview.

0

Share this post


Link to post
Share on other sites

Posted

added git repo with all fixes that has been done for now. One could compile it to achieve the next beta earlier -__-

0

Share this post


Link to post
Share on other sites

Posted

torch works, but only 2 sec...cooldown started, u'll better run bitches XD

0

Share this post


Link to post
Share on other sites

Posted

.cooldown started, u'll better run bitches XD

huh?

0

Share this post


Link to post
Share on other sites

Posted (edited)

huh?

meaning that after flash stop working your hardware will explode...but if i explain it it loose in awsomeness XD

Edited by guido89
0

Share this post


Link to post
Share on other sites

Posted

ah,you mean "you'd rather repair a data connection than torch?" -__-

ok, but torch is working via camera interface(torch constructs camera,connecting to it, and opens flash hw) so that it's just a side effect of fixing camera. I haven't run camera fully, that's why torch stopping to work after 2 seconds(camera opening fails with delay)

0

Share this post


Link to post
Share on other sites

Posted

ah,you mean "you'd rather repair a data connection than torch?" -__-

ok, but torch is working via camera interface(torch constructs camera,connecting to it, and opens flash hw) so that it's just a side effect of fixing camera. I haven't run camera fully, that's why torch stopping to work after 2 seconds(camera opening fails with delay)

no man, it was kinda joke @.@ the fact u specified that works only for 2 sec made me think 'bout films bomb timer XD it was not really refered to your work, sorry :D

0

Share this post


Link to post
Share on other sites

Posted

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

Share this post


Link to post
Share on other sites

Posted (edited)

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
0

Share this post


Link to post
Share on other sites

Posted

Hey Lens thanks for your work!!!

0

Share this post


Link to post
Share on other sites

Posted



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

Share this post


Link to post
Share on other sites

Posted

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

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.