yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] StDevious:
dang, just realized I meant to write what you wrote, and accidentaly wrote data. :o
[Fascinate Android Development] harpdoc:
As jt said, the old kernel works fine with the new build and dock sound works, although the phone seems a bit slower with the old kernel. Looking forward to your new cooking jt.
[Fascinate Android Development] kuronosan:
I'm interested in the new OTB and Glitch kernels too... can't wait to see what kind of surprises jt rolls out.

If I'm currently running Glitch, can I just install a nightly over it?
[Fascinate Android Development] danielkx:
Supposedly running glitch with the new nightly will not function properly. Not sure exactly what is broken though.

I am running build 7/17 with glitch. I am hoping that the next nightly will fix the issues with MMS.
[Fascinate Android Development] speedingcheetah:
Just flashed the nightly 3 build...uses much more memory...no signal bars...market crashes often...volume seems a bit better...need to test some more..still need to turn volume all up, then all down, then all up again to get full in-call volume...also, phantom ring tone in background when phone actually rings sometimes..data connect sometimes drops, have to toggle data off/on to re-connect stick to 1x after sending/receiving texts...I miss voodoo color and all of the fancy stuff from the glitch kernel..
[Fascinate Android Development] seraphls:
Flashed Build 3, and ran into a few issues:

-When loading up CWM in the ROM manager, I was offered only v2 and v3 as options to select for which I had, though the link given before was for v4. Don't know if this is an issue

-When flashing gapps, it took several tries and data-wipes to get everything showing up - the market was stubborn

-Signing into my google account over wifi did not work - it said I needed a stable internet connection

-Attempting to activate the phone via *228 (i had been using another phone) failed after entering my password, and after that I showed no signal.
[Fascinate Android Development] baron4406:
I too cannot access the Market over wifi, Also it seems to have flipped out my sms. Getting messages is spotty , sometimes there is no notification of a message.

Screen hasn't popped on randomly yet tho like it did all day on CM7 build 7/17
[Fascinate Android Development] FDro:
Call volume and speakerphone volume are way better now.
[Fascinate Android Development] baron4406:
FDro is right call volume and speakerphone are better, still not as good as stock but its an improvement.
[Fascinate Android Development] tkirane:
At least I'm not the only one. Ideas?
[Fascinate Android Development] blkhockeypro19:
Random soft-reboot

Has anyone been having random soft-reboots, where the phone is up and running fine but suddenly it starts [infinitely] looping on the CM7 blue skateboarding android boot screen? Only way to fix it is pulling the battery. If anyone knows of a fix I could use it... I nearly overslept today because my alarm didn't go off because of the loop =p
[Fascinate Android Development] Charm8er:
I'm on stock.
[Fascinate Android Development] ecsnead69:
All those changes and data connections still drop out!?!? They need to make a script that automatically toggles airplane mode everytime you lose data connection.......
[Fascinate Android Development] smilepak:
Not sure if this is NORMAL...

everytime i reboot into recovery and try to go wipe DALVIK CACHE...by going to the menu to wipe it, i see message

E: unknown volume for path [/sd-ext]

wonder if that mean anything
[Fascinate Android Development] Syndacate:
That was the same thing I was thinking, lol.

I saw that list, first thing I did:

*scan to see if data connection fix is on here*

That being said, JT and the rest of the guys who work on CM7 do an amazing job, hats off to you guys.
[Fascinate Android Development] Syndacate:
I get that error message too.
[Fascinate Android Development] smilepak:
For every ROM build, I've always reflash JT's Vanilla GB V3 (MTD) Kernel from Rom Manager....

That's the only way to get the Sound Dock Redirect to work..hahaha I wonder by doing that, i basically undo'ing all ofr those changes...
[Fascinate Android Development] Syndacate:
Yeah, I haven't tried it yet, but I'm most likely going to give JT's Vanilla GB a try today after work.
[Fascinate Android Development] TheChillburger:
Toggling airplane mode won't even get my data connect back anymore :(
[Fascinate Android Development] chopper the dog:
Sounds like you both need esn swaps. Flash ec09 modem (if not on it already) and do swap with another vzw smart phone. If you don't have the means of doing that, then continuing to post about your crappy data connections isn't gonna help cause it's not rom related. The esn swap is a proven fix for your issues. Or call support and beg to have it done by them.

good day.
[Fascinate Android Development] Syndacate:
- Thought CM7 used the EC09 modem?

