yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] KyleBryant:
Hmm... lucky you.
[Hero CDMA Android Development] cjdalessio:
Are you clearing cache and dalvik cache after flashing?
[Hero CDMA Android Development] aiwetir:
Are you running firerats and is it cutting it too close?

I flashed right on top, no wipe, no nothing.

Make sure you delete the old zip from your sd card, empty trash, then copy the re-downloaded one to the card checking the md5 of the file on the card.
[Hero CDMA Android Development] sleepyEDB:
I just flashed the 105 nightly on top of CM7.0.3 and got stuck in a bootloop at the blue CM7 logo screen...glad I made a Nandroid first!

I'm running the stock kernel and my CPU settings aren't too dramatic...using ONDEMAND with a low of 19 and max of 576, which has been working for several months. I'm also running ClockWorkMOD 2.5.0.7

I haven't had any problems when flashing any of the stable CM releases so far, and I always wipe cache & Dalvik, so I'm not sure if it's the nightly or something I did...

sleepy
[Hero CDMA Android Development] aiwetir:
Someone else had that issue with 104, maybe there's something messed up. I didn't have that problem with 104 but that's just me.
[Hero CDMA Android Development] brett1211:
same thing happening to me.. going back to 102
[Hero CDMA Android Development] jwhistler:
I haven't had any problem with 105 other than the occasional image distortion when starting up Google Maps/Latitude. Rotating the phone 90 degrees and back fixes that...
[Hero CDMA Android Development] sleepyEDB:
Just tried flashing 106 using the same method (make Nandroid, wipe cache and Dalvik from within recovery, flash zip file) and got stuck in the same CM logo bootloop!

Could it be that my CPU settings are to blame? I wouldn't think so since I've been running them successfully since CM7 came out.

Should I try wiping data? I'd really (really) rather not and it shouldn't be necessary, but who knows.

sleepy
[Hero CDMA Android Development] sleepyEDB:
A couple of things I've tried since my post above:

1. I verified the md5 hash of the 106 zip file, and it matches the source.

2. I restored my Nandroid and tried flashing 106 without wiping cache or Dalvik, but it still bootloops.

3. I uploaded a logcat of the bootloop to pastebin: HERE The only thing that sticks out to me is line 225:

E/AndroidRuntime( 676): *** FATAL EXCEPTION IN SYSTEM PROCESS: WindowManagerPolicy
​

After that, processes start shutting down and the code repeats itself when the bootloop begins anew. I let the CM7 animation repeat itself about 5 times, so I hope I captured enough in that logcat. If not, let me know and I can capture another.

Thanks,

sleepy
[Hero CDMA Android Development] jneg123:
Not sure about the bootlooping, but if you need to wipe data there is an easy solution. Are you using Clockwork for the Nandroid? Not sure about RA, but with CW you can do an advance restore of just the data partition.

Last time I flashed, I made sure everything was up and running and logged into the Google setup. Then went back into recovery and did the advanced restore. Worked perfectly.
[Hero CDMA Android Development] noriyori:
So, I've searched and searched and posted about this before, but does anyone know how to get the "force touch ui" setting back in the call settings? The proximity sensorless hero is driving me crazy hitting buttons with my face durring calls.
[Hero CDMA Android Development] sleepyEDB:
Yes, I am using CW as my recovery and I'll give the advanced restore a try if I end up having to wipe data...thanks!

sleepy
[Hero CDMA Android Development] kurtosterhage:
Flashed 106 over 102, flashed FR-boot, wiped cache & dalvik, bootlooped. Wiped data, flashed FR-boot, wiped cache & dalvik, booted fine. Restored data using CWM, flashed FR-boot, wiped cache and dalvik, bootlooped again. Is there something wrong with the last few builds?
[Hero CDMA Android Development] aiwetir:
The few posts above yours have the same issue, I don't, but I'm sure we have different stuff in data.

posted via tappa tappa tappa
[Hero CDMA Android Development] dastin1015:
Try a full wipe, restore data, flash ROM, flash GApps, then flash FR-boot
[Hero CDMA Android Development] 24601:
Also, instead of restoring data with cwm, try TiBackup and restoring from there.
[Hero CDMA Android Development] kurtosterhage:
Restoring data first, then flashing 106 and Gapps didn't work. Guess I'll be going with the Titanium Backup method. Anyone know why some of us are having problems? My FR is set to 130 18 so I don't think that that would be the problem.
[Hero CDMA Android Development] aiwetir:
Recovery? I'm on cwm 2507. Firerat 158 other than that, I delete adw, rom manager, dev tools, dsp, email, file manager. I didn't wipe anything, but dalvik rebuilds after a flash.

