yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] BlaqkAudio:
Try removing Market using Titanium Backup then reinstall gapps. Used to work for me when Google Voice would constantly FC after a ROM update
[Hero CDMA Android Development] Houndog101:
Yea, tried that. When verifying I get e:wrong digest:

META-INF/com/google.android/updater-script

E:Vitrifaction failed

install aborted.
[Hero CDMA Android Development] stayclean:
I had weird Market FCs when using the web market to do OTA installs. Market hadn't updated to 2.3.3, so I just opened TB, tapped on Market, hit "Clear data", then reopened Market, it updated itself, and works fine. Could work..
[Hero CDMA Android Development] stanltod:
The only thing I could suggest is flashing a Sense ROM like Fresh and doing PRL and Profile updates and making sure you can text and voice call. I had to do this with one of my first GB flashes. Then, NAND or flash back to AOSP GB. I also had some probs back when I did my first flash to AOSP GB. I couldn't get it to flash with CWM recovery 2.5.0.x so I updated to 3.0.0.5 and it flashed just fine with Firerats and everything. However, I later had probs where it seemed that 3.0.0.5 wasn't flashing right so I reflashed recovery back to 2.5.0.7, reflashed FR recovery mod onto it and now it all works great every time.

My current method for flashing (almost daily it seems, AOSP ftw!!!!) updates is simply boot to recovery, wipe dalvik, wipe cache partition (I don't format it), reboot to recovery, flash new AOSP GB zip, wipe dalvik, wipe cache partition, reboot to recovery, flash FR boot, heck maybe wipe dalvik and cache partition again if I think about it, reboot to system and it's all perfect. I assume everyone knows that you have to flash FR boot again every time AFTER you flash the ROM and before you have booted into system if you are using FR. Otherwise, it's boot loops and stuck boots until you do. With this method I never have to nandroid restore or TiBU restore.

I don't use any themes and no special settings in build.prop or anywhere. I use stock kernel and Firerats at 130 4. No FC, no market fix needed, no lag. I went to GoLauncher a couple of weeks ago because ADW kept restarting every time I went back to home screen. I don't like LP's crippling expiration practice. I know this phone stuff is all YMMV but my tank has been pretty full lately. I am with my Hero till Evo2 do us part.
[Hero CDMA Android Development] radrian92:
With all the updates it looks like we have two sets of nightlies 0_0!! Thank you aosp!!!
[Hero CDMA Android Development] il Duce:
what recovery do you have? I flash this with clockwork 2.5.0.1 every ROM release :confused:
[Hero CDMA Android Development] oldjackbob:
Duce, are you saying you still do everything with 2.5.0.1, and you've never gone to 2.5.0.7 or 2.6.0.1 or 3.0.0.5?
[Hero CDMA Android Development] ch1naski:
Ya know, I flashed 2.5.0.7 but it still says 2.5.0.1 .....

π
[Hero CDMA Android Development] il Duce:
Lol, I have tried them, ran 3 for a while, then remembered 2 was green, which makes me happy.

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] thoughtlesskyle:
The EVO battery life is awful its one of the big things I miss about my hero, I even have it underclocked
[Hero CDMA Android Development] CrashV2010:
Do you have the new or shifty evo ?

BTW - GREAT Work here Aosp !!!
[Hero CDMA Android Development] CIDRtheBITER:
Is bluetooth not working on this rom? I hoocked up my headset but people can't hear me.
[Hero CDMA Android Development] windtrader:
Market FC fixed

I tried all the posted suggestions here and on Firerat thread and could not get the Market FC to go away. Tried to remove Firerat partitions. I even tried to nandroid back to an older version and it still FC.

Decided something got corrupted very badly so reformat the SD card and start clean and it is working fine now with Firerat partitions set at 130 30.

Like I said I NEVER had any issues with FC so maybe just an odd unique error.

EDIT - I did more testing and think the issue is related to the size of the cache. When I had it set to 2 and 4 it failed, when set to 30 it seems to work fine.
[Hero CDMA Android Development] bongzilla:
is it possible to turn off haptic feedback on the lock screen?
[Hero CDMA Android Development] axled2:
Do any of you ever get it where you have to press one to connect your call after answering when someone is calling you? Just wondering if I'm the only one who this happens to. Any ideas for a fix?
[Hero CDMA Android Development] registeredmale:
What animations? :confused: Both links point to the same LCD density thread.
[Hero CDMA Android Development] dburg84:
I dont think so unless you check Menu unlock...no feedback. bongzilla...excellent band
[Hero CDMA Android Development] 24601:
Try menu > settings > CM settings > Input > Haptic feedback tweaks > Haptic feedback main (uncheck this setting).
[Hero CDMA Android Development] Brickster:
Ok, I must have got a bad download on 3-7 cause I never have problems like this....Home button dont work, wifi wont connect, bluetooth wont do nothing, I got 2 clockwork mods...hehe