- Why would I need an ESN swap?

- Go screw yourself?

Seeing as the issue ONLY HAPPENS WITH THIS ROM, that makes it ROM related, especially if more than one person is having it. It has nothing to do with an ESN being bad, or me having a crappy this, or a crappy that, or calling VZW tech support..."Continuously posting.." - 1 post. One. Not even? I simply said I searched the list of fixes for the fix to an issue I was having...

My data worked perfectly well on UKB without cut-outs...I just re-installed the latest CM7 build last night, I haven't had any data connection issues yet - maybe the issue I was having has been fixed, don't know, been installed < 24 hours.

Please don't be a jackass just for the sake of being one..
[Fascinate Android Development] chopper the dog:
Considering there were no personal attacks directed at anyone. But you being the better man chose to go that route.

http://rootzwiki.com/showthread.php?t=2638

http://xdaforums.com/showthread.php?t=1051543

And the data drop out spans across many roms after multiple flashes of modems and sometimes just one modem flash may require this to be done after flash. And I had the same issue on vgb but I'm fortunate enough to have an old vzw smart phone and have shared my esn with others many times for the "FIX" as well. And it was even needed if you used the ED05 odin package.

*quote from ed05 odin thread*

*** Warning, some people have reported loosing 1x/3G data svc after flashing with SamsungPST. Flashing with ODIN until is OK.

If you loose data you have two options right now..

1. Login to My Verizon and swap your phone number to some other phone, activate it (*228) and then swap it back to your Fascinate.

2. Call Verizon and tell them you are not getting any data (but voice works ok) and that you would like your keys reset.

Keep up the good communication skills.

good day.
[Fascinate Android Development] Syndacate:
I misspoke. I didn't mean it "only happens on this one ROM" - I meant that it's an issue dedicated to this 'family' of ROMs, as on others (ie. OEM, UKB) it doesn't happen, meaning it's NOT my phone's fault. The point was simply that it wasn't my phone, it was ROM related.

As for your quote from the ED05 thread. That's useless and doesn't apply to me. Not even quite sure why you posted it:

- Hello, Verizon?

- Yes?

- About 20 minutes ago, I didn't get data for about 15 seconds, fix?

- Can you log on the internet right now?

- Yeah.

- Everything looks like it's working fine, then.

- Yeah.

- Ok, bye.

OR

I can waste my time doing an ESN swap, and then the result will be exactly the same because it has nothing to do with the phone...my phone is sending and receiving data just fine. It is (or possibly was) a ROM issue.

That might be prevalent if my phone didn't get a network connection at all, but that is not the case. There is simply an issue with this ROM, or this family of ROMs in which it'll say there's no 3G, when there actually is. Airport on/Airport off, problem goes away. I highly doubt it "happens with all ROMs" - but I just happened to see it 10x a day with CM7 v14 and didn't see at all for a couple of months under UKB 2.1. As I said, it is possible, as of 24 or whatever I installed last night, the issue is resolved, I'll have to see.
[Fascinate Android Development] suppliesidejesus:
Uh...It does happen on UKB, chopper posted stuff from the UKB thread about this exact issue.
[Fascinate Android Development] times_infinity:
Hi, yes. You say that the ESN swap won't work. But you've never stated that you have tried it and it hasn't worked. Don't push aside advice that can be attempted and doesn't take long at all. 5 - 10 mins at most. Data loss has happened to many many people with this phone, and those many many people have tried ESN swapping and reported that it has solved their data woes, unless VZW was having network issues that day. It ISN'T rom related. it has to do with your DMU keys becoming invalid and not being able to verify itself with the network. So either try the ESN swap, or stop complaining that you're losing data because you won't attempt a solution. Worst thing that can happen is that you still won't have data. It's not like it will blow up your phone, because it won't.
[Fascinate Android Development] chopper the dog:
@Syndacate, I forgot about this success story. http://xdaforums.com/showthread.php?t=1227413

good day.
[Fascinate Android Development] Syndacate:
So what you guys are saying is that my "DMU Keys" are becoming invalid only on CM7-14 until I airplane mode it, with the issue regressing once an hour or so, and though I haven't seen that in 1+ months on UKB nor in the ~1 day with CM7-24, but it was NOT a ROM issue.

