yashsingh1/xdaforums huggingface dataset:
[Hero CDMA Android Development] Ezintn:
running 8/30 w/ "stock" kernel, no mms sending or receiving, everything else works well so far.
[Hero CDMA Android Development] laufine:
Where can I get the nightly ROMS?

Thank you!
[Hero CDMA Android Development] Mac11700:
Here..http://mirror.kanged.net/cm/nightly/heroc/

Search is our friend ;)

Mac
[Hero CDMA Android Development] hazyspartan:
8/30 is fantastic except I still have no gps I have tried every suggestion and it works fine when I nandroid back to any 2.1 roms. I may just have to live without gps because this rom runs so smooth.
[Hero CDMA Android Development] LifeInTheGrey:
Try backing up your cm6 setup, wiping completely, then installing fresh 2.3.3 (don't nandroid back, install). Get a gps lock in fresh, then nandroid back to cm6. Worked for me.

Froyo Hero to the rescue
[Hero CDMA Android Development] stricklerjosh:
Also worked with me using aloysius.

Sent from my Cm6 blue envy froyo hero!
[Hero CDMA Android Development] chugger93:
I didnt wipe and went from 829 to 830. mms is broke. Tried clearing the db files as posted...no luck. Ideas?
[Hero CDMA Android Development] killabee44:
GPS and MMS working great on RC1 for me. Had some sdcard issues but not sure if it was the rom or the card.
[Hero CDMA Android Development] Akkeresu:
Can't wait to hear about a stable release version.
[Hero CDMA Android Development] bigjustinturbo:
mms-sign.zip

I'm running the 082910 build, stock kernel, and mms isn't working either. Today is the first day I've noticed since I don't use send MMS very often, but I did have some issues from time to time sending SMS using various nightlies from 08/20 and on. I'm talking about the stock app, I don't use Handcent.

The database deletion trick did nothing for me. Poking around in the CM6 testing thread, I spotted a post from yesterday from someone who said that the "mms-sign.zip" file posted in this forum worked for him.

I searched for and found the file, tried it, and it worked for me. Sent a photo to myself with MMS and it went right through, I received it seconds later. It would just hang earlier.

While searching, I found that the file was actually posted in the CM6 Testing thread about a zillion posts back -- post #55 on July 10 -- but there wasn't much discussion about it at the time. Update: File removed. Keep reading, and check out the file in post #1541 on page 155 of this thread.

It needs to be flashed. I did a nandroid backup before flashing it just to be sure, but that's your call. It worked for me though.

If you dig through the zip, you'll see it replaces 2 files: /system/etc/apns-conf.xml and /data/data/com.android.providers.telephony/databases/telephony.db. I wish I had more information about where mms-sign.zip came from, because if you compare the apns-conf.xml file to even the one from CM RC1, it's pretty trim. Makes me wonder if it was a custom job or if it came from a different ROM altogether.

Anyway there's enough chatter about MMS problems in the nightlies lately that this is something I hope the dev is taking a look at. Maybe there are other users who are affected but don't realize it's busted because they don't use MMS often or are using Handcent. Who knows, but I hope this helps some of you.
[Hero CDMA Android Development] jakejm79:
The apns-conf.xml file I believe contains information for parsing the http links for send and receiving MMS, for whatever reason sprint requires some additional information (a header or something I believe) in order to configure it. This was discovered several months on DD (2.1 ROM). From what I understand all builds DD2.7 and later and all Darch Froyo builds were meant to have this fix in the apns-conf.xml file. Since the *.db files are created on 1st boot from the apns-conf.xml file this is what I assume may be happening:

From builds 8/27 and on there was a new apns-conf.xml file used (apparently to fix GPS issues), maybe this file does not contain the correct info for accurately creating the *.db files. Hence why a wipe and install of 8/27 or later results in MMS not working, but the people that seem to have it working flashed 8/27 or later over an existing version (RC1, 8/25 or lower) and since the *.db files were already created from a working apns-conf.xml file MMS continues to work.

Either that or it is related to a Kernel version.
[Hero CDMA Android Development] Atticustrd:
Could someone please help with this thanks. :o
[Hero CDMA Android Development] Akkeresu:
Be sure that notifications are turned on in your applications. Some apps don't enable by default, or have specific options for the LED, like Touiteur.
[Hero CDMA Android Development] jakejm79:
Did a little more digging and came up with this:

From Fix Zip
<apn carrier="CDMA" mcc="310" mnc="120" [B]apn=""[/B] port="" mmsproxy="" mmsport="" mmsc="http://mms.sprintpcs.com" [B]type="mms"[/B] />

From CM google code page:
<apn carrier="CDMA" mcc="310" mnc="120" [B]apn="1"[/B] port="" mmsproxy="" mmsport="" mmsc="http://mms.sprintpcs.com" />

From 8/30 nightly:
<apn carrier="CDMA" mcc="310" mnc="120" [B]apn="1"[/B] port="" mmsproxy="" mmsport="" mmsc="http://mms.sprintpcs.com" [B]type="default,supl"[/B] />

From RC1:
<apn carrier="CDMA" mcc="310" mnc="120" apn="1" port="" mmsproxy="" mmsport="" mmsc="http://mms.sprintpcs.com" />

I believe the

type="mms"

is the important part and the part that sprint requires to get MMS working. Maybe someone could update the CM code to make sure this is in all builds or something. I believe Darch was adding it on his releases but when the apns-conf.xml was changed for supposed GPS fixes it reverted back to the one from CM source that breaks MMS.
[Hero CDMA Android Development] Atticustrd:
Yeah, they are turned on it's just odd how it works sometimes and other times it doesnt.

Like handcent my trackball lights up when i have a message after i unlock my phone it wont notify me if my phone is off. I have to unlock it, same with missed calls and V.M. Its not a huge deal, but it would be nice to get it to work right.
[Hero CDMA Android Development] laufine:
Thank you very much.
[Hero CDMA Android Development] bigjustinturbo:
That's good info. I didn't know that it had been changed for a GPS fix, which had me worried that maybe flashing that file had busted GPS for me. I just did check outside for about 10 minutes and everything seems fine. It locked onto me in Maps within a few seconds, though I've never had GPS issues with any ROM, CM6 or otherwise.

The second part in your previous post makes sense. In fact, up until yesterday, I was running RC1, then flashed 082010 over that, and then two more nightlies over that since then -- 08/25 and 08/28. On August 20, I sent an MMS to someone that I know was sent and received correctly. I was running 08/20 at the time. I was running uncapped kernels during most of that time, and did not wipe before flashing the nightlies.

However yesterday, I did a complete wipe, then flashed only 08/29, stock kernel. MMS = broken.

I have multiple nandroid backups from those times so I may try some tests later. If what you're saying is what's going on, then it's possible I could restore to my 082810 build, and have working MMS since the .db was created before the changes to apn-conf.xml on 08/27, but if I were to delete the .db and reboot, then MMS might break since it's being rebuilt from the changed apn-conf.xml file.

Update: And that's exactly what happened. Restored my backup to the 082810 build, and sent an MMS without any problems. Deleted the telephony .db files, rebooted, tried again -- no luck. Flashing mms-sign.zip is a fix for me at this moment and does not cause GPS issues that I can tell. I can't promise anything for anyone else. But know the risk of wiping / deleting those .db files if you're running a post 08/27 build - you could likely lose MMS upon rebooting.
[Hero CDMA Android Development] AjaxBU:
This rom is amazing, I've got everything set to how I want it. The only exception I I can't get my HTC widgets to work, which isn't a deal breaker in my book. However, I have tried everything I can to stop those annoying 9016 texts with no luck. I switched to google voice for a while, but I didn't like it very much.

I installed the sprint vvm zip and then got a text saying provisioning successful, then it continued sending me texts everytime I got a vm. Has anyone else found a resolution to this? I've been searching and haven't found anything, so I'm sorry if this has been resolved already.
[Hero CDMA Android Development] wctom:
I, too, am having problems with the GPS; it is frequently showing me several blocks away from my real location. Since I am travel a lot and renting cars without a built-in GPS, I rely on the phone GPS a lot.

I have tried the 8/25, 8/28, and 8/30 nightlies, and they all have the same problem. Fresh 2.33, on the other hand, quickly and accurately locks onto the GPS.

I hope the problem gets corrected soon, since otherwise the ROM is great.
[Hero CDMA Android Development] fifedogg:
I pretty sure none of the HTC stuff will work on this rom.

I'm also getting a text everytime I'm recieving a Voicemail.
[Hero CDMA Android Development] AjaxBU:
Yeah, that's what I've heard and it's certainly something I can look past.
[Hero CDMA Android Development] zeropants:
I get the text on every voicemail, my gmail doesn't synchronize through the gmail app, and I get network errors connecting to the market unless I am on wifi.
[Hero CDMA Android Development] asoong:
FYI, I had the same problem with the 8/24 rom. I jumped to the 8/30 nightly and I have the same issue and it takes a lot longer for the GPS to lock (and its a bright sunny day).

I also tried dec's #9 kernel but when i access anything with gps (maps, nav, speedtest), my phone lags considerably and will usually reboot. I've since nandroided back to 8/24...
[Hero CDMA Android Development] t12icky0:
had the same problem..here is my solution. #8 unca(on 8/24 nightly). LOCKS within like max 10 seconds as soon as i turn it on.
[Hero CDMA Android Development] mdsj:
If you want gps working properly I recommend the 8/28 build with the #9 kernel. Works like a charm. Also use overclock or setcpu, put the speed up to 710 on screen and it connects quicker than ever. Hope that helps for the gps issue.
[Hero CDMA Android Development] srthimsen:
If you want to stop the texts on voicemail, use Handcent, ChompSMS, or similar to blacklist that number (9016, I believe). If you do switch, be sure to turn off notifications in your native messaging app (Home -> Messaging -> Menu -> Notifications [untick]), or you'll get 2 notifications for every text!
[Hero CDMA Android Development] theimpaler747:
No HTC apps/widgets will work with a non HTC framework rom. The texts that you get from voicemail can easily be blacklisted by Handcent or ChompSMS so that you don't receive notifications and so you won't even see the text. There is no "solution," only this workaround.
[Hero CDMA Android Development] theimpaler747:
Your phone most likely reboots because you've set your frequency higher than your phone can handle with set cpu or another over-clocker... What was your max frequency when you ran the uncapped kernel and your phone rebooted?
[Hero CDMA Android Development] jakejm79:
Don't worry about the GPS fix, it was only a supposed fix and I don't know if anyone ever found that it actually fixed anything, it didnt for me. If you are that worried you could always pull the apns-conf.xml file from whatever version of the nightly you are running (8/30) and edit it, push it back to your phone, delete the *.db files and reboot. That would mean you have the most upto date version and working MMS.

What I found to work for me for the GPS fix was to flash Fresh 2.3.3 and then go back to the Nandroid of Froyo I had been running. I have a theory to why this works:

Just like with PRI and PRL there is something related to GPS that is stored outside of the normal structure for ROMs, i.e. it doesnt get overwritten when you Nandroid back. The data gets corrupted on Froyo and renders the GPS unable to pinpoint your location. Flashing Fresh 2.3.3 allows access to that data again and allows it to be rewritten. Thus on nandroiding back GPS works again.
[Hero CDMA Android Development] aka_word:
Google add-on link is broken.
[Hero CDMA Android Development] grimm777:
OK, so I managed to get everything up and running, I was wondering if anyone else is having a problem with retrieving there MMS, I'm given the option to download them, but it usually freezes or just stops downloading, and help or suggestions, thanx.
[Hero CDMA Android Development] jakejm79:
Try this, I just created it, replaces the recent apns.conf.xml with an edited one and deletes the telephony.db file allowing it to recreate on reboot.
[Hero CDMA Android Development] shepkc:
Is anyone else having major issues with Market not loading/timing out? I cannot for the life of me get into the Market for the last 5 or so hours. :mad:
[Hero CDMA Android Development] asoong:
Thanks for your suggestion. I tried 8/24 with dec's #8 and #9. No dice... Please see below.

Thanks for your suggestion. I tried 8/28 (and 8/30) with dec's #8 and #9. No dice... Please see below.

Bingo! Flashing back got my GPS working again and it carried back to my 8/24 build. Its still about 2 blocks off but at least it locks almost immediately when I go outside again. Thanks!

@t12icky0 - now with the 8/24 build and dec's #9, I can get the GPS to lock. thanks for the help!

@mdsj - I'll try 8/30 later but if that fails again, I'll try flashing back to sense, then back to 8/24 and then to 8/28. Thanks again!
[Hero CDMA Android Development] theimpaler747:
I heard that the servers in the midwest are down... are you located anywhere in the midwest by any chance?
[Hero CDMA Android Development] asoong:
Thanks for the reply.

I did try clocking it to 768-480 (mimicking your settings I read from another post) when it rebooted. Again, freezes and the eventual reboot only happened when I accessed the GPS.

After a reboot, I believe the OC gets reset to 691-191(?). If so, the freeze and reboot happened without further overclocking and again after I access the GPS. This happened 3 times so I nandroided back to 8/24 where google maps seemed stable but then it wouldn't lock. The blue circle around my location was fairly wide, like roughly 4,000 ft in diameter. Flashing back to a sense rom as jakejm79 suggested seems to have fixed my issue. I'm now running 8/24 with dec's #9 set to 710 (like i had with test 4) and everything seems to work.

thanks again...
[Hero CDMA Android Development] theimpaler747:
Some phones just can't handle 768, or anything higher than 710 for that matter. I use it because I'm one of the lucky ones, and it works and blazes for me with no reboots :D
[Hero CDMA Android Development] asoong:
So where's the "I'm so jealous" smily? :D
[Hero CDMA Android Development] asoong:
side question

Side question: Has anyone noticed that Rom Manager (I have 2.0.2.5) has been a little flakey recently? When I open the app, I get a few error prompts. If I choose "Other" then I can usually get to the app. Once I select an action, like back up, restore, or install a rom, it'll just reboot the phone instead of performing the action. Eventually I can get it to perform the action requested but it usually takes 2 to 3 tries.

Granted that I've been flashing a lot more than normal recently but is this behavior normal?
[Hero CDMA Android Development] theimpaler747:
I actually did get what you're talking about once... when I finally got the app to open I selected fix permissions and that worked for me. Possibly a coincidence, but nonetheless, it works now.
[Hero CDMA Android Development] bigjustinturbo:
Thanks for this, it did the trick. And just for clarification, I was running CM6 082910 nightly, stock kernel, after having done a full wipe of my phone, so no previous builds were on there.

I can send and receive MMS fine, and GPS is still working normally like it has been for me. Also, I updated my first post a few pages back with a note pointing to your latest post.
[Hero CDMA Android Development] shepkc:
Yup. I'm in Kansas City. Well, that makes it tough to get a new ROM up and running right now. Dammit! Can't get through the initial Google setup either. Nandroid to the rescue I guess.
[Hero CDMA Android Development] theimpaler747:
Very true. Always nandroid. :)
[Hero CDMA Android Development] asoong:
Dude! You rock! So far so good!
[Hero CDMA Android Development] theimpaler747:
Cool cool :) let me know if you need anything else.
[Hero CDMA Android Development] james33440:
Why with rc1 does my memory drop to below 30 within a hour or so and the phone bogs down?