posted via tappa tappa tappa
[Hero CDMA Android Development] cjdalessio:
I pushed 106 over 102 and no issues. FR 130 18 also. Just wiped cache and dalvik as usual. I'm on 3.0.5 CWM though.

Not much help perhaps.
[Hero CDMA Android Development] sleepyEDB:
Heh, gotta love inconsistency. aiewtir is running cwm 2507 and has no issues...I'm running cwm 2.5.0.7 and get the bootloop every time, so I'd guess that recovery alone isn't the direct cause?

sleepy
[Hero CDMA Android Development] sleepyEDB:
I just tried the following, and still got a bootloop:

1. Rebooted into recovery (CWM 2.5.0.7)

2. Did a full wipe (cache, Dalvik, AND data)

3. Flashed nightly 106, which went perfectly

4. Booted into the phone and went through the complete Google setup

5. Booted back into recovery

6. Made nandroid of nightly 106

7. Advance Restored just the data portion from my 7.0.3 nandroid

8. Wiped cache and Dalvik

9. Reboot into a bootloop

That's enough for me. :p I've restored the functional 106 nightly and will just set things up again from there.

One question though: During the Google setup, all the G-apps (gmail, maps, etc.) appear to have been downloaded to my phone. Is there a need to flash the gapps zip file, or can I go with what was downloaded during the setup process?

Thanks,

sleepy
[Hero CDMA Android Development] kurtosterhage:
I'm running 2.5.0.7 as well. Fortunately Titanium Backup makes it much easier to just start over with a fresh install. We'll see in a few days if the newer nightlies will flash over properly.
[Hero CDMA Android Development] dastin1015:
Try your procedure without the cache wipe and just do a Dalvik Cache wipe. There still is the need for GApps because that's how you get your Market and Talk. Talk is needed to connect to Market and Google servers. Your apps downloaded because you probably have the backup account settings on under Settings, Privacy and when you do your setup, it restores your apps, passwords, bookmarks, and settings.

Sent from my Hero that never dies! ;D
[Hero CDMA Android Development] sleepyEDB:
Sorry, no luck...still bootlooped. A logcat of the bootloop is available HERE in case you're curious, but don't feel obligated to troubleshoot it for me. I've got nightly 106 working and am okay with re-customizing it, but thanks for the effort.

Hmm...what if the Market and Talk that were installed during the Google setup are already fully functional? Any need to flash the gapps file then?

sleepy
[Hero CDMA Android Development] zanywood:
Does anyone have a circle battery mod for this build? Also I did get nexus to work but that's all so far.
[Hero CDMA Android Development] rubyknight:
Bleh.. nuf said.

The way I see it, Aosp is just an average guy making his own roms for everyone but choosing to stay private and not participate in the big picture. He's never been a big talker or an attention seeker, just seems like an average guy who's helping us hero cdma peons keep up with the flashy phones.
[Hero CDMA Android Development] radrian92:
Weren't you the one that said that the 2/18 batt mod worked cause that's the one I flashed and it does work :)
[Hero CDMA Android Development] Drunkpilot:
Very nicely put. I am excited to see what happens with cm7. I was running the cm6.2 vanilla and red glass until really 2/16. You guys have made owning a hero so much more fun than stock (at least for me) and have raised my knowledge about the inner workings of this phone. This situation is win, win.
[Hero CDMA Android Development] mercrapper:
I finally figured out why my compcache isn't working (but I don't understand why nobody else is having problem with it).

Sometime between the 2/16 and 2/18 build of AOSP's GB build, the compcache script in /system/bin was changed.

The new one refers to a zram module...

DEV=/dev/block/zram0
SYSFS_PATH=/sys/block/zram0
MODULE=zram

but the correct module is ramzswap. Also, the rzscontrol script was missing from /system/xbin (I copied if from the 0216 build) and the ramzswap.ko module was in /system/lib/modules/2.6.29.6-CyanogenMod/kernel/drivers/staging/ramzswap instead of /system/lib/modules/2.6.29.6-CyanogenMod/kernel/

Once I corrected these 3 issues, it started working again.

I don't know if this is a bug in CM, or if its just me, but I thought I would put it out there in case anybody else was having problems or if it is a bug, somebody could fix it the right way. ;-)
[Hero CDMA Android Development] aiwetir:
I think jaybob already posted that a few pages back.

