yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] pastorbennett:
You might not be hosed. It's possible that just the partition on the SD card is corrupted. To check if it's recoverable, use DISKPART. If you're running Windows 7, from the start menu right-click on Command Prompt and click run as Administrator. From the command prompt, type diskpart and this will bring up the partitioning command-line tool. type list disk, see which one is your sd card, then type "select disk" followed by the # of your SD card. After this, type clean, and if you did everything right, you won't get an error message. You can then try to re-format the disk. I'd recommend using the Disk Manager by right-clicking on My Computer, selecting Manage, then going down to Disk Management.

I hope this helps. If it doesn't, and you still have your receipt, Best Buy will do in-store exchanges for many brands that they carry if they are under the factory warranty. They will do this even if you are returning outside of the normal return policy grace period. They don't do it for all brands, but do have agreements with many manufacturers to do warranty exchanges in-store.

Most SD card manufacturers have a lifetime warranty on their products. So unless you tell them you fried it on your phone, you should be in the clear.
[Fascinate Android Development] FDro:
Build 17 is up, for the ones that were eager to flash something new.
[Fascinate Android Development] Mikes30000:
Who is feeling brave to give #17 a try? Supposedly the sd issue was fixed and tons of other changes were introduced
[Fascinate Android Development] FDro:
I've been on build 14 and JT's v3 kernel for a few days now and it was working fine(mind you, I've had my sdcard go twice on prior builds). Flashing build 17 right now.
[Fascinate Android Development] Mikes30000:
Sweet. Keep us posted. I would like to flash back to this but I don't want to hose another card.
[Fascinate Android Development] decaydance99:
Also flashing 17. Still have had no sd issues. I'll report back.

Sent from my CM7'ed fascinate
[Fascinate Android Development] kuronosan:
Only ones with any issues were the ones using stock kernel, so if you aren't using it, you aren't in danger.
[Fascinate Android Development] Azuma73:
I've been using CM7 for a few weeks now, I friggin' love it!! But, just started getting some weird goings on. Keyboard keeps popping up at random, apps just kill themselves or I'll open an app and it will just go back to home-screen real quick-like. Could that be due to the fact that I have a very poor signal in general? Also, the low audio/call volume issue, but I know that stuff is being worked on.

I've yet to flash any of the nightlies. Seems like they have more problems than I'm currently having since they're experimental and what-not!! I was just wondering if others were having similar issues and maybe had a solution to these strange "quirks" ....if you will?

Thanks guys!!!
[Fascinate Android Development] raymechanic:
Shakes starting to subside

flashed 17 and still no problem. still on froyo bootloader

I'm a flashaholic and can't be helped
[Fascinate Android Development] smilepak:
Flash 17 from 14. no issue so far....

Really wish the Sound Dock Replicator would work...
[Fascinate Android Development] SeatownGST:
How would one flash it if the SD card isn't working? Is there an ODIN'able .tar of the latest nightly, or just zip?
[Fascinate Android Development] decaydance99:
Nope there is no other way:( you need a sd card

Sent from my CM7'ed fascinate
[Fascinate Android Development] SeatownGST:
yiiiiiiiikes I had that suspicion :(:(:(

crap. given the huge blitz of baked SD cards, is there a way to compile the nightly as such? repair the phone via odin, and then reformat the SD card when the new rom/kernel are all overwritten and rebooted?
[Fascinate Android Development] Ritchell:
Why exactly can't you reformat your card from inside whatever ROM you're currently running? If that's the case, I doubt flashing or ODINing a new ROM will do too much good.

If you're trying to repair your card from inside of a working ROM, but for whatever reason your ROM isn't working right now, why not go back to stock ED05? ODIN and repartition with the atlas pit file, see if it recognizes and successfully reformats your SD card, and then go forward from there to a nightly or whatever you want.
[Fascinate Android Development] ivorycruncher:
I believe JT said you could flash the 7/18 kernel patch over the top of any nightly to get that working. You'll just end up trading any kernel updates present in the nightlies for dock audio, as it replaces the kernel. He also said he will be working on updated kernels for the nightlies that include dock audio and BLN, but there is no ETA on those yet.
[Fascinate Android Development] Teng0ku:
Is anyone else mms not working on #18 nightly?
[Fascinate Android Development] brickbeats:
MMS video hasn't worked for me on none of the CM7 roms including build 17. I even tried to make a hybrid froyo/cm7 mms.apk to make it work to no avail. I had to switch back to ed05
[Fascinate Android Development] mxpxrobbie:
Can anyone confirm if the SD card problem was fixed yet? Mine is randomly unmounting, but so far it seems to be OK. I'm going back to a 2.3.4 version just to be safe.
[Fascinate Android Development] smilepak:
I haven't had any SD issue with these nightly. I did got SD corrupt when I did the 1.8.5. of MIUI :-(
[Fascinate Android Development] SeatownGST:
aye, I suppose I could start all over again, that's true. might as well, it's reporting damaged still despite trying to format from within settings. it doesn't mount to a computer either - so it's just toasted from within android. won't even get going. I will nuke it all from orbit again.
[Fascinate Android Development] deitiphobia:
I've braved the nighties now since 13. Lost a 16 gig SD card along the way.

Currently on #19. I'm having issues with very slow GPS lock making navigation a pain in the ass to use. Also issues with MMS not working with photos. Sometimes my SMS don't go through either when they are larger amount of text. Don't know what the hell is up with the SMS.

My call audio is OK I think, but I get long delays after hanging up a call where the screen stays black for a few seconds before coming back to life. So I can't press end... I have to wait for other party to hang up usually. Would love for the phone to immediately wake the screen when I pull it away from my face.

Also having issues with WiFi. It doesn't work half the time and I have to toggle wifi on and off till it does. That bug slows me down big time.

I feel like I don't have the time or desire to switch back to a more stable froyo ROM, so I'm gonna power through with the nighties and see if some of these quirks are resolved over time.

Otherwise, the ROM is fast and responsive and works great outside of the above bugs.
[Fascinate Android Development] m0r0n3s:
When I was on TW Froyo, I was able to use a security pattern when I configured my exchange email account. But since I moved to AOSP Gingerbread it requires me to set a PIN or password instead. I can no longer use a Pattern as security.

Anyone knows how to disable the PIN requirement (I'm OK with using a pattern, but not a PIN/PWD)

Thank you
[Fascinate Android Development] smilepak:
Finally found a nice stable setup

CM7 Build 20 + JT's V3 Kernel from ROM Manager + Volume Control Plus

Galaxy Sound Dock Redirect = Works

Low Call Volume = Resolved

Stability = Check

DSP Manager = Work

SMS = Work

SD Card Issue = None

WIFI Stable = Check

MMS = Haven't tried

Using GO Launcher = Smooth

I am backing this setup up...just in case..ehhehe
[Fascinate Android Development] dividebyzero:
Try the glitch kernel. I have a slight wifi issue if I try to use it when it turns on automatically from reboot and sometimes gps but toggling fixes both quick and until next reboot. My audio is ok too. Just need to tweak in voodoo control. I think turn off tweak for music and hifi record. Not site but mine works.

Just needed to experiment with the different leakages and voltage control. I think I can get 1500 stable but I'm still working on it.
[Fascinate Android Development] dr_w:
Did you test the in call volume? This is FANTASTIC news is you are right about everything.
[Fascinate Android Development] smilepak:
Volume control plus fixes in call volume issue..
[Fascinate Android Development] vlucchetti:
Have to try that with 20 and the Glitch DEV kernel.
[Fascinate Android Development] kuronosan:
It works like a charm.
[Fascinate Android Development] Azuma73:
So let me make sure I got this right, Build 20 fixed low in-call volume/general audio issues?
[Fascinate Android Development] kuronosan:
No, VC+ fixes it. I just confirmed that it will work with Glitch kernel.
[Fascinate Android Development] smilepak:
Build 20 doesn't fit it. An app called Volume Control Plus fixes it. Works well with several kernel tested.
[Fascinate Android Development] gunm3tal:
Sorry but need to clarify;

This app (volume control +): https://market.android.com/details?id=com.cb.volumePlus&feature=search_result

Fixes the issue?

or does this app (Voodoo Control plus): https://market.android.com/details?id=org.projectvoodoo.controlappdonate&feature=search_result

Only reason i'm asking is because some people reference the "fix" as VC+; some mention that voodoo control plus fixes it and others mention that volume control + fixes it.
[Fascinate Android Development] decaydance99:
Will roms like this work on a tellus fascinate, I have A friend who wants to give it a shot but he has the telus version. So will VZW fascinate roms work on Telus fascinate?

Sent from my CM7'ed fascinate
[Fascinate Android Development] Kaik541:
no, which is why the CM wiki clearly states it won't work on the Telus Fascinate 3G+
[Fascinate Android Development] nunyazz:
I think this: https://market.android.com/details?id=com.TEST.android.lvh&feature=search_result

is the app in question.
[Fascinate Android Development] Merman1983:
Can someone confirm this ^ seems the most likely culprit?

I may give the free version a try and if it works the pro version will be purchased for support.
[Fascinate Android Development] gunm3tal:
From what can tell, this works similar to DSP Manager already included in CM7. This basically allows you to push the volume further than DSP Manager. This app, however, only changes the volume on Headset/Speakers/Bluetooth devices and nothing mentioned about the in-call volume.

Still gonna try the paid version though since it's free.

You can get it from his website for free....just need to sign up for his website.
[Fascinate Android Development] ssewk2x:
I'm working on the in-call audio issue by tweaking some of the gain settings in the audio codec driver in the kernel. If it works the way I think it will, it should be pretty easy to port the fix into any of the other GB kernels that suffer from the same issue. I just need the time to build and test my fixes, and that seems to be very scarce for me these days.

It's been my experience that these volume apps don't work, they just give you all the volume options in one place and possibly a few more steps. But max is still max, and that's still too damned quiet. Of course, if you notice an improvement, then more power to ya :)

Just wanted to let the community still irritated by this issue that you have not been forgotten.
[Fascinate Android Development] gunm3tal:
Awesome. But I do agree. From my tests performed just now. Adjusting volume from volume control + app does not do anything. The aforementioned app and as I mentioned, Volume+ is similar to DSP manager. While installed with my preference, it even FC'ed DSP Manager. Furthermore, it did not do anything in regards to the in-call volume issue. Though ringer was noticeably louder.

Like you said, unfortunately, 'max' is 'max' can't wait till you get your in-call volume fixed and share it within the community.

Anyone else having issues with BLN Notifications?

-- I have JT's Kernel v3 (Latest one from the ROM manager) and running build #21 CM7

-- It used to work....but suddenly disappeared =[. I reverted back to JT's v2 kernel with no luck. I hope this wasn't accidentally removed by build #21. I will try to revert back to 20 and see.

NEVERMIND! Still running Build #21 & kernel v3. Battery accidentally fell off, when my phone booted and tested BLN; it WORKED! Lucky fix I found for those of you having the same issue!
[Fascinate Android Development] smilepak:
For me it was this one

https://market.android.com/details?id=com.cb.volumePlus&feature=search_result

Fixed the issue
[Fascinate Android Development] smilepak:
This is the version I use and fixed the in-call low volume issue

https://market.android.com/details?id=com.cb.volumePlus&feature=search_result

It is free and runs great!

Currently running

CM7 Build 20 + JT's V3 Kernel + Volume Control + (app link above)
[Fascinate Android Development] gunm3tal:
From volume control + what settings did you change specifically?

Or did you just install it and fixed your in-call volume issue?
[Fascinate Android Development] smilepak:
Install, adjust in-call volume from default 12 to 15..
[Fascinate Android Development] blahbleh:
my max is only 5...it is 15 for media. Using cm7 + glitch v11..
[Fascinate Android Development] adude247:
just flashed to build 22 and everything is still rock solid for me...
[Fascinate Android Development] gunm3tal:
After install, everything was already set to max. Including voice call volume (15).

dialing verizon test call #832 is fine, but testing a few phone calls with 5 other people with 5 different phones still sounds too low.
[Fascinate Android Development] MJMcMahon:
Just downloaded update 21 and tried to apply it and, for some reason, the SD card wasn't readable inside orange recovery. It's still readable with the device booted and inside Windows, so I'm backing up and going to try and reformat. :(

wish me luck!
[Fascinate Android Development] smilepak:
Strange...I've been using the calls for the past few days..been working fine...

Is your low in-call issue via bluetooth or just holding the phone? I've only tried with holding the phone, haven't tried bluetooth yet
[Fascinate Android Development] adude247:
is anyone having an issiue with a custom shut down animation not working I'm on build 22 and noticed that even though I put the video folder in the media file with my bootanimation, the bootanimation works but the shutdown doesn't...
[Fascinate Android Development] Kaik541:
there is no shutdown animation on CM7.
[Fascinate Android Development] adude247:
Well that explains that thanks...
[Fascinate Android Development] adude247:
just flashed to build 23 and it still seems soild...
[Fascinate Android Development] gunm3tal:
Just holding the phone.

When changing the Call Volume you can hear the beep coming off the phone not the speaker on the back.

Anyways, glad that this app fixed it for you and some other users. Like they say, phones act/respond differently.
[Fascinate Android Development] djk21108:
What I mean is. This is shaping up well!
[Fascinate Android Development] jt1134:
What?

Uh...no.
[Fascinate Android Development] Bubbadogg14:
Lol... Good 2 hear from u over here n glad ur still checking this 2 keep some of the nonsense in check
[Fascinate Android Development] sageDieu:
there's a guy making progress on the issue but it hasn't been resolved yet.

Sent from my MIUI SCH-i500
[Fascinate Android Development] Shakes The AssClown:
Do the proximity sensors work correctly? I am on build 20 but notice when I'm making a call, that if I pull the phone away the screen still stays black...I have to hit the volume rockers to get it to come up. How are the newer builds. I see it's up to 23 now..wondering if I should upgrade from 20.
[Fascinate Android Development] adude247:
23 has the same issue...
[Fascinate Android Development] adude247:
just flashed 24 runs fine...
[Fascinate Android Development] smilepak:
http://cm-nightlies.appspot.com/?device=fascinatemtd

If nothing is listed, doesn't seems much of a use to keep flashing each nightly huh..nothing changed..
[Fascinate Android Development] erivnocmc:
:( I hope that something will change ...
[Fascinate Android Development] exzacklyright:
Haven't really been keeping up with the thread but is the in-call volume fixed yet? thanks.
[Fascinate Android Development] dividebyzero:
When it happens you will know. Archangel Gabriel will personally come to your door and hand you an invitation. It's that big of a deal. There will be no mistake that it's fixed.
[Fascinate Android Development] Shakes The AssClown:
Is there anyway to get the phone to open up to the dialer? It either defaults to my favorites or the call log.
[Fascinate Android Development] raymechanic:
Mine opens on the last item I selected on the top bar
[Fascinate Android Development] Shakes The AssClown:
I tried that and left it on the dialer and closed out, but it opens to either the favorites or call log.
[Fascinate Android Development] raymechanic:
Open your dailer then hit menu softkey scroll down to default (on the end/bottom of list) open it and change to open dailer as default action
[Fascinate Android Development] adude247:
Seriously LMAFO....
[Fascinate Android Development] wyseguy77:
Lmao that's some great stuff.
[Fascinate Android Development] sadisticdemon:
I used this rom and it crashed my phone I had to completely take my phone back to stock and now I can't reroot
[Fascinate Android Development] Shakes The AssClown:
Hmm..wiped cache partition and dalvik and tried to flash nightly 25...now I get the infamous rebooting issue. Tried fixing permissions and such...no go...looks like I may have to re-do everything....dammit all to hell. ;-)
[Fascinate Android Development] printing724:
fwiw...success... wipe 3, odin'd EC09 over ed01, odin'd recovery in op, wipe 3, flash nightly 23 over commrom 2.1, no issues. Smoother/faster, gps lock in seconds. Only thing I miss is my flashlight app which no longer works (knew that beforehand). Call volume seems fine to me.

I even waited until a spare 16g sd card arrived from newegg, didn't need it, have a spare now.

My thanks to devs for making my new daily driver possible.
[Fascinate Android Development] SeatownGST:
is there any way to be certain the SD card fix is integrated? what will we be looking for in the GB roms/kernels?
[Fascinate Android Development] Syndacate:
I've noticed this issue too. I don't think it's a problem with the proximity sensors, I think it has to do with the settings. Try turning off the "use proximity sensors in calls" or whatever the heck the option name is - dig around in the extra preferences, you'll find it. See if that helps.

Me? I've been having issues with no 3G when I have it (got to airplane mode it on/off), SD Card, had a couple FC's in the beginning, but nothing as of the lately nightlies. My largest issue is when 3G dies and I don't get e-mail.

There's still a few more kinks to be ironed out in this ROM, but it's a very solid ROM (other than the card yum yum issue) and I will definitely be switching back to it. That being said, I have a 3000 mile trip to go on in 7 days, and need something I trust very well, and which is 100% stable. So for the next couple of weeks I shall be using UKB 2.1 + OTB 1.6 + EC09 radio.
[Fascinate Android Development] Charm8er:
Is anyone else having issues with wifi? I have had trouble since build 20. It disconnects alot and I have to turn wifi on and off to get it working again. Sometimes that doesn't even work and I have to reboot or even battery pull. I have also been getting issues where the phone randomly rebooted into safe mode. I have wiped all 3 and re flashed several times.
[Fascinate Android Development] vlucchetti:
Just installed 26 with the new kernel. Fast, smooth, voltage control certified, oc'able. Checked with a caller, in call volume okay (but ymmv). Can't send pics via mms, but otherwise nice.
[Fascinate Android Development] kuronosan:
Which new kernel? Glitch, or stock?
[Fascinate Android Development] vlucchetti:
The stock Kernel in build 26. OC up to 1300. Was running Glitch but I like this kernel.
[Fascinate Android Development] Headcase8911:
No......the earth will tilt another degree or so when the volume/audio issues are fixed.
[Fascinate Android Development] adude247:
I thought the Angel Gabriel was going to knock on the door with an invitation, damn it I better get one...lol
[Fascinate Android Development] Talek:
Anyone else having problems where you reboot your phone by going into the menu from holding down the power button and the phone doesnt reboot, it just turns off? (I also get this trying to get into recovery that way --> the way you're supposed to get into recovery...)

Also noticed my Square App's credit card reader (plugs into audio jack) does not work in CM7. Worked perfectly in TSM, any ideas on what may cause that? It is the one and only reason I'm considering leaving CM7... I love CM7 but I really need that card reader to work.
[Fascinate Android Development] tkirane:
Anyone else having issues of cwm not being able to open or mount cache/recovery?(prevents nandroids, causes other issues, etc)

Most likely error on my part, jw if anyone has ideas.
[Fascinate Android Development] 00ffej:
Is it just me, our has anybody else noticed a decrease in wifi signal for all cm releases?
[Fascinate Android Development] adude247:
I'm having the same problem my nanoid backups are pretty much useless...
[Fascinate Android Development] Shakes The AssClown:
Possibly a glitch... Took my phone off the charger this morning at 6am and it's 9pm now but it is saying my uptime under status is 29 hours.
[Fascinate Android Development] Kaik541:
uptime is how long your phone has been on, not how long it's been off the charger.
[Fascinate Android Development] Shakes The AssClown:
OK.. Thanks for the clarification. :-)
[Fascinate Android Development] speedingcheetah:
may break things if you do, since Glitch hasn't updated his kernel yet..
[Fascinate Android Development] jami2976:
just flashed the new 2.3.5 and I have to say its running really smooth...sensors seem to be responding well in call audio is much louder than before and maybe im just lucky but my Wifi works like it normally does..just tried sending a pic and nogo lol but all is good not something that worries me too much and like everyone else my signal doesnt show up but phone calls still call out and come in like normal :D thank you again JT for all your hard work as well as all the other devs that are working together to make our fascinate rock hard!! keep it up guys our fascinates would suck without you :p
[Fascinate Android Development] solido888:
Can the current stock CM7 kernel be undervolted or overclocked?
[Fascinate Android Development] jami2976:
just got my first taste of the phantom ring lol now i know what everyone has been talking about just an annoying lil ringer lol but its cool i still love this rom just thought it was funny and would share and no it does not support voltage controls
[Fascinate Android Development] ivorycruncher:
Does the latest nightly support dock audio? Haven't seen any official word on whether that's been merged into any builds since jt's kernel patch on 7/18.

EDIT: Just read here that apparently it is not.
[Fascinate Android Development] jt1134:
Since it requires an external app those changes wont get merged unfortunately. Feel free to use the kernel from the old thread until I have time to whip up some new kernels ;)
[Fascinate Android Development] Toddw:
Success, finally.
[Fascinate Android Development] neyenlives:
Congrats guys. The fascinate is a beast on CM7.
[Fascinate Android Development] AuroEdge:
Congrats jt on getting our phones up on CM7.

Will kernels with BLN etc. be added to ROM Manager extras? And according to the original post we do not need to wipe data, only cache, when updating CM7 nightlies?
[Fascinate Android Development] StDevious:
EDIT: Ya, pretty sure only cache wipes are needed between going different ROMs due to frameworks and all
[Fascinate Android Development] dustinb17:
When going from one nightly version to another a full wipe isn't usually necessary. Just wipe cache and Dalvik Cache and flash the latest Nightly.

There are exceptions to this if there are major changes, but typically a simple cache wipe works.