1624 replies to this topic

[Ennon]

Ah, I figured it out. To install CWM3:

(I did this in-rom. It *should* work while in bootloader or recovery too though.)

adb shell
flash_image recovery /sdcard/<your cwm3 image>.img

Boot into recovery and it should be loaded

Not a fan of the orange though haha

Ellingsoc, on 19 January 2011 - 01:31 AM, said:

What is eui installer I don t recall seeing anything on this before ennon. What does it do!

Ennon's Unified Installer (EUI) is third-party-installer that optimizes the installation process using official files that come from their respective developers (Read: No re-packaged crap). It's more of a proof-of-concept right now, but it is a good starting point for future endeavors I have planned

http://supermod.net/...topic,17.0.html

[Grumpy Bastid]

FordThunder, on 19 January 2011 - 01:12 AM, said:

anyone know how to flash the cwm3 ?
since we dont have fastboot on the cdma desire.

The way I did it was I copied the new recovery image into the pb99zip used to flash a new custom splash screen. (remember to remove the splash image though) rebooted into recovery and voila it flashed the new recovery image without any issues.

[FordThunder]

thanks ennon , your the man !

[Ellingsoc]

Where do we find the cwm3 iamges at?

Ennon, on 19 January 2011 - 01:50 AM, said:

Ah, I figured it out. To install CWM3:

(I did this in-rom. It *should* work while in bootloader or recovery too though.)

adb shell
flash_image recovery /sdcard/<your cwm3 image>.img

Boot into recovery and it should be loaded

Not a fan of the orange though haha



Ennon's Unified Installer (EUI) is third-party-installer that optimizes the installation process using official files that come from their respective developers (Read: No re-packaged crap). It's more of a proof-of-concept right now, but it is a good starting point for future endeavors I have planned

http://supermod.net/...topic,17.0.html

[FordThunder]

anyone getting a lot of "download unsuccessful" from app market downloads ?

[FordThunder]

nightly-4 is up ...

[Ennon]

Ellingsoc, on 19 January 2011 - 02:17 AM, said:

Where do we find the cwm3 iamges at?

Kali-, on 18 January 2011 - 01:12 AM, said:

no one is coming on #teamdesire
2nd try here

THIS IS COMPLETLY UNTESTED ON CDMA BUT WORKS FINE ON GSM

this is an unofficial App2SD
CyanogenMod do not officially support a2sd, but i made an init script for it (very cutted down version of Firerat 857byte)
Only move /data/app and /data/app-private on SD, if u already have app installed on your /data they will be moved on SD
what u need:
1) CWM3
2) One EXT[234] (ext4 is recommended, ext3 works fine too, ext2 is not recommended because lack journal) partition on SD with "sd-ext" label (without quote)
3) data2sdext-signed.zip  

the "sd-ext" label is automatically added by cwm3 when u create a new partition layout but if u already have sd-ext partition just add the label.

from "official" cm7 nightlies run:

adb shell e2label sd-ext /dev/block/mmcblk0p2

or open a terminal and write

su -
e2label sd-ext /dev/block/mmcblk0p2

or on cwm3 (should work on cwm2 and amon ra)

adb shell tune2fs -L sd-ext /dev/block/mmcblk0p2

http://dl.dropbox.co...voc-3.0.0.5.img

Bottom link

FordThunder, on 19 January 2011 - 02:13 AM, said:

thanks ennon , your the man !

Noo problem mate

FordThunder, on 19 January 2011 - 02:29 AM, said:

anyone getting a lot of "download unsuccessful" from app market downloads ?

@Kali, you were right lol. But why would CM work fine without cache in Froyo/CM6 and not GB/CM7? I'm confused :/

@FordThunder: Try market downloads WITHOUT using cMTD and see what happens. Kali warned a couple pages back that the low cache partition settings for cMTD would bork market downloads

[Ellingsoc]

Ennon, on 19 January 2011 - 03:21 AM, said:

Bottom link



Noo problem mate