Wierd cause the checksum matches and it looks like about the right size......lets see.....68.0 MB's ? <----hmm
[Hero CDMA Android Development] Kevets:
I had the home button issue once, a reflash fixed that.
[Hero CDMA Android Development] ULoveAriana:
Yeah I've been trying to find a way to have it off too! I even tried this ^^^ & it doesn't work either :(
[Hero CDMA Android Development] DJB628:
Should be 71 mb's if I recall
[Hero CDMA Android Development] Brickster:
Yea, I just saw that.......thus, the dingle-berries

Re-downloading and re-flashing now.....Thanks
[Hero CDMA Android Development] picklerick:
I just noticed that all the system@app .dex files are being created twice. Once in /data/dalvik-cache and once in /cache/dalvik-cache but the data@app ones are only being created in /data/cache. Should I just remove the file in /cache/dalvik-cache and make it not writable? having them twice is killing my space. I am using firerats mod.

EDIT: I think this might have been from a previous build, one of the march ones. I removed them and rebooted and they wasn't recreated.
[Hero CDMA Android Development] genuser:
Google voice I assume? Log in to your account and disable call screening.
[Hero CDMA Android Development] il Duce:
You could just get rid of the sliders altogether, lockscreen gestures ftw.

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] il Duce:
Which ones did you delete?

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] genuser:
OverClocking Advice

How are you all overclocking this ROM? CM Settings, SetCPU or OC Widget?

I have been using the INTERACTIVE with 176/768. Phone runs great, except I cannot run Pandora with the 176 setting. So I bump to 352/768, then my battery takes a pretty big hit.

On ASOP Froyo I was using OC Widget and very happy. I could set separate screen on/off settings and this was a nice balance. But that ROM didn't have an internal Governor like this one does. Or at least I don't think it did.

I tried running OCWidget on this ROM and it seemed like it was always changing speeds. My suspicion is that OCWidget and the Governor were fighting each other. Is this possible? Do I need to disable "The Gov" somehow if I am going to use OCWidget? :confused:
[Hero CDMA Android Development] picklerick:
I removed the dir /cache/dalvik-cache and all the files within and got back my missing space which was about 50Mb's
[Hero CDMA Android Development] dawgz:
Hmm... I've been doing fresh installs, wipe dalvik, cache, format boot/system/data/cache etc, firerat mtd 120/50. Just now, trying to update 2 apps over 3G one was success, one failed, re-update, and it worked... so I'm not sure what's wrong... using clockworkmod 3
[Hero CDMA Android Development] il Duce:
Just use cm settings, change to ondemand governor at 176, see what happens.

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] Drunkpilot:
I don't think it's a good idea to have 2 CPU tweaks going at once. I think you are right and they will fight each other.

I think I would use the built in governor and maybe try lowering to 264 first, and see if you have any streaming issues. If so, try switching to "on demand" instead of "interactive". I have seen others suggest this. I use a Deca kernal #589 uncapped with the Deca battery tweak mod as I have noticed that this works best with my phone (so far anyway).
[Hero CDMA Android Development] aiwetir:
check the md5 after you put it on the card

sent via tappa tappa tappa
[Hero CDMA Android Development] oldjackbob:
If you flashed 2.5.0.7 as a zip, it's only temporary. That's why you're still seeing 2.5.0.1.

To make a recovery permanent you need to flash it as an image using adb or a terminal emulator.

I just found that out tonight, in the EVO forum, lol!
[Hero CDMA Android Development] oldjackbob:
Boy, now he's gonna really be confused, because the md5 in the OP isn't for the 3/7 release, it's leftover from the 3/6. Aosp is aware of this, but for some reason hasn't corrected it.

Edit: The md5 in the OP has been in need of updating since early afternoon...I don't know what's going on, but it's a bad thing to have a wrong md5 value under the 3/7 download link.