How can I increase the memory? I didn't notice any gains with autokiller so I uninstalled it. I haven't had any luck in the past with task killers so I haven't tried that yet.

I'm running the latest #9 uncapped kernel with the latest battery tweak.
[Hero CDMA Android Development] aven_soulgazer:
Thank you for the work and effort. Wish I had the know how. I assume the file is attached, can't see it in xda app though. Will grab it when I can get on a PC.

Thank you very much
[Hero CDMA Android Development] aven_soulgazer:
There is no sense framework so HTC Widgets wont run. There is talk of getting 2.2 with sense working if the legend gets it though. Who knows if the hero has enough resources to run it very well though.

As for blocking the text people are using handcent and blocking that number within the handcent app
[Hero CDMA Android Development] dsMA:
Sorry for the misunderstanding lol What is it about having wifi turned on that prevents you from downloading mms?
[Hero CDMA Android Development] theimpaler747:
Sprint :) you have to be on data to get mms since sprint makes you access mms via your account with them

Sent from my HTC Hero running froyo: take that, Sprint!
[Hero CDMA Android Development] TheRonin:
I am having this exact issue, just spent 2 hours with Care and they finally just said "we don't know". I cannot get to any Google services over 3g. Wifi works fine. I Ruu'd back to .6 stock. And, im in KC too.
[Hero CDMA Android Development] jakejm79:
http://www.mediafire.com/?r34f47r16yob4um