sent via tapatalk
[Hero CDMA Android Development] bravo1565:
Are these cm7 nightly ready to download and flash
[Hero CDMA Android Development] PTown599:
New nightly is up.
[Hero CDMA Android Development] bravo1565:
Just downloaded and flash
[Hero CDMA Android Development] radrian92:
Was this build suppose to fix the cdma limitation of 160characters or is there an extra step I need to take, because I'm still unable to send more then 160.

Edit: nvm just found out that I have to enable it in settings ;).
[Hero CDMA Android Development] bravo1565:
It's seem this has the same issue as aosp Rom with video limitation on youtube can only play 3 or 4 videos and that's it get stuck on loading
[Hero CDMA Android Development] dedian:
Check out the market comments on the Youtube app. Since the latest update of the app, a lot of people (on a lot of different phones) are having this same problem. It doesn't seem to be tied to anything but the app.

Edit: More info from the youtube help forums (there's no fix there, just a lot of "Why isn't google fixing this?")

http://www.google.com/support/forum/p/youtube/thread?tid=45f90193e3454329&hl=en
[Hero CDMA Android Development] zanywood:
weird forcloses

I've been running this for about 35hours and I love the phone dialer it keeps me from pushing buttons while talking . Well im getting forecloses on android system every now and than when im using phone. And a couple other forecloses.
[Hero CDMA Android Development] user7618:
Anyone else getting 502'd on the teamdouche mirror?

-----

Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
[Hero CDMA Android Development] zanywood:
bad gateway

Im getting a "bad gateway " when I try to download this. Is this the first build or second?
[Hero CDMA Android Development] zanywood:
odexed or deodexed

Is this odexed or deodexed?
[Hero CDMA Android Development] thoughtlesskyle:
Deodexd
[Hero CDMA Android Development] zanywood:
noob

Im learning things as I go so bare with me. What is the difference between odexed and deodexed? I ask cause on aosp rom they say its odexed. If this is stupid question im sorry but im trying to learn as much as I can.
[Hero CDMA Android Development] :
Here ya go ;) Just playin'

Simple answer is odex has, well, the odex files corresponding with each apk; deodex does not...

Odex can't be themed (as easily); deodex can be themed easier.

Speed differences as well.
[Hero CDMA Android Development] user7618:
I see I'm not the only one, then.

-----

Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
[Hero CDMA Android Development] dastin1015:
The gapps includes the Google setup, calendar, weather, market, talk, etc. I'll check out the logcat once I get a computer up and running.

Sent from my Hero that never dies! ;D
[Hero CDMA Android Development] sleepyEDB:
If you'd like to check it for your own curiosity please do, but I've since gone back to CM7.0.3. Earlier today after a long customization session in nightly 106 I decided to make a Nandroid. I booted into recovery, made the Nandroid without issue and selected 'reboot system' from the menu. Bootloop. :mad: After several approaches including wiping cache/Dalvik, restoring just the data portion, and wiping everything including data before restoring still resulted in a bootloop, I'm done.

The only real reason I flashed the nightly was for the 90/180/270 screen orientation lock, so it's just not worth the headache. I'll wait until the next stable version (or at least the RCs) before leaving 7.0.3.

thanks to everyone for their input,

sleepy
[Hero CDMA Android Development] aiwetir:
according to the changelog, next rc is coming up soon.
[Hero CDMA Android Development] spleef:
yeah possible 7.1rc1 this weekend on the twitter
[Hero CDMA Android Development] bravo1565:
Hey what nightly would you guys recommend
[Hero CDMA Android Development] Houndog101:
I'm running #109, no problems..so far. :)
[Hero CDMA Android Development] bravo1565:
Great I will try that 109
[Hero CDMA Android Development] aiwetir:
If you bootloop, try 102 instead.
[Hero CDMA Android Development] oohaylima:
Best descriptive change log in a long time! :D
[Hero CDMA Android Development] LiquidSolstice:
OP updated to reflect RC1's release.
[Hero CDMA Android Development] GeezyAF:
7.1RC1 drains my battery really fast.
[Hero CDMA Android Development] LiquidSolstice:
Yay. First Heroc specific change in months. Too bad it's nothing exciting :(

heroc: Add CM copyright notice (android_device_htc_heroc)
[Hero CDMA Android Development] oohaylima:
How's the latest one doing? Anybody have any problems with it?
[Hero CDMA Android Development] aiwetir:
Seems the same here, flashed 118 last night.
[Hero CDMA Android Development] Shelnutt2:
Been running 119 with no problems for a while. It fixed my mobile defense issue too.
[Hero CDMA Android Development] aiwetir:
119? I'm on 131.

