yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] mirrinigma:
as I've gone through this for like 5 pages with people in the past in this thread I'm going to keepthis short.

Backup to SD is not automatic and depends on the health of your SD card.

Don't criticize someone else's preference because your needs and preferences don't line up with them.

It's not completely unnecessary, and you're clearly ignorant regarding the needs of others if you insist it is.

That said, it's not coming to CM7. That leaves me with the clunky time consuming options that require EFFORT that you and at least a dozen others have suggested.

Anyone had any luck eliminating the intermittent wifi breaks with different radios? I tried a few times 5 builds back but nothing worked, thought there might possibly be something new going on.
[Fascinate Android Development] Toddw:
Update to 7/24 release.
[Fascinate Android Development] Toddw:
www.mediafire.com/?h4329ujidt2yxyp#1

And a new kernel to boot.
[Fascinate Android Development] dhouston10:
any new perks about this kernel?
[Fascinate Android Development] speedingcheetah:
Change-log?...guess it will be a bit till OP is updated...and I didn't know there was a pbj kernel for cm7...any one try the updated rom and kernel...or just the rom...notice anything different???
[Fascinate Android Development] Toddw:
I just flashed it. It is not OC–able but it is supposed to get rid of volume problems though I'm not having any. It seems OK so far.
[Fascinate Android Development] scarmon25:
Is it undervolted at all or do you know.

Tap-a-Talked from my Mesmerize

Running CM7 @1.2ghz w/ Tk-Glitch ML Kernel.

Much love to all the Dev's working to advance the Mesmerize and Fascinate. :) You guys Rock! :)
[Fascinate Android Development] speedingcheetah:
Try to enable/disable the settings in Voodoo control that previously affected this problem to see if it has an effect..If the volume problem is actually fixed, you should be able to have all the options checked and still get proper sound and microphone response....

Assuming, that if I wanted to update from my current CM7 setup, i would have to wipe data right?
[Fascinate Android Development] scarmon25:
If your flashing just the kernel you shouldnt have to wipe data. If your flashing the full ROM. I personaly do it just to be safe

Tap-a-Talked from my Mesmerize

Running CM7 @1.2ghz w/ Tk-Glitch ML Kernel.

Much love to all the Dev's working to advance the Mesmerize and Fascinate. :) You guys Rock! :)
[Fascinate Android Development] BSayre18:
Thats what I thought, but the market never gets installed? I also tired just getting the market apk and intalling it. It installs, but when I try to open it the screen flashes white and won't open. Thanks for the help by the way
[Fascinate Android Development] Toddw:
Doing that now and will report back.
[Fascinate Android Development] speedingcheetah:
Also, the volume should not be so low that is muted when the volume bar reaches the half way point...
[Fascinate Android Development] Pfredd:
OK - Please don't shoot me if this issue is already listed in the almost 300 pages of this thread, but the thread search function didn't find it (for me)...

I just did a fresh install (clear data, cache & devlik) and 3G does not work.

The 3G symbol in the status bar flashes, but I can not get a data connection.

Any suggestions?
[Fascinate Android Development] dhouston10:
well dern. i wasn't really having audio issues, but after flashing pbj i started to.
[Fascinate Android Development] jami2976:
Does anyone know if imnuts rom can be flashed right over jts?
[Fascinate Android Development] Headcase8911:
Where are you guys getting this rom?
[Fascinate Android Development] Toddw:
His tweets. OP has not been updated yet.
[Fascinate Android Development] Toddw:
None for me so far.
[Fascinate Android Development] mod143:
When I flashed pbj my speakerphone stopped working
[Fascinate Android Development] doctorj1:
hmmm i was just about to flash imnuts 7/25 but i guess i'll wait to see if more people are having audio issues
[Fascinate Android Development] jami2976:
Been running the imnuts/jt rom and kernel and everything seems to be running smooth not one force close haven't talked much so I will need to test that out but all seems well, side note mms/wifi still don't work together but realistically that hardly matters
[Fascinate Android Development] Headcase8911:
As for the volume issue?
[Fascinate Android Development] xceebeex:
For some reason I cannot boot in to recovery all of a sudden. It gets stuck at the Galaxy S/cyanogen mod logo screen. The softkeys light up if I touch them so it is not 100% stuck, but it just sits there.

I just tried to push the odin fix and that didn't seem to work either. Any thoughts?
[Fascinate Android Development] Mystique:
"What?"

