yashsingh1/xdaforums huggingface dataset:
[Fascinate General] sarkozy:
It will be fixed in the next build if the issue is manually corrected in time.
[Fascinate General] wideopn11:
Just downloaded nightly...now the fun begins. Which one to flash first.

edit: Flashed build 3, no issues so far. *fingers crossed

Edit: lost signal bars, but 3g works.
[Fascinate General] dbcalo:
So far so good here. The only thing I've notice so far is that the signal strength icon is stuck, but that's not a huge issue (#3).
[Fascinate General] Groundhound:
Same for me, signal bars are non-functional but otherwise all seems ok. Glitch was replaced so no OC & UV. Upon reboot I had to toggle airplane mode to get data to start, but I had to do that before.
[Fascinate General] Rick S:
Is everyones mms working on nightly #3? Mine just says sending...
[Fascinate General] Headcase8911:
Signal bars work fine on jt's latest build though.
[Fascinate General] LakerFam0824:
So just flash as normal? Or do we use rom manager?
[Fascinate General] Headcase8911:
Rom manager isn't functioning yet, but soon. Just flash as normal for now.
[Fascinate General] 00ffej:
Is it just me or does the op for the new nightly not include the ODIN package for cwr, as it says it does? Apologies if I'm just not finding it.:confused:
[Fascinate General] sageDieu:
In JT's thread he said Android 2.3.5... was that a typo or is that real and if so what's new?

Sent from my MIUI SCH-i500
[Fascinate General] skynet11:
It's no typo - the build actually exists - afaik just minor bugfixes.

Another Fascinating post by my XDA app...
[Fascinate General] 00ffej:
Starting from rooted stock... if anybody could point me to the cwr 3 tar package that would be awesome
[Fascinate General] welcomebob:
Swipe

Whats the liklyhood of someone creating a zip to be able to install the full verision of swipe on CM7?
[Fascinate General] spartan.062:
No one NEEDS to. Go to the Swype website and sign up for the beta of the most recent version.

Back on topic: Nevermind. Found changelog.
[Fascinate General] welcomebob:
one question, or really two. When i install another nightly, do i have to do*228 to reativate? Is it the ROM, or kernel, or both, when that needs to be done, or is that only if a full data wipe is done, and wipeing cache and dev cache not needed to activate?
[Fascinate General] Keithn:
It appears to work fine since you just set it to use the current recovery, unless you mean the features of the paid for Rom Manager which I haven't tried

MMS doesn't seem to be working for me with #3
[Fascinate General] Headcase8911:
I wipe cache and dalvik, then flash new nighlies. *228 will never hurt.

As of right now I think jt's 7/17 build is the best choice. Signal bars/mms don't seem to work on nightly #3. Let's see what #4 brings. Can't wait for rom manager to be fully functional.
[Fascinate General] Sqrls:
I'm currently running the 7/17 cm7 ROM with the GLITCH-LL kernel. I previously was using the OTB kernel for cm7. The only issues I currently have are low call volume, no flashlight apps work, and autobrightness doesn't work (just sets it to 30%constant). However, Im not completely sure as to why, but BLN is up and running on my phone with no problems even tho it technically should not be and I don't even have the app installed.

The only real difference I can see with my flashing procedure for upgrading to newer builds compared to the general consensus as to how to do it, is that I :

1) Reboot Recovery.

2) Wipe Cache Partition.

3) Wipe Dalvik Cache.

4) Flash newest CM7 build I want.

5) Flash kernel I will use (currently glitch-LL).

Note, I DO NOT reboot between flashing ROM and kernel. This is because I believe cache built on reboot might cause software conflicts between different kernels.

I have had no reboots, no missed calls, no issues entering or waking from deep sleep, no bootloops, or any other install issues I see mentioned frequently.

Hopefully this might help someone with fixing their install or getting bln working as well.
[Fascinate General] thekylebrody:
Sad this finally came now that I'm getting rid of my fascinate for a Dinc2 or Charge. Oh well hopefully ill see more CM7 love in my future!!
[Fascinate General] baron4406:
Found another weird glitch in CM7, just got a call from my wife who has a special ringtone I downloaded from Zedge assigned to her, but what played was a random sound file from my SD card not the ringtone I had assigned from her.
[Fascinate General] Jazz848:
Curious... did you set that up on another Rom prior to CM7?
[Fascinate General] baron4406:
No i set it up on CM7, I've actually been on cm7 for a week or two. I'm just trying to throw bugs out there in hopes of getting a stable build.
[Fascinate General] Sheriff Austin:
On release #4, and my cell service will not activate, even after getting an "activation ok" from *228.
[Fascinate General] netpa:
I had the same issue. Try rebooting your phone, that worked for me.

