yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] bemymonkey:
OK, that sounds like a different symptom then. Definitely not the problem I'm having...
[Desire Android Development] sykopompos:
They are manual builds still, I don't have cron set to build at a certain time. I just have a build script that runs the commands and uploads for me. (Btw, I am still making these by myself) can I modify them, yes, do I want to, no, that would go against putting out a snapshot of the current source

(if you have problems then try a wipe or a fix permissions. if you don't take the time to read a few posts before you ask a question expect to be blown up on)
[Desire Android Development] the_truth:
Issues B #51

HTC BravoC (USCC Branded)

Coming from Stock but rooted/s-off Sense 2.1 rom (unrEVOked)

Wiped Data

Wiped Cache

Wiped Dalvik cache

Fixed permissions

Phone sits at HTC logo indefinitely; Does not boot. Is this me, or is there an issue in build 51?

Issue in B #51?

Going to try B #49 since people seem to have decent luck with 48-49
[Desire Android Development] bemymonkey:
Sounds good to me. Thanks for making the builds available to the rest of us :)

#51 is running just fine here. GSM though...
[Desire Android Development] Roscopcoletrain:
Trackball wake doesn't seem to work on 51. All else is good so far
[Desire Android Development] the_truth:
Any insight into what I may be doing wrong then?

Process:

Copy rom/gapps to sd card

Reboot to clockwork

Wipe Data

Wipe Cache

Wipe Dalvik Cache

Install rom (completes)

Install gapps (completes)

Reboot

I sit at the HTC logo for at least 10-20 minutes, no cyanogen load screen. Just hangs.

Attempted fix permissions in clockwork on both build 49 and build 51 after unsuccessful boot with no luck.
[Desire Android Development] bemymonkey:
Works, just not right after the screen's timed out, for some reason.

@truth: No ideas :(
[Desire Android Development] cTrox:
Last week I had the same problem, I was just stuck at the splashscreen. I also noticed that flashing was taking way longer than before. So I formatted system and boot, and flashed my rom again and it was fast again plus it booted just fine!
[Desire Android Development] marinierb:
Try formatting BOOT, SYSTEM, CACHE and DATA from the recovery menus and re-install.

And which HBOOT are you running? The Alpharev HBOOTs have different partition sizes. The one you are using might have a system partition that is too small.

And make sure your phone is GSM :)
[Desire Android Development] sykopompos:
I am unsure of bravo but you radio or bootloader might not be up to date. Also you might have had a bad download so try a new one and see what happens but hanging on the HTC would mean the kernel is not loading
[Desire Android Development] sykopompos:
Bravo is gsm, bravoc is cdma version
[Desire Android Development] the_truth:
I have HBOOT-0.98.0000

Radio-2.05.10.06.29

SLCD version