Sent from my CM7 with EC09; Thanks to jt1134.
[Fascinate Android Development] jami2976:
The volume seems about the same..but the orientation sensor seems much snappier when I was in youtube it transitioned very quickly and smoothly...haven't talked much cause I'm working, just tested the in call volume on my voicemail a few times
[Fascinate Android Development] neyenlives:
xceebeex, get your files in order, you need to start completely back over from scratch with an Odin repartition and stock Rom flash. It usually happens when someone on CM7 does a battery pull while its on. Happened to a bunch of us. Its part of the game.
[Fascinate Android Development] wideopn11:
Just for fun, did you try using adb to boot recovery.
[Fascinate Android Development] rigglemania:
wiped data, flashed 7/25 and imnuts kernel and volume does not seem improved, in-call button press tone sounds like it's underwater and speakerphone doesn't work at all.

Oh well, back to 7/17 + Glitch.
[Fascinate Android Development] xceebeex:
Thanks, that was my next step. I actually just got my Charge in (and activated) as a replacement for my Fascinate anyway so I will just odin back to stock at this point anyway.
[Fascinate Android Development] neyenlives:
I have yet to get it working fully. I have followed every guide from the one in the wikis to the ones "for dummies" here in the forums. It recognizes the device as connected (shows as a long string of numbers in devices) but I can see the entire file tree but every time I try to open one it says it can't open it. Try to adb reboot recovery and it just revolts, never into recovery, can't get logcat to communicate at all, and no commands work in terminal. I gave up on it honestly. In the time it would take me to figure it all out I can already be Odin'd back clean so no biggie.
[Fascinate Android Development] xceebeex:
Crap, I wasn't thinking and I forgot to Odin my phone back to stock and update to ED04 before activating my new Charge. So I logged in to Verizon to try and activate the Fascinate again to update it but it is not letting me. It says that it can't be completed at this time, yet it would allow me to swap for my wife's phone (which I can't since hers is a dumb phone).

Is it just because I just activated the Charge like a half hour ago? Right now the Fascinate is at DL09, I would really like to get it back to ED04 before sending it back in. If I were to do a "Factory Reset" on the Fascinate would that just wipe data or would that literally bring me back to DI01? If it would bring me back to DI01 then I guess worst case I could go all the way back to that.
[Fascinate Android Development] wideopn11:
I read most of the guides, I think this one is pretty clear, http://xdaforums.com/showthread.php?t=1152148&highlight=adb+guide

Take it look, if you haven't seen this one it may help fill in the gaps to get you up and running.
[Fascinate Android Development] APeaceofStrange:
Did you try activating the fascinate using *228? I have used that to switch back between phones often before
[Fascinate Android Development] sorb3t:
Have you tried it with a tablet? Doesn't work for me.
[Fascinate Android Development] xceebeex:
My only concern is that you can't use *228 on the Charge, so I don't want to get "stuck" on the Fascinate. I guess I could try that and worst case I could call Verizon and have them "fix" it if I can't get back to the Charge.
[Fascinate Android Development] dividebyzero:
Installed the 7/24 update over clean stock 7/18 and 7/4 and was stuck in a boot loop each time. Never had that with any other ROM before. Weird. Going back to 7/18 and waiting for official release.... maybe longer.
[Fascinate Android Development] Maisum:
Is there a newer GAPPS out? Because the current one doesn't show that we can video chat, even though we can't, it should atleast have the video symbol for the ones who can, right?
[Fascinate Android Development] gkirby11:
I installed over 7/18 perfectly fine. No loops.
[Fascinate Android Development] harpdoc:
Same here.
[Fascinate Android Development] miah009:
sorry if this got answered somewhere after I stopped reading, but after going through 125+ pages and not finding it, I gave up.