posted via tappa tappa tappa
[Hero CDMA Android Development] genuser:
I have browsed the change log but didn't see much related to GPS. What's the current state of the GPS reboots on CM7?

I stepped away for the past month or so since I have been traveling and solid Nav is a must.
[Hero CDMA Android Development] DrunkenOstrich:
Same here. Still wondering if that bug is fixed yet? Specifically, the proximity sensor is not working properly in calls, face constantly hits buttons, hangs up the phone, etc. Drives me nuts.
[Hero CDMA Android Development] aiwetir:
There has never ever been a working proximity sensor in the Hero.
[Hero CDMA Android Development] DrunkenOstrich:
Well, whatever method was used in the stock Sprint ROM worked pretty well, as the issue only started after I went to CM7. Also, I searched around the CM forums and others are having this issue with other phones as well after going to CM7.
[Hero CDMA Android Development] GeezyAF:
GPS here is solid as a rock. This rom is fully functional in all the essential ways.
[Hero CDMA Android Development] aiwetir:
I think the method was that the screen timed out after 10 seconds while in-call, now it seems to respect what you have it set at. It is annoying, hope they fix it, then again I'd just as soon get a phone with a proximity sensor.

posted via tappa tappa tappa
[Hero CDMA Android Development] ch1naski:
I was waiting for them to fix that. Now I can finally use this as my daily.
[Hero CDMA Android Development] aiwetir:
The changelog indicates a screenshot app and it's on the phone but I can't find it anywhere to run it.

It also indicates touch to focus which actually seems to have totally removed that functionality instead of implementing it.
[Hero CDMA Android Development] Decad3nce:
Long press power button. It's an option. I'll be checking out the touch2focus bug, might be a while since my hero is a bit "under the weather" atm.

Upstream fix incoming: http://review.cyanogenmod.com/#change,6577
[Hero CDMA Android Development] aiwetir:
Thanks! It won't save the screen shot though, can't find a setting for a save directory.

EDIT:

Ok so it isn't writing tmpshot.bmp, says file or directory doesn't exist. If I create a file by that name it uses it but then I get some java pointer null exception or something like that, it writes a screenshot to the dcim/screenshots/ directory but the file is unreadable.

posted via tappa tappa tappa
[Hero CDMA Android Development] stayclean:
Came in here to post this exact problem. Hopefully it gets sorted out, I really like the idea of this feature.
[Hero CDMA Android Development] Decad3nce:
Can you paste the logcat?
[Hero CDMA Android Development] aiwetir:
Here are 2 consecutive attempts to take a screenshot.

I/ActivityManager( 169): Start proc com.cyanogenmod.screenshot for broadcast com.cyanogenmod.screenshot/.ScreenshotReceiver: pid=21406 uid=10068 gids={1015}
W/InputManagerService( 169): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@405bc0f8
I/ActivityManager( 169): Starting: Intent { act=com.cyanogenmod.screenshot.ScreenshotActivity flg=0x10800000 cmp=com.cyanogenmod.screenshot/.ScreenshotActivity } from pid 21406
D/dalvikvm(21406): GC_EXTERNAL_ALLOC freed 54K, 50% free 2695K/5379K, external 0K/0K, paused 62ms
D/Screenshot(21406): Ran helper
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
D/MediaScannerService(18273): IMediaScannerService.scanFile: null mimeType: null
W/InputManagerService( 169): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@40756c48
D/dalvikvm(16640): GC_EXPLICIT freed 33K, 49% free 3212K/6279K, external 331K/512K, paused 68ms
I/ImageCache(20051): Flushing Memory Cache
I/ActivityManager( 169): Starting: Intent { act=com.cyanogenmod.screenshot.ScreenshotActivity flg=0x10800000 cmp=com.cyanogenmod.screenshot/.ScreenshotActivity } from pid 21406
D/Screenshot(21406): Ran helper
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
E/libEGL ( 169): called unimplemented OpenGL ES API
D/MediaScannerService(18273): IMediaScannerService.scanFile: null mimeType: null
W/InputManagerService( 169): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@4072e7a8
D/dalvikvm( 169): GC_EXPLICIT freed 1749K, 52% free 7625K/15751K, external 2044K/2281K, paused 219ms
I
[Hero CDMA Android Development] kyouko:
Looks like the next nightly should fix the opengles error you're getting.