Different issue that I'm not sure has been mentioned but I didn't see it - it seems like my phone only gets notifications if the screen is on. Stuff will come in, but it won't sound/vibrate/anything until I turn the screen on and then it'll give me everything that has come in since the last time the screen was on all at once.
[Fascinate General] baron4406:
The exact same problem I had, no notifications unless the screen was on
[Fascinate General] netpa:
Same for builds 4 and 5.
[Fascinate General] Headcase8911:
It looked like the signal bar fix was merged in on build 5, is that true?
[Fascinate General] inmybrain:
I'm currently on build 5, it doesn't seem to be true on my fascinate.

Sent from a CM7 nightly mod testing fascinate.
[Fascinate General] netpa:
Same here.
[Fascinate General] netpa:
I'm pretty sure this is fixed in build 5
[Fascinate General] papstar:
Negative. It was a dbm text fix, not a signal bars fix.
[Fascinate General] jt1134:
Uploading a signal bar fix to gerrit shortly. Koush merged the mms patch earlier today, so it should work on the next nightly build.
[Fascinate General] edward_h:
low call volume elaboration?

First off, props to jt. Using his past ROMS and now CM7 makes dealing with Verizon bearable because I can be my own tech support.

I'm on jt's 7/17 build, with the dock and compass fix. The *only* thing that I am experiencing as an "issue" is that others are telling me that I'm hard to hear in a call. I've confirmed that my voice is a bit low by swapping phones with my sister, and yes, the in call volume on her phone was at max.

I've been searching terms like "low call volume" trying to find some explanation of other's problems with this issue, but it seems that most people are referring to the headset volume while in a call, not their voice volume to others. Is this correct? I have not yet had any issues with my headset volume in calls...

Anybody have any comments/suggestions as to why my voice is hard to hear, other than my theory that several of my commenters would be considered by most to be "old" and hard of hearing :p Have the nightlies yet offered any improvement on the call volume issue?
[Fascinate General] iztel:
It's an issue with software. Supposedly it will be worked out in the next glitch kernel. A lot of people myself included are anxiously hoping the devs will have some free time to fix it soon. Once that's sorted jt's cm7 will be absolutely perfect.
[Fascinate General] Efpophis:
I've been having the opposite problem with in-call audio. The other side can hear me just fine, but I have trouble hearing them, even when my in-call volume is maxed. However, when I listen to a google voice message with the same in-call volume maxed, it's REALLY loud! I wish live calls would behave the same way as google voice playback!

Anyway, I've also heard of your issue, and maybe even had it once. What I have done is to download the voodoo control app and use it to turn off all the sound options. There is a microphone sensitivity option in there somewhere that will likely help you with your issue. Disabling a bunch of the others may give marginal improvement to people experiencing my issue as well .. at least I noticed an improvement.

Good luck!
[Fascinate General] Bubbadogg14:
Great work jt!!! Thanx for everything... Its sad 2 hear your leaving xda but things r getting a lil outta control here
[Fascinate General] netpa:
Notifications while the screen is off are for sure fixed, as is MMS :) The signal bar still isn't working but I'm completely okay living without that lol.
[Fascinate General] eshu68:
I still face the phantom ringer problem? Anyone else facing the same issue?

I checked up my call usage from Verizon and looks like no one had called me during the phantom ringer. My guess is that the sound is triggered when the phone enters deep sleep?
[Fascinate General] lagbot7000:
I've experienced the random sound file bug as well. Instead of my usual notification ringtone, a random MP3 from my sdcard started playing. Running the 7/17 release with Glitch kernel.

Sent from my SCH-I500
[Fascinate General] speedingcheetah:
Volume with different kernels

So i have tested different kernels out...results were that OTB kernel was the best for sound volume AND clarity....second place was the OPBJ

What I did was to call my home voice mail, listen to my greeting to test in-call volume, then leave a message to test the microphone sensitivity and volume. I then checked the message on my home land-line phone, comparing each message to the other.

The OPBJ kernel posted somewhere actually had the the loudest sound overall, but the microphone seemed to be over amplified or something, as the message i left sounded muffled, sometimes distorted if I spoke louder then normal. The in-call volume was the best of the bunch, most adjustable and the loudest, without having to to the down then up again trick..but the microphone clarity was the worst...