Try that.
[Hero CDMA Android Development] theimpaler747:
I don't think changing roms will help unfortunately, as this is a sprint tower/server issue

Sent from my HTC Hero running froyo: take that, Sprint!
[Hero CDMA Android Development] jakejm79:
Having wifi on does not mean that MMS wont download, if you have wifi on and try and download a MMS then it will open a mobile data connection along side the wifi. The only way turning on wifi stops MMS from downloading is if you have a widget or app set to disable the mobile data connection when wifi is on, under default conditions wifi being on or off has no influence on MMS receiving.
[Hero CDMA Android Development] theimpaler747:
That's not how its always worked for me... I have to manually disable wifi and then try

Sent from my HTC Hero running froyo: take that, Sprint!
[Hero CDMA Android Development] shepkc:
So, it's weird. Using my fiancee's Moment, I can access the Market, and google.com, but Maps is slow to lock or times out. On my Hero, I can't hit google.com, Market or Maps, but I can get my location from both SCVNGR and FourSquare.

I can also hit just about any site other than google.com on the browser.:confused:

I nandroided back to my RC1 setup from a clean wipe of the 8/30 nightly and brainfuct kernel. I had also re-flashed GAPPS when I did the clean install of 8/30.
[Hero CDMA Android Development] TheRonin:
Same exact thing, my wife's moment is fine. My hero cannot sign into any google services over 3g, wifi works fine. And im in KC. soooo glad I checked now i know im not going insane by myself.
[Hero CDMA Android Development] jakejm79:
Using the stock messaging app or something else?
[Hero CDMA Android Development] theimpaler747:
Sprint is probably having server errors with the Hero... it wouldn't be the first time; they already had issues with the market servers on the hero earlier this month.
[Hero CDMA Android Development] theimpaler747:
Handcent... perhaps that's why.
[Hero CDMA Android Development] shepkc:
Found this on the Sprint forums...looks like it's not just us.

