[NIGHTLY][ROM][GWK74] CyanogenMod 7 for vendor Bravo (HTC Desire GSM)
- Thread starter Kali-
- Start date
This is what I'm getting , screenshot
Sent from my HTC Desire using XDA App
But have you got EXT3?
Fresh install and used Data2SD used by Droidzone's ROM. Let's see if it's gonna behave well.
via xda app
via xda app
Is it working well?Fresh install and used Data2SD used by Droidzone's ROM. Let's see if it's gonna behave well.
via xda app
Sent from my HTC Desire using XDA App
If worked but I experienced some app FC's without the usual FC message. It's probably my sd card not up to the task. It's worth a try if you think your sdcard can handle it. Went back and use the S2E.
Oh yeah, the built-in kernel included with the rom doesn't seem to support EXT4 still. I flashed ManU's kernel and I got my ext4 partition detected.
i have an ext4 and this rom work well..
my setup:
-cm7 hboot
-stock kernel
-kali a2sd script
-ext4 512 mb
-about 90 apps installed (80 MB free on internal memory)
everything working fine..i just modified the file /system/etc/init.d/05mountsd changing the word ext3 to ext4..simply as that before to flash the zip
so the stock kernel and the kali script support the ext4, but the script inside the rom mount the sdext as ext3 (if u wanna use an ext4 change it as i did)
let's talk back about the rom and not the scripts
Last edited:
There is one place where I've been witnessing a FC: the DSP manager FCs when I receive a call (it seems it happens mostly the first time after a reboot). As in - I start the phone (or restart it), receive a call, and on the screen I get a FC error. I have to close it before being able to answer the call (or seeing who is calling).
Once I've closed the error, it doesn't seem to show up again (I don't receive many calls as such)
Once I've closed the error, it doesn't seem to show up again (I don't receive many calls as such)
The last nightly build works very well.
I have only a force close that is followed by a reboot when I try to log in in Skype.
I think that this nightly release use the battery in a different way in comparison with the 262 build... the battery seems last less than the usual but is only my first impression.
I have only a force close that is followed by a reboot when I try to log in in Skype.
I think that this nightly release use the battery in a different way in comparison with the 262 build... the battery seems last less than the usual but is only my first impression.
CM70 20120225-Nightly doesn't seem to play well with ManU 2.1 HAVS... to me at least. When I undervolt it to the usual values I had it with v261 nightly, I get random reboots and app restarts. I haven't tested it with the default voltage values for ManU 2.1 though but I do find the voltage values a tad bit too high.
I'm currently using the built in CM7 kernel and its seems stable. Battery drain's quite a bit I think...
Anyone had any issues with the ManU kernel with this nightly?
I'm currently using the built in CM7 kernel and its seems stable. Battery drain's quite a bit I think...
Anyone had any issues with the ManU kernel with this nightly?
Just downloaded it now, can you upload or give me your undervolt values so i can test along with you.
Will only be able to give you an answer after i get home from work, which is in about 4 hours.
Just in case, what app are you using to undervolt???
I use IncrediControl app as suggested by EV. I just adjust all the lower threshold values several steps down until the 245MHz frequency is set to 900mv.
I leave the upper threshold for each frequency as is. Ondemand governor using 245MHz-998Mz
This config works fine on Nightly v261 but given the fact that there are a ton of changes between that and this last nightly, they might have made some changes?
The battery is working fine at this moment.
Yesterday afternoon (4.00 PM Italian Time Zone) I do a full charge and I used my phone for playing mp3 for more or less two hours I browsed some internet pages in 3G (on a Bus while I was travelling for more or less 110 km) and I used the wlan connection for the rest of the time until now... and after 23 hours I have yet the 48% of my battery.
So my first impression about battery draining was wrong.
I use the last nightly build but I prefer to use another RIL (the HTC-RIL 2.2.0028HM) and the 32.56.00.32U_5.17.05.23 Radio version.
The governor I use is Interactive (245-1113 MHz).
I hope that my data could be useful for other users.
Yesterday afternoon (4.00 PM Italian Time Zone) I do a full charge and I used my phone for playing mp3 for more or less two hours I browsed some internet pages in 3G (on a Bus while I was travelling for more or less 110 km) and I used the wlan connection for the rest of the time until now... and after 23 hours I have yet the 48% of my battery.
So my first impression about battery draining was wrong.
I use the last nightly build but I prefer to use another RIL (the HTC-RIL 2.2.0028HM) and the 32.56.00.32U_5.17.05.23 Radio version.
The governor I use is Interactive (245-1113 MHz).
I hope that my data could be useful for other users.
I use the same set up, if 900mv is your starting point, by what increment do you increase your voltages - from 900mv to 925mv for the next clock speed?
As i am going to use this procedure!
The battery is working fine at this moment.
Yesterday afternoon (4.00 PM Italian Time Zone) I do a full charge and I used my phone for playing mp3 for more or less two hours I browsed some internet pages in 3G (on a Bus while I was travelling for more or less 110 km) and I used the wlan connection for the rest of the time until now... and after 23 hours I have yet the 48% of my battery.
So my first impression about battery draining was wrong.
I use the last nightly build but I prefer to use another RIL (the HTC-RIL 2.2.0028HM) and the 32.56.00.32U_5.17.05.23 Radio version.
The governor I use is Interactive (245-1113 MHz).
I hope that my data could be useful for other users.
That is pretty impressive battery life your getting.
I can barely barely make it from 06H00 to 17H00 on 1 charge, just popped it in on charge now @ 30% left?
You can PM me with your method you used to get this, as this thread is for CM nightly discussions and not battery life.
Thanks
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
102This thread is reserve for nightly build of CyanogenMod Rom for HTC Desire
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:** 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.
What are Nightly build? Auto compiled build of the latest CyanogenMod source from github. This version change each night and aren't officialy supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
Warning : Not for new user, flash this build only if you know what you are doing !!!
INSTRUCTIONS:
- First time flashing CM 7 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery.
2. Do a Nandroid backup!
3. WIPE (wipe data/factory reset + wipe cache partition)
4. Install the ROM
5. Optionally install the Google Addon
- Upgrading from earlier CM7?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://download.cyanogenmod.com/?device=bravo
before flash is recommended to check the md5sum
CyanogenMod Enhancement:
ChangeLog / Twitter
Device specific ChangeLog by igor.tonky
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!51cm7 is in a development stage and for the first installation i recommend to:
1) install rom
2) reboot, skip setup wizard and setup your access point
3) reboot recovery and install gapps
4) start and follow setup wizard, when requested select desired gapps to be downloaded from market
Battery drain issue:
Set wifi sleep policy to never
settings -> wireless & networks -> wifi settings
press menu -> advanced and set wifi sleep policy to Never
press menu -> save
RIL issue:
Switching RIL is cause of know network problem:
* Unable to make a network scan
* Data connection die on asleep (only for some carrier)
CM7 HBOOT by Alpharev | xda thread
Change partition table size 130/5/302 (system/cache/size)
Require nightly #18 or newer
Upgrade instruction:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl-cm7.img'
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything, advanced restore system & data, install CM7 again (same version or a newer one).
Legacy App2SD Addon:
CyanogenMod do not officially support a2sd, i'm working on it because desire (not only) desperatly need it (cutted down Firerat script)
Bootloop free: bind mount do not cause bootloop
Zero Maintenance: no maintenance required after ROM update
Other a2sd can be used, this is just the easiest way: use recovery to partition your SD then install cm7_legacy_a2sd_rX-signed.zip
By default only App will be moved on SD
Optionally Cache and Data can be moved to SD, but is not recommended (guide)
Require GB Nightly #7 or newer
It's recommended to set the install location to "Internal" under Settings -> CyanogenMod -> Application Settings -> Install location
Before install check if /sd-ext is mounted, "quick system info" under A2SD Storage should report Total and Free space, if it report "information not available" format sd-ext from recovery.
r3: improved installation process (i hope)
r2: added data2sd and cache2sd as options
r1: first release
General App2SD Q&A:
Q: A2SD is recommended?
A: Internal storage perform better than SD, install A2SD only when low disk space warning happen
Q: How to check if is working?
A: run:
adb shell
df -h | grep /dev/block/mmcblk0p2
output should be
Q: I have installed a2sd addon but now i get low space warning again, why?Code:Filesystem Size Used Available Use% Mounted on /dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /sd-ext /dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /data/app /dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /data/app-private
A: by default a2sd addon move only app, this is fine for most user but some user with more application have to move also cache and/or data.
Cache2SD can be enabled with
adb shell
/sd-ext/userinit.d/10cache2sdext-binds enable
Data2SD
adb shell
/sd-ext/userinit.d/11data2sdext-binds enable
reboot when prompted
HBOOT
All alpharev's hboot are compatible except the oxygen version
CM7 version is recommended ~270MB for app (stock 110MB, N1 195MB)
HowTo
Perform automatic backups of files in /system/ while (re-)flashing CyanogenMod
useful link
http://goo-inside.me/google-apps/
md5:
18ef81c567398a93183aff65a41a1565 cm7_legacy_a2sd_r3-signed.zip11130/5/302 hboot is available on alpharev site
this hboot require nightly #18 or newer
this is the alpharev instruction, extended for user who already have cm7 and want to change partition layout without wipe (just slight changes on point 6):
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img' (change into the correct filename for the HBOOT you downloaded)
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything, advanced restore system & data, install CM7 again (same version or a newer).
Big thank's to ieftm & kmdm8new semi-official nightly build
(to replace the buildbot auto builds)
mirror1: cm_bravo_full_teamdesire-20110601-1925.zip size: 84M (88037737 bytes)
mirror2: cm_bravo_full_teamdesire-20110601-1925.zip md5sum: 38591bab5df5d8f57e714f7888567bdb
have fun with this - lets hope official nightlies are soon back. after 2nd hdd crash in about 2 month, chris is doing durability tests with the new harddisks first - to make sure, they dont crash again in near future.
btw: if you refer to this later on, remember, those links are on first page, third post - much more easy to find than "search a few pages back"
btw2: you bravo guys do a LOT more downloads than i get on my ace and vega builds - thats why i included bravo in todays build cycle - even though i gotta hit a civ5 lan at friends time to go now...7my dear old bravo friends, i miss you! unfortunately time doesn't allow to read this thread too often. so much happening here. see my current primary project in signature to get a clue what keeps me busy most
but since no nightlies for 3 days, i remembered you and myself some months back. and i remembered how this would have driven me insane.
get my nightly build here:
cm_bravo_full_teamdesire-20110326-1142.zip md5sum: c38983df1fe50c1c511b18fd03b31d55
even though i got no bravo to test, i am pretty confident it should work as intended! just handle it like any other nightly you usually flash.
for the people that dont know me: i started my android career with a bravo device which i later sold and used the money to buy a (very cheap) ace/desire hd.
i am a cm dev for a while and a member of teamdouche. so i usually know what i am doing. i only do those builds for ace and bravo in case there was no nightly and i got the time to build/upload one.
the reasoning is simple: i was nightly addicted, too. and it sucks to have no build in the morning. especially for multiple days.