review.cyanogenmod.com/#change,6577
[Hero CDMA Android Development] aiwetir:
Screenshots work great. Ditching my other screenshot apps now.
[Hero CDMA Android Development] bravo1565:
What is screen shot
[Hero CDMA Android Development] GeezyAF:
CM7 now has a built-in app for screen shots, rather than using something like Shoot Me or Drocap2.
[Hero CDMA Android Development] bravo1565:
Has anyone had the issue with adw were you hit the launcher and it vibrates like your gonma remove it how can I get rid of that
[Hero CDMA Android Development] XGodOfModzX:
Downloading the latest nightly 123, also how does cm7 have built in screenshot app? I don't see it

GingerBreads have no souls.....But, Windows Phone 7 gives it one. I Love Launcher7 :)
[Hero CDMA Android Development] bravo1565:
You have to hold the power button like your powering the phone off and it will come up
[Hero CDMA Android Development] aiwetir:
all you had to do is read just a few posts back to find how to take a screenshot.
[Hero CDMA Android Development] XGodOfModzX:
Lol never noticed it
[Hero CDMA Android Development] jwhistler:
Navigator Freezes, Force-Closes

Anyone been having any issues with this? My GPS using Navigator will freeze and then force close when I try to exit....
[Hero CDMA Android Development] skola28:
akmd - battery drain

Has anyone else been experiencing the akmd app/service running constantly and destroying the battery life? So far I can confirm the issue does NOT exist on 113, but DOES exist on 124-129.

I installed 129 a while back when it had just posted, and after rebooting noticed my battery draining quite quickly. I checked the battery use utility and akmd was showing 80% of my battery usage. I rebooted, recharged, and same thing. So I started working backwards through the nightlies to find one that wasn't draining my battery, I got to 124 and I finally gave up and went back to the nightly I was on before this all happened (113).

Anyone else seeing this?
[Hero CDMA Android Development] cjdalessio:
I've seen battery life tank more recently, but not specifically observed this. I've just spent a while logging akmd process and it's not doing much at all. Radio seems to eat most of my battery these days.

I'm on 126.
[Hero CDMA Android Development] LiquidSolstice:
Well guys, it's a sad to say it for me, but I've finally made the decision to move on from the Hero. In a few hours, I'll be the proud new owner of the EVO3D.

The Hero has been a ridiculously resilient phone. What's been done with it is nothing short of incredible. It's gone through and will probably continue to go through every version of Android that we've thrown at it.

It's been a great deal of fun being at this section of XDA, but now I must take my leave. Thank you to everyone who made my phone experience what it was.

The links in this thread should remain accurate with no need to change them, but I will not be updating it when major versions come out or if RCs come out.
[Hero CDMA Android Development] jwhistler:
I've been suffering horrible battery life with the last few nightlies. Between that, and the GPS issues, I finally went back to 7.1 stable.
[Hero CDMA Android Development] ch1naski:
"See you on the other side, Ray."

nandroids are for

sissies
[Hero CDMA Android Development] Shelnutt2:
See you on the flip side:cool: (if I ever upgrade haha)
[Hero CDMA Android Development] Nanan00:
I have run into a new one, phone runs fine, it goes to sleep, upon waking up it appears frozen on the last application run, hitting any button seems to trigger like the back button, upon hitting a button it goes to the previous last app running, then the next, then the next etc all the way back to the launcher at which point the phone reboots.

My upgrade is Aug1, not sure if I want a Evo 3d... starting to think I'll just hold onto the hero till the next regular non-gimmicky phone comes out.
[Hero CDMA Android Development] Decad3nce:
What nightly? Can you grab a logcat.
[Hero CDMA Android Development] LiquidSolstice:
You do realize there's a hell of a lot more advanced tech on the Evo 3D than just the 3D part, right?
[Hero CDMA Android Development] GeezyAF:
Not a lot of people read into the nitty-gritty.

I bet majority of consumers, like him, think the EVO 3D is the EVO 4G with a 3D button the side.
[Hero CDMA Android Development] LiquidSolstice:
Yes, but aside from the "gimmick" of 3D, it's the most powerful phone on the market right now right next to the SGS2. Dual core 1.2 GHz, 1 GB RAM, qHD display (which I don't think even the SGS2 has) 4 GB of on board space, and still manages to pack in dual flash cameras with a FFC as well.

It's the most powerful phone you can buy today on Sprint. It goes neck and neck with the SGS2.
[Hero CDMA Android Development] ch1naski:
Wait......it's not? :D

nandroids are for

sissies