Don't really know what else to say about that. Can someone please talk to aosp about that?
[Hero CDMA Android Development] Brickster:
Trying to understand that one...... Why would it be different after I put it on sd? I mean, the md5 was correct on my computer, so you are saying it could change in the transfer to my sd........ if there was an error or something?

I did see that the file I downloaded was 69.0 MB, and was suppose to be 71.0.....but the md5 was correct @ my computer.

I guess something got lost along the way but still generated the correct md5. weird
[Hero CDMA Android Development] Brickster:
No, I used the md5 off the wiki: md5: c83ce0e74de49b32151f1a1e13a7663b
[Hero CDMA Android Development] Nilxchaos:
That's the one.
[Hero CDMA Android Development] oldjackbob:
Apparently that's exactly what happened, because the md5 says the copy on your computer is correct, but we know from the 69MB size that the copy on your phone was bad.
[Hero CDMA Android Development] Brickster:
Anyway, thanks for the help. Re downloaded/flashed and I'm back to the screamin demon rom that it's was earlier. That was the first real problem that I've had so far and it was user/computer error and not rom.....

Thanks again,,,,,,my head hurts now...hehe
[Hero CDMA Android Development] SammyM00782:
Am I the only one overclocking at 807?? :D
[Hero CDMA Android Development] Brickster:
I call BS on that....
[Hero CDMA Android Development] stayclean:
http://xdaforums.com/showthread.php?t=959080

However, just like last year when that was also done, I'm sure there is no upgrade to performance, and probably a nice decrease to battery life.
[Hero CDMA Android Development] Brickster:
Ok, I stand corrected,,,Still would like to see how it acts.

Mine will run at 768MHz.............for a nanosec:p
[Hero CDMA Android Development] jadenj5:
My phone is always clocked to 768/691

Just throwing that in

And I tried the newest release, faster than the others. But still laggy, at least compared to aosp froyo, but that's prolly cm, definitely a good ROM good to show my buddy who abandoned his hero for a nexus s lol, but when it's aosp im sure it will be the fastest if not a close tie with 2.2

Great work aosp,
[Hero CDMA Android Development] ch1naski:
Hey ojb,

I'm a lazy bastard, and never learned a whole lot of adb commands.... If I can find an image, how do I flash it in TE?

And how come clockwork won't update itself, recovery-wise, dammit....

π
[Hero CDMA Android Development] silberj:
Just want to share an "oh sh*t" moment with you. I had the same problems as you. I was doing my rebooting and flashing and nand and such while plugged in to my laptop because we all know that this process drains a lot of juice out of our heroc's while we are hooking them up. I found out that many processes fail if the usb is plugged in, including a good nand backup. I know my backup would always stick at data, then I inadvertently unplugged my cable and the process went through smoot as silk. Just something to think about.
[Hero CDMA Android Development] il Duce:
Make sure the recovery image is on the root of your sd. Rename it to recovery.img for ease. Go into te, type su, then type flash_image recovery /sdcard/recovery.img

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] wjason:
I tried but had lots of reboots
[Hero CDMA Android Development] vayman:
From TE:

su

flash_image recovery /sdcard/nameoftherecovery.img

Just make sure your recovery image is on the root of your sd before you start. ;)

**Edit: duce beat me to the punch**

Sent from my sweet ass Gingerbread Super Hero!
[Hero CDMA Android Development] josiahdm:
what sense rom is everyone using to update the profile and prl? and do i need to flash back to a earlier recovery image to do so? my recovery is v3.0.0.5

Thanks
[Hero CDMA Android Development] thatdudepoops:
I've always run 768/190 ondemand...till Jason's God kernel I at 800..it is faster but not too noticable...until 3-07. Now it boot loops when useful the max to 806(I use deca.mod2.2 to cap at 800)
[Hero CDMA Android Development] lazie0402:
I personally use the rooted stock one I made a backup of after I first rooted my phone
[Hero CDMA Android Development] cptkool:
sorry but do i need to wipe anything when upgrading to a newer version?
[Hero CDMA Android Development] Freeroot:
You can do whatever you want, but I thought you should know the wiki says you should specifically not use that kernel. It works for some though. But really, I can't imagine it would make much difference.. im at 768 and it is QUICK.
[Hero CDMA Android Development] Freeroot:
Wipe cache and dalvik.
[Hero CDMA Android Development] cptkool:
thx for the help!
[Hero CDMA Android Development] Freeroot:
Sure :)
[Hero CDMA Android Development] lazie0402:
Do his kernals support the built-in governors and the "wireless teather for root users" app? Every time I try to run the app I get an error saying my kernal is not supported. I'm currently running the stock ROM kernal.
[Hero CDMA Android Development] h4kudoshi:
I am having issues with using the DSP settings. After a while the music begins to get choppy and slows and the phone becomes totally unresponsive.
[Hero CDMA Android Development] thatdudepoops:
I remove dsp everytime i flash. U can only use it very lightly, and if u don't uncheck it stays running in the back ground, even with no music, even on reboot.
[Hero CDMA Android Development] aiwetir:
I'd look into the min cpu settings.
[Hero CDMA Android Development] oldjackbob:
New release is posted, along with a new gapps! :)
[Hero CDMA Android Development] jckeyser:
Rockin'.