@Kali, you were right lol. But why would CM work fine without cache in Froyo/CM6 and not GB/CM7? I'm confused :/

@FordThunder: Try market downloads WITHOUT using cMTD and see what happens. Kali warned a couple pages back that the low cache partition settings for cMTD would bork market downloads

Sweet thanks got it installed so what all does this change for us if anything really?

[Grumpy Bastid]

Has anyone successfully gotten the unofficial Ap2sd to work? It appears that its calling for bravo instead of bravoc:
This is the output I'm getting when I try to flash it.
assert failed: getprop("ro.product.device")=="bravo" || getprop("ro.build.product")=="bravo" || getprop("ro.product.board")== "bravo"
e: Error in /sdcard/datat2sdext-signed.zip
(Status 7)
Installation aborted.

[Ennon]

Ellingsoc, on 19 January 2011 - 03:32 AM, said:

Sweet thanks got it installed so what all does this change for us if anything really?

No idea lol. Something about adding ext4 support to recovery? But I'm not seeing anything like that.

Uh. . . It's now orange. Haha, that's the only thing that I can visually see that's different with CWM3.  

But hey, it's an upgrade to the latest software, so why not

Grumpy Bastid, on 19 January 2011 - 03:41 AM, said:

Has anyone successfully gotten the unofficial Ap2sd to work? It appears that its calling for bravo instead of bravoc:
This is the output I'm getting when I try to flash it.
assert failed: getprop("ro.product.device")=="bravo" || getprop("ro.build.product")=="bravo" || getprop("ro.product.board")== "bravo"
e: Error in /sdcard/datat2sdext-signed.zip
(Status 7)
Installation aborted.

I haven't looked at Kali-'s a2sd. But looking at that error you posted, it looks as if Kali- forgot to change the assert from "bravo" to "bravoc"

It won't work because it fails the phone model check, thus resulting in recovery's vague "Status 7" error.

[FordThunder]

think i will resort back to cm6 and let some of the bugs get worked out first before i stay with cm7 ... i cant live without cMTD and apps2sd

[prgmnd]

This is getting really frustrating.  I seem to be the only one that doesn't get any sound from the speakerphone in CM7.  I've been going back and forth between 6 and 7 for 3 days trying to figure it out, and all I've found is a couple differences in logcat and kmsg output, but I don't know what it means.

Just loaded nightly 4, and I see this line in logcat on start up, near the beginning:

I/AudioHardwareQSD(  115): voice volume 0.000000 (range is 0 to 0)

Where on 6.1.1, I see

I/AudioHardwareQSD(  124): Setting in-call volume to 5 (available range is 0 to 5)

The only other difference I've noticed is in kmsg, when audio should be playing, in CM7 I see:

<6>[  286.381256] pcm_out: open
<6>[  286.382263] acdb: 864 bytes for device 607, rate 48000.
<6>[  290.481323] pcm_out: release

Where in 6.1.1 I see:

<6>[   97.121398] pcm_out: open
<6>[   97.121856] acdb: 864 bytes for device 607, rate 48000.
<6>[   97.288452] tpa2018d1_set_speaker_amp: ON
<6>[  101.260559] tpa2018d1_set_speaker_amp: OFF
<6>[  101.268829] pcm_out: release

Does that mean anything to anyone?

[Ennon]

FordThunder, on 19 January 2011 - 04:26 AM, said:

think i will resort back to cm6 and let some of the bugs get worked out first before i stay with cm7 ... i cant live without cMTD and apps2sd

I haven't switched over yet either

prgmnd, on 19 January 2011 - 04:38 AM, said:

This is getting really frustrating.  I seem to be the only one that doesn't get any sound from the speakerphone in CM7.  I've been going back and forth between 6 and 7 for 3 days trying to figure it out, and all I've found is a couple differences in logcat and kmsg output, but I don't know what it means.

Just loaded nightly 4, and I see this line in logcat on start up, near the beginning:

I/AudioHardwareQSD(  115): voice volume 0.000000 (range is 0 to 0)