http://community.sprint.com/baw/message/208145#208145
[Hero CDMA Android Development] theimpaler747:
Like I said, sprint is having issues.... bad sprint, bad :P

Sent from my HTC Hero running froyo: take that, Sprint!
[Hero CDMA Android Development] Vandelay007:
Tried out 8-30 nightly - no GPS so I went back to my Nan of 8-25

Sent from my HTC Hero with Froyo...
[Hero CDMA Android Development] andygu3:
Try 831
[Hero CDMA Android Development] schmooo:
its the #9 kernal causing this it does the same to my phone, the #8 does not have this memory leak also im on the 8/30 nightly with stock kernal ocd to 691 and its faster then the other kernals ocd to 729 and 768 and the stock kernal also holds memory correctly. im using autokiller set to extreme its keeping memory around 55-60 for about 24 hours now
[Hero CDMA Android Development] vortex91:
can someone lead me to where the sprint original visual voicmeil apk is at?
[Hero CDMA Android Development] aven_soulgazer:
Thank you very much for doing that. Much appreciated.

I need to look into theming so I can contribute something myself
[Hero CDMA Android Development] gadgetcraze:
I am on this RC for the last 15 days or so with colin's battery tweak. I dont find any real problem with this. Any reason to flash any of the later nightlies?
[Hero CDMA Android Development] rickyq12:
Jake, I just flashed the 'fix froyo mms fix.zip' and my mms is working smooth. Thank you so much for this. This was a huge help. Keep up the good work.
[Hero CDMA Android Development] theimpaler747:
Look at my signature below (not the froyo one, the one lower than that make sure you're on a computer :)

Sent from my HTC Hero running froyo: take that, Sprint!
[Hero CDMA Android Development] theimpaler747:
Not really... some are a bit faster I think but most break mms and GPS

Sent from my HTC Hero running froyo: take that, Sprint!
[Hero CDMA Android Development] whoiswes:
Here are my findings in regard to some of the issues mentioned above:

MMS - works fine for me (on sprint) for both sending and receiving.

Lock screen delay - without JIT enabled, I have about a second delay. No lag otherwise, including when playing music. With JIT enabled, I have about the same amount of lag. Either way it doesn't bother me as it's probably due to some of the power saving features of the ROM. I'll take a 1 second delay for improved battery life ANY day.

Gallery3D - replaced with Gallery2D and I'm one happy camper.

Things I've noted:

With JIT enabled, I was actually having music skipping issues this morning, which I've never had before. The entire phone was slow and laggy, to the point where screen redraws within the app drawer were painfully slow...scrolling was basically a stutter from one screen to the next. I have a class 6 card so it shouldn't be due to hardware. I did notice that disabling JIT seemed to resolve the issue completely, for both the music skipping and the overall slowness. For now, JIT is going to stay disabled. I didn't see any appreciable gains with it on.

I can't tell you how happy I am overall with this ROM - it is extremely fast and has been extremely stable for me, so much so that I loaded up my wife's phone last night as well. Thanks to Darch and the entire Cyanogen mod team, and as soon as I get a chance I'll be sending a donation your way!