I went from UKB 2.1 to build 11 with zero hiccups, and problem free, with the exception of my MMS aren't working. I made sure to try wi-fi off, wi-fi on, 3g off, 3g on, cycling airplane mode, power cycling the phone. re-flashing rom, fixing permissions, wiping davlik 3x, then again 3x later to see if something got lost. Still nothing. It sits on the "sending" side of things for about 15minutes before coming back failed, and when receiving them, i get the "download" box, and upon pressing it, it just hangs there. Not getting to spend as much daylight hours with my kid as I'd like, really sucks, and MMS are a big deal to me. Any ideas?
[Fascinate Android Development] Tkun:
Does anyone have a working link for the 7/04 rom?
[Fascinate Android Development] kkennedy22:
For those with wifi tether issues I've seen a few solutions in here in the last 300 pages or so but nothing clean, simple, and straightforward for tethering my stock retail unrooted galaxy tab 10.1, which ignores ad hoc networks created by the likes of barnacle or the built in tethering options in cm7. So after lots of research and lots more trial and error i found a setup that works for me 100%, so i thought i'd share. First, for background, I'm running the 07/17 rom, the .13 OTB kernal, EC09 radio, and wireless tether for root users 3.1 beta1 which can be found at the top of the google results if you search 'wifi tether'.