Where on 6.1.1, I see

I/AudioHardwareQSD(  124): Setting in-call volume to 5 (available range is 0 to 5)

The only other difference I've noticed is in kmsg, when audio should be playing, in CM7 I see:

<6>[  286.381256] pcm_out: open
<6>[  286.382263] acdb: 864 bytes for device 607, rate 48000.
<6>[  290.481323] pcm_out: release

Where in 6.1.1 I see:

<6>[   97.121398] pcm_out: open
<6>[   97.121856] acdb: 864 bytes for device 607, rate 48000.
<6>[   97.288452] tpa2018d1_set_speaker_amp: ON
<6>[  101.260559] tpa2018d1_set_speaker_amp: OFF
<6>[  101.268829] pcm_out: release

Does that mean anything to anyone?

Hmm, interesting. Did you try the latest nightly? To me, it looks like a kernel/driver (does Android have drivers? lol) issue. However, you're the only one being affected, so that doesn't make much sense.

[seve1476]

Ennon, on 19 January 2011 - 01:50 AM, said:

Ah, I figured it out. To install CWM3:

(I did this in-rom. It *should* work while in bootloader or recovery too though.)

adb shell
flash_image recovery /sdcard/<your cwm3 image>.img

Boot into recovery and it should be loaded

Not a fan of the orange though haha



Ennon's Unified Installer (EUI) is third-party-installer that optimizes the installation process using official files that come from their respective developers (Read: No re-packaged crap). It's more of a proof-of-concept right now, but it is a good starting point for future endeavors I have planned

http://supermod.net/...topic,17.0.html

Noob question:

Do you put the image directly on the root of the SD card and type the above script using "terminal emulator"?  

thanks

[Ennon]

Ah, no. And yes.

I didn't think about it, but yeah terminal emulator would work. Just type

flash_image recovery /sdcard/<your cwm3 image>.img

In term. after putting that file on your sdcard. That will work too. If you get an error, ignore it and boot to recovery to see if it worked anyway.

[seve1476]

Ennon, on 19 January 2011 - 05:23 AM, said:

Ah, no. And yes.

I didn't think about it, but yeah terminal emulator would work. Just type

flash_image recovery /sdcard/<your cwm3 image>.img

In term. after putting that file on your sdcard. That will work too. If you get an error, ignore it and boot to recovery to see if it worked anyway.

Didn't work....do you have a "space" after image, recovery?  I put image to root of sdcard....

[FordThunder]

ok , this might be a silly question but ..

since cm7 seems not to play real well with cMTD , what is the factory /cache partition size ?

i was thinking i would set the cMTD : mtd {size of rom} {cache to default size}

[dollabillz217]

Has anyone else running the HTC Desire BravoC noticed that under about my phone now there is a processor status that wasn't there before?  Not sure if this has anything to do with that, but my phone seems to run extremely hot since I've flashed the nightly build 2 yesterday.  Actually it was running so hot that I flashed back to my 6.1.1 stable because I didn't feel like melting my cpu was a great way to test anything in the future :-)

[arueder]

ciwrl, on 16 January 2011 - 11:39 PM, said:

Given the recent explosion of nightly users, I understand your need for a place to discuss them, and/or ask if other users are having similar issues as you...this is that place

1) DO NOT: Post to the bug tracker
2) DO NOT: Open another thread (I will enforce this with temp bans)
3) DO NOT: Think of this as official forum support; this thread will be strictly user to user support. Don't expect CM-dev help.

** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading 
** cause of male impotence.

Download: http://mirror.teamdo.../?device=bravoc
Gapps: http://android.d3xt3...0115-signed.zip
Changelog: http://twitter.com/cmsrc

When installing CM7, will I have to wipe everything then install gapps, then gapps process one, then the rom, then gapps process two, then the cmtd patch? Can't find ennon's instructions anymore, link seems to be down.

[Ellingsoc]

Yes those are the steps you need to do and iam using this as my day to day and it does not get hot maybe warm when I use it alot