I get what you guys are saying..but I just don't see it... If I'm having a problem with 1 OS (not even 1 OS, 1 build of 1 OS) *constantly* - and the problem is NOT persisting for me with ANY other build of ANY other OS (on my phone, anyway), guess which component I'll blame.

If the problem persists I will be sure to try one of the above solutions. Though I had the issue about once an hour (easy), and since I switched off of CM7-14 (Thursday?) I've seen it 0 times.

EDIT:

Also, seems to be lots of talk between the wifi to 3g or vice versa hand-off. I rarely used wifi and this was most definitely happening outside of that situation.

EDIT2:

Sorry I came off douchey. Your non-directed response felt very directed.
[Fascinate Android Development] exzacklyright:
gps takes 20min to lock on :[ , phone randomly died today and had to fix permissions, call volume still **** :[
[Fascinate Android Development] Syndacate:
Hrm, I haven't had any of the above in CM7-24, what build you running?

Also, I think the call volume was fixed..I was on the phone today and didn't notice it...not sure if I grew attuned to it, or if it was fixed - I think I heard the latter somewhere. GPS also locks damn near instantly for me. Which nightly you using? Stock kernel? UV? OC?
[Fascinate Android Development] tkdboi:
I flashed the cwm recovery from OP then flashed CM7 then flashed Gapps from OP (6/13/11). Gapps won't install. After flashing CM7, in cwm recovery it tells me I can't mount datadata and system. Is that why I can't install gapps? I really would like CM7 on my fascinate... please help!!! Thanks in advancr~
[Fascinate Android Development] :
I had a similar issue where I could flash CM7 via ClockworkMod but couldn't flash gapps with CWM. I managed a work around through ROM Manager and it worked great. I'm not certain if this will help but perhaps it could be a method to try.
[Fascinate Android Development] sageDieu:
Try going to the advanced section of CWM and mounting system and datadata... you should be able to go to Download Rom in ROM manager and hit gapps, then the latest one and install it from there.
[Fascinate Android Development] tkdboi:
I've tried that method and as well as the rom manager method. I even tried unzipping the gapps and manually moving them to /system/apps folder via root explorer. Am I out of options??
[Fascinate Android Development] spollock:
I had a similar issue with #27, where gapps would not load as well as no WiFi for some reason. I flashed #26 and WiFi worked fine, rebooted into recovery from ROM Mgr and flashed the gapps zip. All seems fine now... staying on #26 for a while.

HTH
[Fascinate Android Development] Syndacate:
Make a backup, and reinstall - it's worth a shot.

I haven't used rom manager (ever...like, ever, don't even know what anything but the icon looks like). I installed gapps 2.3.5 via the zipped installer package via CM7's recovery.

So:

1. Backup using t-backup or something (I don't backup my phone, but that seems to be what everybody else does)

2. Use atlas 2.2(.1) pit and the I500 OFFICIAL release - throw them into odin (or heimdall if you're unix based), and flash those guys

3. Once the regular (OEM) OS boots up, reboot to make sure it's good.

4. Flash CWM4 w/ CM7 fix, hold 3 finger recovery, don't let boot.

5. Clear whatever caches and voltage settings mount, cache, dalvik, etc. They might not all mount.

(5a optional - I'm recommending): Run the kernel cleaner script, that wipes out all your caches + some.

6. Install CM7 from sd card's zipped installer via CWM.

7. Reboot the OS AFTER it 1st time boots.

8. Reboot into recovery

9. Install gapps off sd via the zip installer package via CWM.

See what happens then...I know it's pretty drastic to start from the beginning like that, but if you have the time and the backup, give it a whirl, it'll probably work fine. Hope that helps ya some.
[Fascinate Android Development] Coolsaber57:
It doesn't mean anything. That's for Swap IIRC, and unless you've created a swap space on your SD card, it won't find it. Hence, no volume.
[Fascinate Android Development] mxpxrobbie:
So, are we still having problems with SD cards dying?
[Fascinate Android Development] Syndacate:
There's actually a few different 'clears' that it can't do. Dalvik and cache are the only ones it does, IIRC. I think it fails on battery and voltage.

I can't remember all the details, just remember seeing that error message before.

From what I heard it was fixed 3 weeks ago and I was a complete idiot for not knowing about it o.O.

IIRC somebody said that somebody committed a patch for GSM SGS phones which caused the issue. Still not quite sure where they would have committed it that it made it to every single ROM, but yea, that's what I heard.
[Fascinate Android Development] sageDieu:
Something to do with how JT gets his code for Cyanogen which is all committed from the general galaxy S code, then he modifies/ports whatever for us. I assume that's what happened, and it was just a little bit of code he missed.
[Fascinate Android Development] tkdboi:
Thanks to all replies. I will try above methods and see if it works. :)
[Fascinate Android Development] Syndacate:
I don't think he missed it as much as much as he didn't realize that that GSM oriented CM7 patch was ****ing SD cards..that's what I think, anyway.
[Fascinate Android Development] Azuma73:
I'm thinkin' about being bold and flashing build #29?

Oh yeah, in call volume issue FIXED with Glitch V12 audio kernel!!

No joke man, i'm for real!!:eek:

Glitch is now near perfect!

http://db.tt/FwCMeg6 high leakage

http://db.tt/FwCMeg6 med leakage

http://db.tt/NHsZcGR low leakage

Check 'em out and let me know what you think!?!?!

I'm jazzed!!
[Fascinate Android Development] Syndacate:
Not much to be bold about. I'm running CM7-29 and haven't had a single hiccup. Even the CM nightlies are damn stable, so even if you run a good nightly (ie. 29) as a stable version, you should be fine.

As for the volume issue, I don't know much (anything) about the glitch kernel, so I'm not sure if it shares any source with JT's, but I'm 95% sure that JT (or somebody) fixed the in-call volume issue. I experienced it on CM7-14 but I haven't seen it in CM7-26 or 29.

So uhh, you shouldn't have any problems with in-call volume regardless of your kernel. Even if the issue isn't fixed completely (I have no idea what the 'official' status is), I had to press the phone to my ear in CM7-14 to hear the person on the other end...now I just talk normal. So yeah, ROM's stable, no SD card issues from what everybody is pretty sure about, and volume issue is fixed...so it's not really a gamble, it's a pretty solid ROM at this point - load it up - doubt you'll be disappointed.
[Fascinate Android Development] cowman4000:
What kernel are you running?
[Fascinate Android Development] chopper the dog:
You would be doing a better service to people if you just linked ssewk2x's post rather than just link things without notes. And why let you know what people think? Some may get confused that you actually had something to do with it.

http://xdaforums.com/showpost.php?p=16976976&postcount=786

good day.
[Fascinate Android Development] Syndacate:
The one that came stock with CM7....JT's that came with VGB also seemed to work fine.

Also, I agree with chopper.
[Fascinate Android Development] Azuma73:
Yeah, you're right. My bad, I really diddn't want to imply that at all. I was just hyped about it that's all.

So check it out, it does fit really nice with CM7!
[Fascinate Android Development] OneAn9ryN00b:
Is anyone else's accelerometer not working, it was previously working on nightlys prior to build 26, but has since stopped working for me.
[Fascinate Android Development] xsc0rchx:
Can someone tell me where I can get this Froyo bootloader? I really want to stay with the Glitch kernel.
[Fascinate Android Development] Syndacate:
What's so great about it compared to the kernel that comes with CM7?
[Fascinate Android Development] FordDenny:
Can we find what each Nightlie does? I install these daily but really don't know what each does.
[Fascinate Android Development] smilepak:
http://cm-nightlies.appspot.com/?device=fascinatemtd
[Fascinate Android Development] sageDieu:
It has a lot of great tweaks. The screen is undervolted to save battery life, there a lot of little tweaks and fixes for performance and speed, it supports overclocking up to 1.7Ghz as well as undervolting, it has a newer version of voodoo, etc... It's just better in every way.

Not to put down JT's kernel; his is meant to be pure speed while glitch is made for customization and awesomeness. Both work great.
[Fascinate Android Development] Syndacate:
While I don't necessarily see the big 'awesomeness' in it being fixed recently in the Glitch kernel while the issue's been resolved for a decent amount of time in JT's kernel, I see where you're coming from.

The screen undervolting probably helps a lot..can't imagine a 1.7OC is necessary or even practical for a daily, and most realistically most end users can't tell the difference between 1 voodoo vers and the next.

I'll give the glitch kernel a try at some point, but something tells me I'm not going to notice much (if any) of a difference, but who knows.
[Fascinate Android Development] FordDenny:
Thank you!
[Fascinate Android Development] Dan Ang:
this might sound EXTREMELY stupid, but does the updates of JT's kernal just come in the nightlies? How do I tell if I'm on v3?
[Fascinate Android Development] Syndacate:
I'm in for the answer on this as well.

I just stay up to date with the nightlies, though JT may do "stable" builds at some point. As for determining what kernel on, there seems to be no indicator besides a number which I'm not sure what it means in the phone info...check out CPU Spy - else wise just flash V3, if it's successful, it's there :-P.
[Fascinate Android Development] djk21108:
Firstly Syndacate, Glitch kernel does afford you a LOT of advantages over JT's stock kernel. It has a bunch of bug fixes. As for the kernel. It is not updated in every nightly. The kernel is released seperately and then included in nightly releases after that. Basically what I'm saying is if you're on CM7's latest nightly, you have JT's latest kernel. Most likely wasn't updated for a while though.

I recommend giving Glitch's kernel a try, especially now that we have in call audio up to speed.
[Fascinate Android Development] wideopn11:
The V3 JT posted to ROM manager is voodoo 10 and is not supported by voltage control. The latest kernel in nightly's is voodoo 9 and IS supported by voltage control OC to 1300.
[Fascinate Android Development] Syndacate:
So do you think JT's kernel has no advantages over Glitch?

Also, is Glitch a team kernel, or is it a single dev?

Yeah, I don't expect the kernel to be updated nightly, it's just the auto-build. Though I guess there is some better stability standards if you do a "Release" opposed to nightlies. Though if I felt that was an issue, I wouldn't be on nightlies.

Hrm, I gotta dl ROM manager, typically I just flash all my **** in.
[Fascinate Android Development] doctorj1:
i've been having some MMS issues, on any CM7 or other MTD ROM i use, I can receive MMS and any other functions, however, i cannot send MMS

when i try to send it just shows it trying to send but it never goes through,

this is on 3G, EC09 modem, everything else works fine

anyone have any idea why just outgoing MMS wouldnt work??
[Fascinate Android Development] MrManiacNF:
I've had this same problem, and believe it or not it's not the rom. It's happened to me on stock froyo a couple times, and CM7 nightly's, differnet ones.

You should check your carrier's SMS number and make sure it's entered under msging settings. That fixed me one time, another I had install Go SMS, and I don't know if that's what done it, but that's when I noticed the problem come about.

Another problem I've had on both stock rom, and CM7 nightly was when I would dial a number in the dialer and I didn't enter my area code it would automatically enter a 617 area code. That ended up being, I used the app autostarts, under "New Outgoing Call" there was an entry for "Dialer".. and it was enabled... I disabled it and it fixed that problem.

I would check settings.
[Fascinate Android Development] sageDieu:
glitch is better than jt's in my experience. you will definitely notice. it is a single main dev (tk-glitch) but he has a couple of other guys that help.

Sent from my MIUI SCH-i500
[Fascinate Android Development] cking122:
This is probably a really stupid question, but I want to flash nightly 30 but I don't want to lose my app progress, I have 3 stars in Cut the Rope up to magic box and I want to finish it, but I don't know how to flash a new nightly and keep my apps, and all my accounts and data and such, anyone know how to help me?
[Fascinate Android Development] Mikes30000:
Damaged SD Card Once Again

So I was one of the unlucky ones originally affected by a damaged, unrecoverable SD card in one of the early nightly builds. I purchased a new 16 gig card and have been running Powerwashed ED05 froyo for a few weeks without incident.

Well I figured I would give CM7 a go once again since the SD issues were supposed to be fixed. I flashed build 30 (with much difficulty mind you as it took several bootloops and attempts to get my SD card to mount properly). I have to say that I received the DAMAGED SD CARD message about 5 or 6 times in 2 hours. Luckily, I was able to reformat the card either via the phone or in windows every time and it was still functional. Does anyone have any insight as to why my phone is still corrupting SD cards on the latest nightlies?

The last bit of information that I can give is that my current sd card was restored from a backup in windows of many items from my old sd card before it was fully damaged. Were there subtle changes to the files stored on my computer that carried over to the latest nightlies? I even tried Odining back to ED05 stock, reformatted the card and then installed CM7 with essentially nothing on the card and still got the damaged card message. This is really frustrating because CM7 is awesome but I can't afford to keep frying SD cards. Any help would be greatly appreciated!
[Fascinate Android Development] speedingcheetah:
I flashed build 29 over Powerwash....sd card fine..no sure about 30...nothing should have changed according to the change log....