The OTB kernel sounded better on both ends than any CM stock kernel...still have to do the volume down then up trick to get full in-call volume, but its tolerable. Microphone volume wasn't as loud as OPBJ was, but was much clearer and not muffled or have the over electronically-amplified sound as the OPJ kernel did...

Also, note, these were tested on CM7 the 7/25 build, with Hi-fi record and DAC direct un-checked in Voodoo control...

Just throwing this out there..
[Fascinate General] vlucchetti:
Not to flame, but can we get back to discussing what works with the nightlies and not what is being done with older versions (7/17 through 7/26)? There are other threads for that.
[Fascinate General] Headcase8911:
It looks like rom manager has nightlies now.
[Fascinate General] speedingcheetah:
This does have to do with nightlights, as people are using these custom kernels since they are the only ones out right now if they want the fancy stuff...

I have tried the same setup on the nightly builds and got the same results...until the custom kernels are updated, the nightlies use a different stock kernel and results will vary per build depending on if the the kernel is updated by the CM team....or if the user flashes one of the now considered older kernels to a nightly build..

All in all, I found older builds to be the most functional and stable builds at the moment...but that will change once all Jt's fixes are implemented...gonna give till build 10 till I flash a nighty again...

EDIT: BTW, the thread for the older builds has been locked/closed..
[Fascinate General] mxpxrobbie:
I am loving CM7, but I prefer GO Launcher over ADW... I noticed the Cyanogenmod Settings screen is baked into the settings for ADW, and I don't want to break anything, but I'd really like to use GO Launcher instead.

Is that possible?
[Fascinate General] smilepak:
running 08/02 build...

When doing *228, it goes through activation process. Press 1, continue with activation, "voice message said" activation was successful.

On screen it said "Problem with activation, your phone did not activate"....noticed all signal bar was "X" out and no signal whatsoever.

Reboot the phone, battery pull, same problem. No dice.
[Fascinate General] Groundhound:
I'm using Go Launcher with CM7 nightly #6, no problem.
[Fascinate General] mxpxrobbie:
Thanks! I tried on an earlier build and I ended up having to restore...
[Fascinate General] Headcase8911:
Nightly number 7 is out now I'm curious if the signal bars or fixed. I cannot test right now.
[Fascinate General] Headcase8911:
Double post
[Fascinate General] 08cherd4:
How's the battery life? Still an issue?
[Fascinate General] mikeytusa:
Just installed nightly #7 -- signal bar is still broken.
[Fascinate General] kuronosan:
Man. Jt was right. People here just don't read through anything.

Activation was successful. It's normal for it to say "Problem". You reboot and it works. Simple as that.
[Fascinate General] lagbot7000:
Just upgraded to nightly #7 from the 7/17 build and it's running great. Wiped both caches before installing and flashed the Glitch kernel as well.

Around what time are the nightlies generally released? Tried registering for the nightly update notifications, but it just fails, as others have mentioned before.
[Fascinate General] speedingcheetah:
Whole bunch of stuff on the change-log for the next build(8)...seems they are finally getting things into gear...
[Fascinate General] aes55:
any word on whether in-call volume has been tweaked in nightly 8 ?
[Fascinate General] lagbot7000:
Looks like signal bars are still broken in build #8.

Sent from my SCH-I500
[Fascinate General] dr_w:
Can anyone verify in call volume and sensors?
[Fascinate General] bdanders:
Are the phantom button presses still a problem with the nightlies?
[Fascinate General] tlogank:
Does anyone else have super slow GPS locking? Mine is taking FOREVER to connect. Using latest nightly (but this has been a problem for a bit), EC09 modem. Am I alone in this?
[Fascinate General] stephenwdaniels:
GPSo Lock