I am fairly reluctant to go messing with radio as there is no RUU available for the SLCD us cellular desire (and won't be until 2.2 is released within the next 2 months)

I made sure to grab the BravoC versions, so it is not the gsm/cdma issue.

I tried the other items suggested by marinierb and tried build 51 again.

Apparently it is an issue with something in either boot or system partitions. I get the cyanogen 7 load screen. Thanks for the suggestion!

Is there anywhere that has a filesystem/nand map that shows where everything is stored? (bootloader etc...) Possibly even a hardware/software hierarchy?

I am really wanting to get into compiling my own distribution because I really like to customize things, but the information on android seems to be pretty scattered and disorganized.

Thanks in advance guys!
[Desire Android Development] Silence66:
got also the fast battery drain issue since build #48. one night and the battery is gone
[Desire Android Development] mad-murdock:
you couldnt be more wrong. gingerbread has made huge changes on the code base - you might have noticed few new features from users point of view, but under the hood a lot has changed. perhaps for honeycomb and tables, perhaps since it has to be done sometimes. guess the last last internals change was 1.5->1.6

well, some apps just run as they used before, some others create problems. like all media players had to be updated or show now picture. or like quadrant doesnt show anything. the more system-stuff a app does, the more likely it needed small gingerbread compatibility tweaks.

my kernel needs 1% in two hours with wifi and sync off, and about 3% per hour with both on, k9 polling each 5 minutes and pingchat push service - probably more - a lot of activity. 3% per hour is a damn great value.

trust me, if you got drain issues its one of your apps. if you got speed issues, i found some live wallpapers slow down the launcher a lot. and of course some widgets slow down the system a lot - but thats the same on froyo.

gingerbread is a damn fine rom, which increased some parts in speed significantly. thats why not that many major features. i am fine with that, knowing honeycomb is not that far away

cheers mate - hope you try a release candidate. sense is the bloatware - aosp is usually fine - cyanogen is the grand father of all roms and kernel patches. of course in untested nightly builds, there can be problems, but they are usually gone pretty fast.
[Desire Android Development] sykopompos:
Working on that right now and am trying to get it all linked together so we can get more people involved and have more options. I am starting work on a aosp project soon but have been having my resources taken up byt the cm7src builds so once the rc1 drops then I can devote my time to my project. I will be documenting it all and any help with experenced coders is helpfull as long as they are willing and able to share what they do (be able to explain what you did and document it for others)
[Desire Android Development] wackymix:
Bravo is GSM .

I also have a problem. My bloothot doesn`t work. any news about this working ?
[Desire Android Development] mad-murdock:
working here - i guess you mean bluetooth
[Desire Android Development] sykopompos:
Building guide

http://xdaforums.com/showthread.php?p=10635918#post10635918
[Desire Android Development] najar360:
i will learn to compile by myself

firstly first...ubuntu here i am!
[Desire Android Development] Roscopcoletrain:
Well after some time the trackpad wake just started to work. Nice lol!
[Desire Android Development] the_truth:
gridlock, thanks for the link to the building guide.

I am grabbing virtualbox and a copy of 10.10 (was going to just use my x86 mint vm, until you said that gingerbread requires x64)

I will say, I am not a big java guy by any means, but I figure I can pick it up. I mainly come from a C++/assembly background. At this point, I wish my assembly experience was in arm instead of mips! (honestly, who really uses mips anymore?)

First project... Convert my stupid contacts from the "My Contacts Backup" software that US Cellular forces you to use (instead of google sync). >.<

... To be continued!
[Desire Android Development] sykopompos:
If you got c++ then that is a valuble skill and new coders in android are always appreciated. I will be writing up in depth anatomy of android along with what is actually in the source and how to work with it soon :)
[Desire Android Development] JoeSixAtPack:
Well. I also run into battery drains using CM6.1, OpenDesire 4.0.36, etc.(*RIP*), thus, imho the problem is not related to GB.

It's exactly like so many people reported before. System suddenly (after running fine many hours - days) starts to consume ~40-60mAh in standby mode instead of 4-6mAh - used by AndroidProcess...

Sure, Sense is bloat-ware, but I did not run into the drain again so far... It's really confusing.

Unfortunately I have absolutely no idea how to "freeze" this situation in a log/protocol without changing the "environment" significant - like plugging in USB or turning on the display :mad:

Maybe someone else got an idea how to track down this behavior?
[Desire Android Development] d0msen:
Try aLogcat from the market ;-)
[Desire Android Development] fenderf4i:
CM7 builds fine on 32bit.
[Desire Android Development] sykopompos:
Read post 13/14 on the compiling guide
[Desire Android Development] fenderf4i:
CM7 builds on 32 bit. I do it on my 32 bit Core Duo with 32 bit Linux. They made a change with CM7 early on so that it could be built on 32 bit systems. Building straight from AOSP is a different story, but CM7 is fine.

I believe the same accomodation was made with CM6.
[Desire Android Development] sykopompos:
That is why I said that cm7 is highly modified in that post, I only heard of people doing it on early cm7 source and havng some very funky behavior
[Desire Android Development] mad-murdock:
my suggestion would be to flash cm6 or even cm7 after full wipe and only restore the apps you absolutly need. then test that setup for a small while. you cannot imagine how often the reason for all kinds of trouble is in fact an app. or two apps, which produce terrible results when installed both.
[Desire Android Development] hajen78:
Thats true, i have only had battery drain ones, and that was a app. I have treid every rom there is (almost) and i have treid many radios, kernels ect, but none of that has ever made battery drain, only apps.
[Desire Android Development] metalk9:
Hi, I don't like to criticise but there is already guide to building CM on cyanogenmod.com which is IMO a lot simpler and somewhat more accurate than this.
[Desire Android Development] Nickedynick:
From Twitter:

@ChrisSoyars - "Nightly builds are back, this time with moar bacon (CM7)."
[Desire Android Development] hajen78:
I sure hope that someone will continue building CM7 from Crackflashers ?
[Desire Android Development] sykopompos:
actually mine was up long before the wiki but up on gdocs and has had many other guides based off of it. Secondthe wiki is extremely outdated. Does not go in depth on what you are actually doing and is poorly put together
[Desire Android Development] erto90:
what means with "moar bacon??"
[Desire Android Development] sykopompos:
If nightlies are back than I can move onto my aosp project and let the nightlies do their thing
[Desire Android Development] ziggy1001:
Only guessing but http://mirror.teamdouche.net/?device=bravo

Has been cleaned up so maybe something will appear later:)

and

CyanogenMod Forum

> HTC Desire GSM

> HTC Desire GSM Experimental Mod [Nightlies] [CM7] Discussion of Nightlies Posted Yesterday, 11:47 PM by ciwrl

so looks imminent
[Desire Android Development] sykopompos:
Not tonight

http://buildbot.teamdouche.net/builders
[Desire Android Development] hheexx:
@cyanogen

Nightly builds are back, this time with moar bacon (CM7).
[Desire Android Development] ziggy1001:
But maybe

http://buildbot.teamdouche.net/

"Currently Building: Bravo"

http://mirror.teamdouche.net/?device=bravo&type=nightly :D:D
[Desire Android Development] marinierb:
Downloading now!

I assume a full wipe will not be necessary.
[Desire Android Development] najar360:
official cm7 build 1 already release.
[Desire Android Development] marinierb:
Now that CM nightlies are back, I would like to give my very sincere thanks to crackflasher for providing these nightly builds. Thank you very, very much!!
[Desire Android Development] najar360:
yeah, me too. thanks for helping us done a compilation. :):)
[Desire Android Development] sykopompos:
No problem guys, it was my pleasure
[Desire Android Development] bemymonkey:
Thank you so much for sharing your builds with us to hold us over until the nightlies have come out. You saved me from the shakes (nightly addicition is a bad thing) :D

Is your AOSP project going to be Desire compatible? I'd love to give it a shot when you're done, so give us a heads-up when the time comes :)
[Desire Android Development] KroonBerg:
Thank you crackflasher!

Thank you so much for sharing the nightly builds, really appreciate it!
[Desire Android Development] JoeSixAtPack:
Still draining without apps installed

Still no luck :mad:

I wiped, installed CM7build#1, gapps, Firerat-All-in-One script http://xdaforums.com/showthread.php?t=679572 and CurrentWidget and my system is draining again. It using around 40-50mAh with display switched off. Too bad.
[Desire Android Development] sykopompos:
I am hoping down the line it will be
[Desire Android Development] Tuborg68:
Thanks to Crackflashers for great builds!!

Now when there are CM7-nightys, is it better to download those? Will crackflashers builds continue as a separate project or will they be incorporated in CM7 nightlys?
[Desire Android Development] sykopompos:
Google teamdouche mirror for the download site. Crackflashers will be getting revamped and will continue on to other projects :)
[Desire Android Development] erto90:
These official nightly will have the possibility to update via OTA?
[Desire Android Development] bemymonkey:
No. Unless you count downloading via the Android browser and flashing the file directly on the device as OTA... :)
[Desire Android Development] Zhypr:
Is there a possibility to install the HTC keyboard in this rom?
[Desire Android Development] beidl:
Rom Manager Premium has such functionality.

@Zhypr: google for "HTC_IME mod" and install both the clicker and the actual keyboard apk.
[Desire Android Development] stingerpl:
Most probably ROM Manager premium will allow this (like with cm6)
[Desire Android Development] 12aon:
Thread Closed

I closed this thread as it's not in compliance with the GPL as it is applied on XDA. Closing your thread is standard protocol and is in not meant as a punishment just as a way to handle this quickly. You can contact me (for questions or because you are angry with me) by reporting this post. I'll send you a PM as well,

Sicerely,

12aon
[Desire Android Development] bemymonkey:
Tried jonasl's HCT_IME mod? http://xdaforums.com/showthread.php?t=624416
[Desire Android Development] gilmorenator:
For USB ADB issues check http://xdaforums.com/showpost.php?p=10054771&postcount=271 for resolution
[Desire Android Development] fenderf4i:
Do you mean the CRT screen off animation? It was never taken out of Bravo, it's been there all along. I believe it is the EVO and a few other phones that had problems with it.
[Desire Android Development] sykopompos:
Oh, well I didn't know it wasn't taken out. Ace, vision and glacier it was removed for sure so I was adding it back in
[Desire Android Development] gilmorenator:
It's been in all the Bravo builds - but your juggling so many balls its hard to keep track - keep up the good work :D
[Desire Android Development] sykopompos:
I am currently up to 8 devices and I am looking for me, the more balls I am juggling the happier I am. I don't like my mind being bored
[Desire Android Development] najar360:
So, if on 16 build, what do i need to do if want to upgrade to build 17?just flash or do i need to wipe cache only?
[Desire Android Development] sykopompos:
Just flash it, if you have issues or fc's then reboot into recovery and run a fix permissions in the advanced menu. If you still have any issues than do a wipe
[Desire Android Development] metalk9:
Does anyone else have problems flashing GB gapps. They wouldn't flash for me in amon-ra-2.01 but mounting /system beforehand fixed it :-)
[Desire Android Development] najar360:
just flash build 17 reboot. then reboot back to recovery, flash gapps, reboot.

nothing happen. any idea?
[Desire Android Development] sykopompos:
With what? With gapps, you might need to mount /system and /data to get them to flash correctly
[Desire Android Development] najar360:
thanks, it works.

anyway, what time usually bot do a compiling on CM source (eta in gmt). since we got diff time region.just want to make sure i have a latest build.
[Desire Android Development] sykopompos:
It is a script I run when I see new thing on @cmsrc on twitter which is a bot that tweets everytime something is changed in the source. A lot of new changes just happened so a build 18 will be out shortly.

Ps if you look in my sig you will see my twitter, since I am building for 8 devices, I am jumping back and forth to different threads trying to do support and all so best why to know about a build is twitter
[Desire Android Development] sykopompos:
I wanted to share some stats with you guys

56,129 downloads so far spread over 8 devices with 299.24 gigabytes transferred. Highest downloads in a day was 12/30/2010 with 20,876 downloads. Most download for is glacier with vision close behind then bravo and ace. Sholes doesn't have working gapps yet and problems with prox sensor and gps. Inc is having bootlooping issues and I think will be solved in build 18
[Desire Android Development] sykopompos:
Build 18 was delayed to get all the new commits into the source, this should be a major update and we should be seeing cm goodness now
[Desire Android Development] sykopompos:
Build 18 has cm parts, I think we can say we are in the cm7 alpha stage now :)
[Desire Android Development] sykopompos:
#crackflashers looks like we are gonna be making a new recovery.img later tonight too RT @cmsrc bootable_recovery/gingerbread - Koushik Dutta * da32b5 - readd ext2/ext3 format support.... http://bit.ly/gDlzSU

Looks like I am gonna have to run the crt script tonight after all so I get the new recovery.img which will give us ext 3 support back so we can flash back to froyo (as if we would want to know) but this should solve all gapps flashing problems
[Desire Android Development] sykopompos:
Ignore the last post. It was meant for the ace thread

Build 18 with cm parts will be upload in about an hour for you guys
[Desire Android Development] ziggy1001:
Thanx D/L now ;)
[Desire Android Development] sykopompos:
Build 18 is up now
[Desire Android Development] guru_root:
That's good news, I am trying it now :D
[Desire Android Development] ziggy1001:
Can anyone confirm b#18-bravo-cm7src is ok wouldn't flash for me and at 67,768 Kb seemed a bit small
[Desire Android Development] fenderf4i:
It probably wasn't finished uploading. Try downloading it again.
[Desire Android Development] ziggy1001:
Well spotted it's now 75 MB:o
[Desire Android Development] guru_root:
Still does not have all the cm stuff .. quadrent 2d test isn't working .. is this already discussed
[Desire Android Development] sykopompos:
It is because of the native code that quadrant tests.

It is the start of the cm goodies not all of them prob not till we see a rc1
[Desire Android Development] guru_root:
Umm .. thank :-)
[Desire Android Development] spences10:
spences10 's a happy bunny

CM Parts YAY!!

Thanks for this, now my life has purpose again!!

:p
[Desire Android Development] sykopompos:
#crackflashers I am getting sleepy so I set the build script to loop, I just started now for build 19 and when it is done in 4 hours it will repo sync again to pick up anything that cames in after 3 to about 7 am est for build 20. If there are no commints after 3am est then you don't need to worry about flashing 20
[Desire Android Development] najar360:
Do you know how to activate a2sd+?or is it still not available?
[Desire Android Development] najar360:
and got one more question, how can we move dalvik cache from data partition to cache partition?
[Desire Android Development] BlackWhiteOne:
as far as I know there is no available a2sd under this seires cm7 build. dt and firerat do not work at all.
[Desire Android Development] FrancisFuku:
As a matter of fact, you can at least use dtapps2sd with these early CM7 builds : http://xdaforums.com/showpost.php?p=10170065&postcount=744 . I've tested it with build #19, and it works flawlessly.
[Desire Android Development] worstenbrood:
This is because the init.rc script in the boot ramdisk doesnt create a /sd-ext folder and run-parts is not executed, although in this rom there is a script called /system/bin/sysinit, but it doesnt seem to work.
[Desire Android Development] najar360:
i try to flash on build 18 and 19,both fail. i stuck at white htc logo. any idea?

do i need to change ext?im using amon ra.
[Desire Android Development] Narfx:
Tried #19, almost everything works perfectly. Only a couple of issues:

- Trackball wake doesn't work, even when selected in CMParts (trackball unlock does, though).

- The mobile network switch behavior is a bit erratic.

And of course the jerkiness when scrolling desktops or opening the app drawer, that will hopefully be fixed with the N1 OTA.

Thanks for compiling it! :)

PD: Also, my sdcard was not mounted in the first boot after flashing. Rebooting fixed the issue.
[Desire Android Development] worstenbrood:
The thing is, dtapps2sd takes alot of space, so you need to clean the rom a bit (i removed pinyin and openwnn (app en libs)), this is only necessary on n1 table. Flash the cleaned rom, flash the ramdisk, flash dtapps2sd, flash gapps. Should work then, it does here.
[Desire Android Development] najar360:
if i want to use firerat

clean flash rom -> flash ramdisk -> flash firerat ->flash gapps ?

do i still need remove pinyin?what other app do i need to remove?

edit : still it wont work. stuck at htc logo after flash ramdisk
[Desire Android Development] worstenbrood:
make sure you add 99complete from dtapps2sd to your init.d

edit: Added a fixed update zip which includes the 99complete script.
[Desire Android Development] najar360:
I stuck at htc logo after flashing ramdisk. How do i need to proceed flashing dt while i stuck at htc logo after flashing ramdisk?
[Desire Android Development] worstenbrood:
flash ramdisk then dtapps2sd without booting in between... just flash em straight after each other. Or flash the fixed update ramdisk one post back and boot, then go back to recovery and flash a2sd
[Desire Android Development] najar360:
Thanks, it works!! During update nightly w/o wipe. Do i need to this again?
[Desire Android Development] catohagen:
Thank you very much :D worked here
[Desire Android Development] worstenbrood:
Are you using dtapps2sd ? Anyway, you have to flash the ramdisk update after each update, unless they ever integrate it again in cm. If you're using dtapps2sd you have to flash that also every time after an update, so: flash cm update, flash ramdisk update, flash dtapps2sd, ...
[Desire Android Development] FrancisFuku:
For some reason, my Desire became really unstable when I flashed the #18 and #19 build. ADWLauncher was very unresponsive, the scrolling in the app drawer was incredibly laggy (and I'm not talking about the slight jerkiness that all Gingerbread ROMS have), and my phone rebooted three or four times in an hour. I flashed back the #16, and everything works flawlessly.
[Desire Android Development] bemymonkey:
So how much CMParts has been ported already? Is the automatic backlight and custom lock screen already there? :)
[Desire Android Development] fenderf4i:
It sure is! The only thing I've found not working yet is trackball wake. Otherwise I have my lock screen gestures set up and everything else.
[Desire Android Development] bemymonkey:
Awesomeness. Maybe I'll give it another try tomorrow :)
[Desire Android Development] guru_root:
works great .. But, the home screen freezes after a while in #18 ... testign #19 now and will wait for #20 ;-)
[Desire Android Development] fenderf4i:
I haven't tried 18 or 19, I compiled my own build this morning and it's running great, not sure what the problem could be.
[Desire Android Development] nanujra:
@fenderf4i:

I clicked on the n1 partition instructions link in your sig. Are those instructions to move the davlik cache from /data to /cache?
[Desire Android Development] fenderf4i:
No, it just repartitions you from

/system 258MB /cache 41MB /data 152MB

to

/system 149MB /cache 98MB /data 203MB Like a stock Nexus One. You can't run a Sense ROM with it, it's for AOSP ROM's. There's also a partition layout that increases the /data to 261MB, but with a /cache 10MB you have to fastboot radio files.

Also, my instructions are for if you already have Cyanogen installed and you want to restore your backup. If you do a fresh install, it's much more straight forward.

http://alpharev.nl/
[Desire Android Development] worstenbrood:
I think because its getting too big for the n1table, im getting random crap too, now that i stripped out the useless stuff it works flawlessly.

Sent from my HTC Desire