The key for me was finding the correct settings in the wifi tether app so here they are: Change Device-Profile: Google NexusOne (not fascinate, galaxy s or anything else) Change Setup-Method: Netd (master) (the only way the tab will 'see' the hotspot) Enable wifi-Encryption/Passphrase: optional (I've had zero issues either way) Change Channel: Channel 01 (2412 MHz) seriously

I know, I know, the wifi channel shouldn't have anything to do with it but I was constantly having my tab drop the connection (on the default Channel 06) followed by being unable to see the hotspot altogether. I found the issue referenced in the FAQ on the wifi tether homepage which directed me to an androidpolice post with several suggestions. I tried the Channel 01 suggestion and have not dropped a connection in over a week, in fact I'm tethered right now. And before you suggest wifi interference as the problem, I had the same issue regardless of location, home, work, driving down the interstate, etc. The post had a few other suggestions as well if you're using tasker to turn wifi on/off based on some factor or another.

All other settings in the app I left default. I did mess with access control without any ill effects but I leave it off and just use wpa/wpa2-psk encryption.

All in all it works great, I just dock the widget next to the power control widget, and you hardly notice that they're two separate widgets. Hopefully that helps some people having issues, but if not let me know what you're seeing as I may have run into it in my long period of trial and error.
[Fascinate Android Development] caly2259:
Read directions carefully don't flash using 3 button install 7/4 then while in cm7 hit power button go to reboot select reboot recovery this will take you to cwm4 flash from there it works a little different than cwm3 so play with it a bit
[Fascinate Android Development] Toddw:
I've still got a copy of the download on my phone if you can't find it anywhere else. I guess I can upload it, or try to.
[Fascinate Android Development] shorto85:
Thanks kkennedy22! Worked perfect for me.
[Fascinate Android Development] rigglemania:
Seconded and thanked.
[Fascinate Android Development] MJMcMahon:
Regardless of what device brand I select, I'm unable to download XTRA data. Was that your experience as well?
[Fascinate Android Development] vlucchetti:
Same with me, but I found I locked on quicker/better choosing Galaxy S versus other.
[Fascinate Android Development] 1993cb7:
Works like a charm! Now only if i had a tablet to tether LOL!!!!
[Fascinate Android Development] usetheschwartz:
kkennedy, works find with 3.1 beta 2 also. Dialed!
[Fascinate Android Development] sstevenson72:
0717 Build and USB Drivers

Noticed I have flashed the 0717 build and now none of my computers will install drivers for it. It shows up in device manager as fascinate and the USB drivers by samsung do not update this device so I no longer have ability to adb with the device... Anyone else have this issue and how did you resolve this?
[Fascinate Android Development] gotsflat4love:
You need to download the Nexus drivers. Search this thread and you will find the link. Check back a few pages.
[Fascinate Android Development] Grimis:
Are we using Rom Manager now?
[Fascinate Android Development] JOrtenzi:
7/25 build and kernel

did not see this in the OP

as per imnuts twitter account:

7/25 build - http://twitter.com/#!/imnuts07/status/95572172336144384

(in-call audio fix and mms fix)

7/25 OPBJ kernel - http://twitter.com/#!/imnuts07/status/95584230209355776

(kernel to go with 7/25 build, should fix audio problems)
[Fascinate Android Development] djk21108:
Nice post.

Hopefully JT/Glitch can integrate these fixes into their mainstream ROM/Kernel respectively.
[Fascinate Android Development] mxpxrobbie:
Does anybody have a link to the kernel that came with CM7? I'm on Glitch right now, and it's great, but I'm really having some battery issues, and I'd like to benchmark with the 'stock' kernel to see if it's worth keeping Glitch around.
[Fascinate Android Development] mising:
The dockaudioandcompassfix.zip in the first post is just the kernel.

http://xdaforums.com/attachment.php?attachmentid=658807&d=1311030769
[Fascinate Android Development] JOrtenzi:
as far as I know, it only comes with the rom, so you would have to reflash cm7 (thats what I did)
[Fascinate Android Development] JOrtenzi:
i thought that was a patch for the kernel in the rom.... but, i may be wrong
[Fascinate Android Development] mising:
That is what I use to bounce back and forth between stock kernel and Glitch.
[Fascinate Android Development] JOrtenzi:
Gotcha... did not know that
[Fascinate Android Development] mxpxrobbie:
I just finished downloading these... are they safe to flash, or should I wait until they're added to the OP?
[Fascinate Android Development] JOrtenzi:
i flashed them.... haven't tested the voice volume yet, but the flashes were successful

will report back with what I find out

Also, from the way it sounded.... I dont think this OP is going to be updated any more. Any further updates will be through the nightlies, but we do not know when they are going to start rolling those out.
[Fascinate Android Development] juremy:
The audio in my earpiece is much better with imnuts kernel..but people keep saying I sound broken up and can't understand me well..so I hope glitch finds his own audio fix
[Fascinate Android Development] bqq100:
Is that with both the imnuts kernel and imnuts system build?
[Fascinate Android Development] juremy:
Yeah...the 7/25 build from his twitter...its was the same way on my phone with his other kernels as well
[Fascinate Android Development] m0r0n3s:
I just tried imnuts ROM + kernel and the audio volume is much better. I called myself using google and it sounds ok, but once I enable the speaker it goes completely mute and you can't get it to work anymore. I had to hang up and call again.

So, better volume but no speaker functionality :(
[Fascinate Android Development] suppliesidejesus:
The builds that imnuts has posted have included stuff that jt put on his git for his own testing. Jt reverted all of the changes because they broke ****. Keep that in mind, please.
[Fascinate Android Development] ssewk2x:
In call audio is without doubt the biggest headache (the only one, really) that I have with this ROM. I did a lot of googling and poking around today and found a few things out. I'll post some here.

First, it looks like a lot of people on a lot of devices are having low in-call volume issues with GB roms in general. That's .. interesting.

Second, it looks like there's a way to tweak it through the "secret menus" that you have to get through by dialing in some strange super-secret stuff on the dialer. Unfortunately, I was not able to access these on my CM7 phone. A possibility is to maybe flash back to UKB 2.x and use the TSM parts app they had that lets you into those, make the change there, and hope it sticks when you flash back to CM7. I might try that route at some point if another fix doesn't come along first. Someone with more time on their hands than me is welcome to take that idea and run with it in the meantime. Also, if anyone knows of a way to access those menus from CM7, that would be awesome.

Third, I took a look at JT's github and, with the help of some of the guys from the glitch beta dev team, noticed that one of the things he changed for fixing audio this time around was a build.prop edit that gave 15 steps (instead of 5) for in call volume. I edited my build.prop file to match, and while I did see the 15 steps, my volume was no louder when cranked up to 15. Bummer, man :(

Fourth, I just flashed JT's new kernel that was linked above. It behaved the same as with my build.prop edit. Nice 15 steps, no real improvement in volume. I think what needs to be changed is how loud the max actually gets. The one thing I didn't do was actually flash the ROM itself - I'd rather wait till it gets ported into a CM7 update before trying that. I guess it's entirely possible that ROM+kernel changes would work for me, but I remain pessimistic at this point.

Finally, I noticed something very odd. When playing a voice mail in the gvoice app, the ear-piece volume is actually very loud, and appears to be governed by the same in-call volume setting .. so what the hell is up with that, I wonder? Why is it sooooo loud in gvoice (it's perfect in gvoice, imo), but not in actual calls?

I guess my next step will be to try the secret menu stuff, or to just be patient until the devs make official releases / update OPs / whatever and hope it gets fixed then.

TL/DR:

In call audio still borken, a bunch of ideas on where to go from here to get it working.

You devs are awesome and your work is equally awesome. I mean no disrespect, I just want to help and wish I had the time to help more.
[Fascinate Android Development] not balanced:
I flashed both of these with no problem. Had to return to jt's kernel due to no speakerphone with the 7/25 OPBJ kernel.

Yes this is the jt's original kernel with the dockaudio & compass fix included.
[Fascinate Android Development] wowser21:
I also tried the updated imnuts kernel. Speakerphone was broken for me as well and so was bluetooth audio. I could not hear anything when trying to make calls using the bluetooth kit in my car.
[Fascinate Android Development] speedingcheetah:
Still on the 7/17 CM7 rom and Glitch 11.1 ML kernel...just noticed that also in Google Voice, the messages play back at max volume setting as loud as they should be...nearly 2x as loud as in-call volume at the max setting...although, the volume adjustment in Google Voice still acts like in-call, get to half and sound is muted...definitely something messed up in they way it adjusts the volume values internally..

I have no idea how volume is adjusted internally in the OS, but I guess it isn't as easy as adjusting some values in a config file somewhere to fix it..

I have noticed as far as in-call volume goes, setting to max, then all the way down, then to max again helps just a little bit..

The microphone sensitivity/volume bothers me much more...no where near as sensitive as it was on TW. Helps to disable Hi-fi record and DAC direct, but only slightly, people keep saying they can barely hear me...

Bluetooth headset volume seem ok...on TW, it was always too loud even on min setting. The microphone does seem to come through a bit low..no as bad as built in mic...
[Fascinate Android Development] usetheschwartz:
Try the 7/25 build from imnuts and JT's new kernel - WiFi MMS and in-call volume issues are both fixed with this combination. Wipe 3 before installing and just to be safe, run the kernel cleanup script.

All seems well, but I've only got about 4 hours on this combination, will update after a few days.
[Fascinate Android Development] Headcase8911:
I couldn't get jt's kernal to install in the blue recovery. Am I missing something?
[Fascinate Android Development] usetheschwartz:
I installed the 7/25 build, new PBJ kernel and ran that for a while (one of those two installed a yellow recovery) and from the yellow recovery, I was able to install JT's kernel.
[Fascinate Android Development] wowser21:
I can't seem to get back into yellow recovery. I was getting in there no problems after installing CM7 and hitting "Recovery" from the power menu, but now it takes me to the blue recovery. The last thing i installed in yellow CWM was Glitch's kernel. How can i get back into Yellow recovery?

Thanks.
[Fascinate Android Development] usetheschwartz:
Glitch's kernel installs blue recovery. You're going to have to install the ROM or kernel that gets you to yellow. I didn't break out whether it was the 7/25 build or was the PBJ kernel that installed yellow, so you'll have to try them and see what works.

For the record, while JT's kernels don't have the whiz bang cool shiny stuff, they're always rock solid and just work. I've found that too often, people are getting caught up in overclock this, undervolt that and while that's fun and all, I like my phone to just work. JT's (and now imnut's continuation of JT's) work on the Fascinate clearly leads in that department.
[Fascinate Android Development] neyenlives:
Flash the 07/25 rom first, that will install orange/yellow recovery. You will then be able to install the kernel.
[Fascinate Android Development] speedingcheetah:
What new kernel by JT?...the kernel and rom poted a few back was imnuts PBJ...Is that the one you flashed...

I see some say that the 7/25 build and PBJ kernel fixes the volume issue break causes the speaker phone not to work? So, what about just the rom itself with stock kernel?
[Fascinate Android Development] Kbesaw:
yes what is the new kernel by JT? how do we get this? is it the one that's just bundled in the 7/25 build by imnuts?
[Fascinate Android Development] Headcase8911:
Check out andmer's twitter. Need to flash in orange recovery. Three finger should get you there.

https://mobile.twitter.com/#!/andmer_/status/95892619141464064
[Fascinate Android Development] Headcase8911:
Double post
[Fascinate Android Development] AuroEdge:
Doesn't jt's new kernel break speakerphone capabilities?
[Fascinate Android Development] mod143:
Ive flashed all the new stuff and it all seems to break speakerphone and not fix in call volume. Other ppl seem to have success tho.. Just my experience
[Fascinate Android Development] PhoenixPath:
Odd. Though I am on miui, I flashed jt's kernel through rom manager without a hitch.

Even verified that it changed in cpu spy (though the lack of the glitch splash was a darn good giveaway...)

Told rom manager to use fascinatemtd and cwm 3.x compatible. Maybe it affects it even though I have a blue recovery? (4.something)

EDIT: ...why does SwiftKey X hate me??
[Fascinate Android Development] Toddw:
http://imnuts.net/quXv55

New twitter post. What to make of it? Is it the same update from yesterday?