Sprint Nexus S what?
[Hero CDMA Android Development] SammyM00782:
I'm surprised people missed that. Performance is marginally better and battery life is no different for me. No matter what I do, when I unplug at 7am and come home around 4 it's always at about 60%. Doesn't matter what ROM I use, my settings or if I just leave it alone all day it's always the same. I work in areas with lousy service though so I'm rarely at full bars or even close. If I'm really in northern Mercer County I might as well bring an extra battery cuz it'll be dead before 12. Thanks Princeton :-)
[Hero CDMA Android Development] Kevets:
Mirror for aospCMod-20110308

http://db.tt/xK247P9
[Hero CDMA Android Development] ch1naski:
Thanks for the mirror, kevets

π
[Hero CDMA Android Development] davec1234:
Is there a reason we only get tiny gapps?

Used to be able to get everything in one zip.

Are there instructions some place how to make your own gapps?
[Hero CDMA Android Development] aosp:
ladies and gents 3/08 is up let me know if its any quicker if not i have a few other tricks up my sleeve to try dont know why but i just refuse to give up on the heroC :o
[Hero CDMA Android Development] kashb91:
Well we all appreciate the effort aosp. Question though, is this build essentially RC2 for CM7?
[Hero CDMA Android Development] skola28:
AOSP, you the man. I don't care what anyone else says :P

Downloading now... Excited that the gapps got updated yesterday as well.
[Hero CDMA Android Development] Pyr0TeK:
You are the freakin man... I love my Hero because of you (and all the devs). I have been wiping my cache and dalvik and just flashing over since 02/25 build and it just keeps getting better. Thanks a ton bro. You are the reason I really don't have a need to upgrade my phone. :):D:)
[Hero CDMA Android Development] aosp:
no alpha, beta, nightly, rc

just aospCMod build 3/08 :D
[Hero CDMA Android Development] ULoveAriana:
Don't know about others but it's quicker for me & with this rom I've gotten better life than any other plus it's real smooth. The work on this rom has been amazing & much appreciated by everyone :)

Sent from my cool-whiped SuperHero
[Hero CDMA Android Development] ehurt152:
Oh yeah, I thank God you refuse to give up on the heroc!!! I'm running launcher ex on fast with this rom and everything is fast and smooth.
[Hero CDMA Android Development] skola28:
Has anyone tried the new Music Sync that the EVO guys are raving about? I installed the .apk file and removed the old Music.apk from system/app, but I keep getting force closes.

:(

Original EVO Thread with details

http://xdaforums.com/showthread.php?t=980018
[Hero CDMA Android Development] DJB628:
Hey bro thanks a bunch, also what is with the call screen going black at times, any solutions for that, it only happened twice yesterday to me in all the build, but seems that many others are also experiencing this issue
[Hero CDMA Android Development] pstevep:
Thats because its addicting like a drug.. Just when you think you are done with it those cravings come back and you pick it up again.. Thankfully for us when you pick it up you bust out amazing roms..

Kudos, it is a bit quicker on this build

<insert witty line about your rom here>
[Hero CDMA Android Development] andythegreenguy:
Thanks a million for not giving up on the HeroC. It's because of people like you, I still love my Hero!
[Hero CDMA Android Development] :
I upgraded (added a line really) to our plan and went with the Epic, swapped the numbers, so the Epic now has my Hero's number and the Hero is now the work phone...but I can's stop tinkering with the Hero! Thought I would move on, but I can't. It's like a bad breakup or something, and I only have aosp to blame ;)
[Hero CDMA Android Development] cmccracken:
aosp, do you have any thoughts on the problem/fix for the GPS crash issue? Any idea where the problem lies, or if a fix is realistically in the future?