I would say the GPS lock is mediocre. Not as slow as with some ROMS but not as fast as it was on my DInc2. Definitely not slow enough to get me off CM7. Too fast, too clean, too close to stock. Until VZW gets off its' ass and gets a nexus device, this is about as good as it gets.
[Fascinate General] tlogank:
just curious..what modem you on?
[Fascinate General] sarkozy:
Say what? There's nothing new on the gerrit review for the fascinate. A couple of bugfixes in cm code, but other than that all the other stuff has nothing to do with the fascinate. JTs signal bar fix is making its way through the review process, but it'll be a couple more days before its bundled into a nightly.
[Fascinate General] Ritchell:
Signal bar fix should be in the next nightly (#9)

http://cm-nightlies.appspot.com/?device=fascinatemtd
[Fascinate General] dr_w:
Honestly man, who gives a **** about signal bars. Just make the call already. Don't you think the in call volume is a higher priority? Theres bigger trees to fry if you catch my drift and I think you do.
[Fascinate General] aes55:
totally agree. i had to go back to TW for the sole reason that i couldn't hear calls if i wasn't in a completely silent room... the in-call volume issue is the only thing keeping me from cm7 :(

im not a dev, so i have no clue how to fix it - so i'll just wait patiently until our devs get it fixed. you guys rock, thanks for the hard work.
[Fascinate General] dr_w:
Same here, it's the only thing keeping me from cm7 too. Don't get me wrong, I'm extremely grateful of the devs, I just need functionality.
[Fascinate General] eibbed0001:
Number 9 is now available. I just booted up after installing it and have signal bars. Haven't checked voice volume yet.

http://download.cyanogenmod.com/?device=fascinatemtd
[Fascinate General] aes55:
i dont think in-call volume can be fixed until the 2.3 kernel source drops
[Fascinate General] Bubbadogg14:
My signal bars seemed fixed initially but according 2 my status bar I have had 0 bars for the last hour or so but I def do have signal
[Fascinate General] SotYPL:
Flashed #9. Signal bars working. Proximity sensor during the call still doesn't work as it should. It turns off display but can't get it back on. Have to press power to light up display and be able to end the call.

btw. is there any Accurate Battery mod available? Like that one: http://xdaforums.com/showthread.php?t=1164420 but for Fascinate.
[Fascinate General] jeremytheindian:
Radio Stops Working at Random

Is anyone else seeing problems with their 3g radio cutting out? My phone will be fine for a while and then even though the 3g symbol is in the notification bar I get no connection. Some time turning the radio off and back on in settings will work sometimes not.

I am on build 8 with EC09 radio. Would it help if I ODIN'd a different radio or reflash EC09? Thanks in advance!
[Fascinate General] Adr0it:
Mine does this too, not sure if it's when I switch towers or if it's when I lose 3G and regain it (at work I do a lot of driving in remote areas). Haven't had time to do any real testing. It seems to keep when I'm at home.

Toggling Airplane Mode on/off always fixes it for me.

Has been happening for me in 2 different builds that aren't nightlies with EC09. Pretty sure it's not because of the modem though. If you try flashing a different modem and testing it for me it will save me some time. I'm probably going to get some logcats soon.
[Fascinate General] jeremytheindian:
Thanks for the info I have been around some low coverage areas lately. I'll keep that in mind and pay close attention over the weekend.

Also, am I the only one that went into CM7 settings and switched my alternate signal display to signal text? At least that way I have an idea of my connection without bars. Seems to work fine.
[Fascinate General] mrbobhcrhs:
I flashed ec05 and it seems to be better then ec09 was, but still does it. I think with nightly 9 im having issues if both 3g and wifi is on at the same time (got to play with it more)
[Fascinate General] Headcase8911:
It looks to me like there may be some audio enhancements on the next build, link for things included in the next Nightly on the OP. I could be wrong, what say you? This is really the only major remaining issue for me.

Sent with a thankful attitude from gingerbread goodness
[Fascinate General] ssewk2x:
I spent a couple hours digging through the source trees for a few different kernels yesterday. I *might* have found a few things that could help the in-call audio issue. I want to test them first tho, and sadly my ubuntu install bit the dust last night.

I will hopefully get some time this weekend to do some coding, building, avoiding bricking, and testing. If my idea works, I'll communicate it to the kernel devs and hopefully go from there.

Edit: to answer your question, it doesn't look like anything going into the next build will help afaict.
[Fascinate General] Headcase8911:
Wow! That would be a major breakthrough, thanks for the info.
[Fascinate General] ssewk2x:
Well, don't get too excited, lol! I could also be waaaaaay off base. But I figure out doesn't hurt to give it a shot. I'll keep the forum posted :)
[Fascinate General] zaliva:
3g in Ukraine

Could somebody help me to make work 3g internet connection on CM? on other ROMs it's working, but not CM7. editing apns-conf.xml did not help.

im not verizon user. my operator is Intertelecom in Ukraine.
[Fascinate General] kevlar924:
gps since the nightlies

My GPS worked with my original installation of JT's CM7 builds, but once i've switched to installing nightlies, my gps appears to never got a lock anymore, does anyone have any advice/info/help on this?
[Fascinate General] dr_w:
Sorry to break it to you man but its not CM7. Its something you did messing around installing a rom here and a rom there. You need to flash back to stock and call verizon for a warranty replacement. Trust me, its a mind fcuk but it'll be worth the wait. I spent weeks going back and forth trying to get mine to work. Warranty replacement=only solution. Become one with it, don't fight it.
[Fascinate General] baron4406:
Flashed build 10 yesterday after the "stable" build of cm7 began giving me fits, wiped everything and installed. Alot of FC's everywhere so I totally redid everything, phone was ok for about an hour then I missed a very important call, first thing the lockscreen would not work, then when they called back I got the dreaded phantom ring all thru the call. Got sick of it and went back to TW ROM the powerwashed ED05. Unreal how much functionality you give up with these MTD ROMS, everything actually works now! So Im gonna have to wait until things get better before I flash back CM7, I need a functional phone. I feel kinda defeated now.
[Fascinate General] jt1134:
Lol reading is fundamental.
[Fascinate General] sfobrien:
Try turning your wireless on if you haven't done so.
[Fascinate General] bigmike88:
Another ukrainian who can't get 3g? Strange.....so strange XD
[Fascinate General] netpa:
I know this has happened to a lot of people. I'm on build 10, and my SD card got corrupted. Only thing is, when I select on my phone to format it, it doesn't. It starts giving me the "Erasing SD Card" message, but then it gives me an error saying the SD card is blank or has an unsupported file system. No matter how many times I try it gives me the same message. I'm about to format it with Windows, but I thought I might ask here before to see if there's a solution you guys know of that I can fix it from my phone.
[Fascinate General] Mikes30000:
Try repairing errors in windows first before you format
[Fascinate General] dr_w:
What up jt, you like that ****?

Here for you man. :)
[Fascinate General] kevlar924:
While I understand this will help it see me on Google maps it does nothing for my GPS except prove that maps can find my wifi signal, not GPS.
[Fascinate General] speedingcheetah:
So the change log mentions:

OMAP4: Added FM API to support FM on OMAP4 (android_hardware_libhardware_legacy)

Coming up for next nightly...might that be related to hardware acceleration support or something to help the sensors/accelerometers..
[Fascinate General] sarkozy:
Nothing to do with the fascinate.
[Fascinate General] speedingcheetah:
The why do they list these as included under the fascinate change log...

EDIT: I just noticed that all of the devices in their change log lists the same thing added to all the nightly builds for all the devices...so why in the world have it sort by device if they the changes are global...

How are we supposed to know what is for the fascinate or for another device...seems to me that if nothing is changed between nightly builds for a particular device..then whats the point of it auto-compiling and taking up server space for something that hasn't changed but making it appear that it as...then to have some here who flash a new nightly as soon as it comes out, and their waste their time...

Not trying to rant or anything, I just discovered that I was wrong for thinking that the page I was looking at was an actual changelog for the Fascinate and not CM7 globally...I think a lot of people may be surprised to know that..

The page I am referring to is: http://cm-nightlies.appspot.com/?device=fascinatemtd

O well..my misunderstanding...
[Fascinate General] t5noel:
I read on Development that the SD card problem is related to 2.3.5. That being the case they say the latest build with 2.3.4 is 7/25. Does anyone have a link to 7/25? It is no longer listed on the nightly.
[Fascinate General] speedingcheetah:
I was running JT's 7/26 build for a while, then had the sd card corrupt suddenly..can't remember if 7/26 is 2.3.5 or not...I am pretty sure the 7/17 is 2.3.4...

Anyway...I can't remember where I download jt's roms from...but I am uploading the 7/25 rom to my dropbox now...

JT's 7/25 CM7: http://dl.dropbox.com/u/21976551/update-cm-7.1.0-Fascinate-KANG-0725-signed.zip
[Fascinate General] thermom:
Does anyone knows how to fix 3g data issue in non verizon activated phones?
[Fascinate General] gabe565:
Why haven't nightlies been built lately?
[Fascinate General] Headcase8911:
That's a good question, I believe it's because people were reporting sd cards failing. I don't think they'll release any more nightlies until the sd card dibacle is resolved.

EDIT: It looks like build number 17 has been released, we'll see what it brings.