I'm still using aospCmod (because well, it rocks), but without any GPS since using that reliably crashes the phone. Going back to aosp 2.2 to get a GPS will be so painful after getting used the sweetness of this ROM!
[Hero CDMA Android Development] wild1z:
I am hoping Sprint announces another dud (Ok that is for my benefit, maybe Sprint will release something cool for you. ;)) so I have to stick with the Hero a little longer. Ride the wave!
[Hero CDMA Android Development] :
I still have the Hero...just have an Epic as well, both activated and used every day :) Can't abandon the Hero...look at how far development has come! Amazing.
[Hero CDMA Android Development] gadgetcraze:
Thanks a ton aosp. I wonder what would my hero be without you. I followed you on froyo and now on gingerbread. Thanks a lot for whatever you have done for heroc community.
[Hero CDMA Android Development] il Duce:
aosp for prez! Popup animations are fast :)

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] abadasstanker69:
I've been having connection issues with the gps since 4 builds ago when it was classified as working. Is anyone else having these issues or a fix?
[Hero CDMA Android Development] Kfunk:
I completey understand - I have a shiny new Evo and I continue themeing and tinkering with the Hero instead!
[Hero CDMA Android Development] picklerick:
turd green.....
[Hero CDMA Android Development] :
Just a quick thought I had for those having wake issues where the phone awake time is far greater than the screen on time. I recall a string of posts awhile back on this. I generally don't have this problem, but I always press "back" to exit out of each program instead of just hitting "home". My awake time and screen on time are very close to the same when I do this, and I notice more awake time when I just hit home. So give that a try. YMMV. Just an idea that may have gotten overlooked :D
[Hero CDMA Android Development] il Duce:
This only works with the stock theme right?

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] ch1naski:
And aosp is the reason WE don't give up on the heroc.

π
[Hero CDMA Android Development] pstevep:
i do the same.. i havent had any kind awake lock on this rom.. well stock anyway, i am using sObe's .35 kernel and it has something in it that will cause a lock occasionally but it just requires a reboot.. i have always used the back button instead of home.. my wife always used home and she always had all sorts of programs still running and her battery was generally worse..
[Hero CDMA Android Development] :
What about the incoming call black screen?

Working fine here :confused: If I do lose connection (which is rarely) it picks it back up. What kind of connection problems are you having?

Yup. I like to push things beyond what the capabilities are, and so far for the Epic, eh...not happening...seriously, GB on a Hero?! ;)
[Hero CDMA Android Development] METHOD1911:
Ranger can I ask you what's the difference between aosp Rom and the rc that was released if you know

Hijacked aospCMod Darkhorse GB Hero
[Hero CDMA Android Development] 24601:
Had to flash back to stock to update and O . . M . . G! I thought I was in he**! A totally different beast.
[Hero CDMA Android Development] aosp:
naming scheme maybe use whichever you like and works best for you always free to try and you never have to buy so you always win i promise ;)
[Hero CDMA Android Development] aqualls:
Ok. searched and didn't find the answer. No matter what kernel I use with this ROM, I have no wireless tether. Just curious if anyone else has this problem and if there is a fix. It works fine on all the other roms I switch back and forth between.
[Hero CDMA Android Development] andythegreenguy:
Are you using the wireless tether app from the market? It works very well for me. If you are talking about the stock tether... it may still be an issue.
[Hero CDMA Android Development] il Duce:
You need a market app, the native tether has never worked.

sent from my hero, which no longer sucks ass.
[Hero CDMA Android Development] aqualls:
Using wireless tether app and barnacle with correct settings and nada.
[Hero CDMA Android Development] ktynchy1:
Thank you
[Hero CDMA Android Development] GeezyAF:
Only days in development and things are like 90% done.

Definitely will be flashing once camera gets implemented.

Good work, AOSP.
[Hero CDMA Android Development] wjason:
Yes, it is the new text selection tool in GB
[Hero CDMA Android Development] gadgetcraze:
Had tried the earlier version a couple of days ago. Now stuck on android boot screen. Using firerat's. What do I have to do in order to get this newer version working?
[Hero CDMA Android Development] ahager88:
Just wanted to stop by and say thanks publicly!

Newest release:

Browser doesn't force close.

Gmail hasn't force closed on me... but I've only received one email since flashing.

Other than that, I can't see a difference. Great release once again aosp!