yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] jt1134:
I am working with the mainline cm guys in getting everything merged. Hopefully things will ready within the next week or so :)
[Fascinate Android Development] usofrob:
Since others seem to be having this same problem, when I went to update from the 6/26 to the 7/04 release, i went into a boot loop / bootloop. These are the steps I followed that worked for me getting my phone back. Thankfully they worked as I don't have a windows machine to run Odin.

-Three finger boot to get to my original red CWR (may work with other colors too)

-Format the "big three" as they say

-flashed the 07/01 build (the 6/20 release worked as well)

-it reboots into the orange CWR to do the install

-rebooted into 07/01

-after booting, reboot into recovery

-this time it should be the orange CWR 4.0.0.5 (I think)

-flash the 07/04 build (presumably could be the 07/08 build as well)

-reboot and be happy
[Fascinate Android Development] beenz:
I love you :)
[Fascinate Android Development] FDro:
The voodoo app got updated with a V10 driver for the fascinate, just a heads up. I haven't flashed build 8 yet or I'd give more input as to the effects this might have had.
[Fascinate Android Development] bespinct:
I haven't had the problem at all with the 7/4 release. On the previous releases it happened often for me...a couple of times a day. I think I was an oddball though, I don't recall anyone saying it happened that often to them.

Steve in CT
[Fascinate Android Development] slaz13:
It says in call audio can now be adjusted. Where can we turn it up?
[Fascinate Android Development] Bardasian:
The EC09 Radio is an improvement for me as far as service and stability. Also, the Gingerbread Touchwiz Leak and ROMs (Nameless/Techno) are having SD issues. Haven't heard any related to the radio.

Posted with a Fascinate
[Fascinate Android Development] aes55:
i had the *228 option problem as well.

to fix, i created a contact named "vzw roaming" and set the number as *228,,,,,,2 (the commas insert 2sec pauses)

worked great.

EDIT: the woman's voice will tell you programming was successful, but the phone screen will report it wasnt - it was. just reboot and all is good.
[Fascinate Android Development] elarson006:
Happened once during a week of use of an early july build.. running 7/4 build since release and has not happened yet. The signal just went to no service reglardless of rebooting, airplane mode toggle, etc, so yes, it was quite obvious.
[Fascinate Android Development] Bardasian:
Are you guys using any themes? I moved back to EF just because its Gingerbread theme is very clean and was wondering if maybe I didn't look into theming CM7 enough.

Posted with a Fascinate
[Fascinate Android Development] andmer:
Nope. Move along now.
[Fascinate Android Development] nitsuj17:
you mean my gingerbread theme that was ported over for it? might as well use com rom
[Fascinate Android Development] Headcase8911:
Uh, the volume rocker during a call.
[Fascinate Android Development] akaine2001:
Any word on diag mode or dun settings codes jt? Is there a cm wide code for it? Can you check with the main line cm guys?
[Fascinate Android Development] shredder47:
ring during phone calls

so i've had this issue happen twice;

someone will call me, phone will ring like normal with the stock ringtone, then immediately a second ringtone, one like a regular telephone...a 'bring bring bring' type of tone, begins playing alongside the first, and continues to play through me answering the call and trying to talk to the other person, which can make it considerably harder to talk to whoever is calling me....

happening to anybody else? fixes?

thanks guys
[Fascinate Android Development] lane32x:
ROM Build 8 with kernel .13 evidently yields great microphone pickup for in-call audio. However it seems to have broke SoundHound and VCast Music ID. ( and I'm assuming anything else that uses the mic)

Any ideas?
[Fascinate Android Development] Grimis:
LOL, no kidding
[Fascinate Android Development] natalic:
Its built off the AOSP so i highly doubt it'll contain samsung copyrighted software:). Which is what phoneutil is.

On a side note my phones radio didn't work this morning after i woke up...so i dont think all wakelock issues have been fixed there
[Fascinate Android Development] JoeProcopio:
correct me if i'm wrong, but isn't there a second popup option under reboot to reboot in recovery or normal reboot? if so, i seem to have lost that function (7/04)...haven't flash 7/07 yet, but am going to right now with OTB .13 kernel for mic fix....

any confirmation that it indeed breaks soundhound?
[Fascinate Android Development] nunyazz:
Or you can just use the *22899 option.
[Fascinate Android Development] aes55:
anyone having problems with camcorder?

the clarity seems great, but the video itself gets all choppy...

any fix?
[Fascinate Android Development] nunyazz:
settings/ CyanogenMod settings/ Interface / Power prompt
[Fascinate Android Development] slaz13:
Seriously! Im not slow. My volume is all the way up but its still not loud
[Fascinate Android Development] jkat797:
I'm also experiencing this problem...hm....anyone else?
[Fascinate Android Development] FDro:
Just tried to record 720p, on stock kernel 7/04 cm7, and its choppy.

Not liking the aosp camera software at all.
[Fascinate Android Development] Headcase8911:
I'm pretty sure jt tweeted that he has more audio tweaking to do. I don't think too much gets by him.
[Fascinate Android Development] happynoodleboyx:
Guess I misunderstood about the ec09 rom and modem. Gonna flash it now and test it out.

I also have a buggy camcorder, it doesn't record any sound and when I watch th video, it's choppy and flickering all the time. Is there anyway to get the camera app that's on the stock rom on here?
[Fascinate Android Development] jearl75:
Has anyone lost the use of their home and search softkeys on the 7/07 build? Mine don't seem to work
[Fascinate Android Development] bleeeeeeek:
My buttons tend to go out once a day or so.. but if I put the phone to sleep and wake it back up then I'm good to go..
[Fascinate Android Development] jearl75:
It's not my buttons in general, menu and back work flawlessly, just home and search. I've put it to sleep and woken it up several times since flashing, reboots and all. Just wondering if others are experiencing this or not.
[Fascinate Android Development] zeroxg4:
Mine work correctly on the newest (7/7) build.
[Fascinate Android Development] Bardasian:
There seems to be some undeserved hostility in those responses and I'm not sure what provoked them. I was just simply wondering what themes people were using for CM7 besides the included ones because I liked the widgets/look of the EF Gingerbread theme. Wasn't trying to step on any toes here.
[Fascinate Android Development] nitsuj17:
i was just pointing out that the ef gingerbread them was a port of our comrom theme...and if u like the gb theme and use froyo touchwiz, comrom has more options than ef and the kernels are the same
[Fascinate Android Development] Bubbadogg14:
Im using the eye candy v1.76 theme n it looks sick bro
[Fascinate Android Development] adambobbyburgers:
The microphone only works for voice calls, but not for apps, voice search, voice-to-text, etc. Is this a known issue? Or am I the only one? I'm guessing it coincides with the pre-existing "low volume on the other end during a call" issue
[Fascinate Android Development] Bardasian:
Ah, I wasn't aware that it was a port. I've been unable to find any widgets that resemble the themed ones from the EF version (maybe I haven't been looking hard enough), which is what has been keeping me from ComRom. Other than that, ComRom worked wonderfully for me and has shown a lot more support than EF.
[Fascinate Android Development] Grimis:
Link please
[Fascinate Android Development] solido888:
I can confirm it doesn't work for me with voice search. I am using build 8 with the OTB .13 kernel.
[Fascinate Android Development] hecantbreathe:
eye candy theme
[Fascinate Android Development] lowtech80:
Yeah, I've noticed the same.
[Fascinate Android Development] garywojdan81:
I'm on build 8 with otb.13 since this morning & soundhound works for me. In-call audio is fine & everyone I've talked to has heard me fine.
[Fascinate Android Development] dopepope:
it's funny because the first result I get is just back to this thread.
[Fascinate Android Development] pgm131:
Just so everyone knows I came up with a great feature for android a few weeks ago. I get texts from people all day long that are just "k" or "alright." I thought it would be great to be able to mark those as read in the notification bar with a quick swipe to the right or left. Just a few moments ago I accidentally came across this feature on this rom! I love this thing!

P.S. when did this feature become available. Is it something in gingerbread itself or just on cm7?
[Fascinate Android Development] :
http://xdaforums.com/showthread.php?t=1056292

Enjoy...
[Fascinate Android Development] jt1134:
Lol that was introduced in cm6 almost a year ago :p (I had the same idea before that tho too ;))
[Fascinate Android Development] akaine2001:
Jt you keep replying everyone but to the ten people who are asking u about modem mode/diag mode... Lol

What's up with that, I know by now you could already have given us an answer, or suggest something, anything, we're lagging to death over here.

I mean adryns been doing gb stuff, he might even know, since he made it for 2.2 I just figured him or somebody main line cm MIGHT want to help the flashing community out. On behalf of allof us, plz find diag/modem mode!

Not trying to be an asshole, just really anxious to get back to cm after 8 months with this phone. All this lag, I can't take the lag wiz anymore. Save us jt, for the luv of God plz save us from touch jiz!!

Edit: seriously, i cuss this phone out every day
[Fascinate Android Development] Junkboy0:
We did ask, but honestly he's done so much for us that like i said before, even without data his CM7 builds destroy touchwiz and I can do without it. Again JT thank you for all your work.
[Fascinate Android Development] JoeProcopio:
Ahhhh thank you...and I now remember turning that off thinking it was a confirmation like a PC
[Fascinate Android Development] akaine2001:
Yeah but everyone reads this thread every day obviously, I'm just saying, let us know something, anything, tel us kick rocks, atleast respond tho... I wasn't knocking him or his work, vzw users are a majority, so if it works for them, he's 99% not worried about data working for anyone else since everyone on vzws does work. def. Not knocking him, he just might have not seen it or forgot. But we're still PATIENTLY waiting am I right? Nothing wrong with communicating our interest in it though. Imo
[Fascinate Android Development] Junkboy0:
True enough. Question, will you stick with JT's CM7 (this or Miui) even without data?
[Fascinate Android Development] akaine2001:
yeah. I would... its just I use google music to stream a lot in the car, but I can put songs on my sd again... I was actually downloading the 7 4 build because I tried to go direct to build 8, and that don't work, didn't find that out until today in pcpark87s post.
[Fascinate Android Development] Bubbadogg14:
http://xdaforums.com/showthread.php?t=1016269

This is a link to the eye candy theme... sry for the delay i was at wrk
[Fascinate Android Development] Junkboy0:
Yeah, when I was at the Anime Expo last week I missed google music and pandora in my down time :(
[Fascinate Android Development] church101:
Bad idea to comment right now
[Fascinate Android Development] lane32x:
What are your settings in Voodoo? Also, what was your flashing sequence? Did you start with the 7/04 rom and then update without wiping? Some people seem to be having better luck without a wipe between updates, some better with wipes.
[Fascinate Android Development] Junkboy0:
*edit* nvm
[Fascinate Android Development] akaine2001:
Had anyone tried restoring the apns with apn backup restore? Like you do when originally flashing. The flash is not lost going to cm7, or we'd have to reflash when we odin back... I didn't...

So it must be something with the apns or the rom... Can't believe noone tried that yet. Can you, somebody, try restoring the apns you save in comrom or the cricket/metro one u used?
[Fascinate Android Development] harpdoc:
I can confirm that, other than phone calls, audio-in is broken on this build. No audio recording, voice search, etc. Still no audio out through the car dock either. Other that these things I love the rom.
[Fascinate Android Development] mrtonee:
Have u tried nemesis 07/04 .13 kernel? audio should work with that
[Fascinate Android Development] chrisexv6:
Im confused, whats this talk about no data? 3G data is listed as "working"....did something break in the newest release?

Was planning on wiping my phone and moving to the CM7 side of things tomorrow.
[Fascinate Android Development] Junkboy0:
This refers ONLY to people that are NOT on Verizon, so metro PCS, cricket, ect users lose data but for VZW user it's smooth sailing. So flash away without doubt.
[Fascinate Android Development] lane32x:
If you look back over the last 3 pages of posts, numerous people are using the .13 kernel with the newest rom.

From what I can tell, if you flash the newest rom over the previous rom (and you were already using nemesis's kernel) it seems like it kills the microphone completely.

If you then flash nemesis' kernel, it brings back audio for phone calls, but audio for other apps still does not work.

I haven't tried flashing the last 2 roms, then updating to this rom (without flashing nemesis' kernel at all) to see if that works.
[Fascinate Android Development] ludevious:
I used stock (jt's) kernel from the transition from 7/04 to 7/07 and my mic was nuked as well.
[Fascinate Android Development] Hilbe:
Got CM7 to install. Was getting a boot loop trying to mount my SD card. Replaced the SD card with the card from another device, which seemed to fix the issue.
[Fascinate Android Development] FDro:
Flashed 7/7 on top of 7/4 with cache and dalvik wipe, broke my mic. Flashed OTB kernel, nothing, looked in voodoo app and unchecked recording, nothing. Had to revert back to 7/4.
[Fascinate Android Development] kuronosan:
Flashed it exactly as you described it, and haven't had a single problem.
[Fascinate Android Development] garywojdan81:
I did this earlier as well. Flashed 7/7 over 7/4, both with JT's kernel, and lost mic so I flashed nem's kernel & got some sound functionality back. Phone calls are fine & some sound apps like soundhound work but voice search does not.
[Fascinate Android Development] ezas:
Couple of quick question. I installed 0704 the other night but borked it with a kernel install.

Since then I have had 4 failed install. All went back to stock to start and took slightly different paths to boot loops or hung on Samsung logo.

Finally today I realized that when it worked I had the EC09 Radio, and all four installs last night were with ED04 radio.

So now I'm on dead stock ED04 with a voodoo kernel and lagfix enabled (it was the kernel that enabled lagfix but I know that is not an issue, rooted with CWM installed.

My question is should I do a full reboot after installing 'fixed' CWM, or just boot recovery to get into 'fixed' CWM? Or can I just use infinity's 3.0 CWM that I already have installed?

Also should I do the wipes in my original recovery or once I'm in the 'fixed' recovery?

I know these are nit picky questions but I'd really like my 5th install to work. I only had CM7 working for couple of hours and and I'm eager to get back on it.

Thanks in advance

Update: From ED01 with infinity CWM: I flashed fixed CWM from this thread. Booted into new recovery (using CWM menu). Did my reset and 2 wipes and install the 0707 package and I get the status 7 updater.sh error. Which I know has been discussed so I'll do a search.

Why am I getting this? I did not get this when I successfully installed 0704 the other night? I'm really nit-picky about my installs going right.

Update 2: found the answer easy enough. Here it is for others so they don't have to search:

Another note, if anyone is coming from TW or have ODINed to stock and try to flash Build 8, you will get assert error. Build 8 has updater script that builds upon previous roms (i.e. sort of like a patch).

So if you are coming from any TW rom, ODIN or not:

Flash the fixed CWM3 -> wipe data/cache -> flash Build 7 (07/04) -> reboot recovery -> wipe cache/dalvik (optional) -> flash Build 8 and gapps -> profit.. or flash nem's kernel​

Update 3: followed the above up to flash build 7 which completed without error and the phone rebooted before I could catch it and now I'm in a boot loop, quickly cycling between boot logo and CWM screen. This is mirroring my adventures of last night. Do I need to go back to stock after my aborted flash of Build 8? Or can I just flash 7 over the aborted 8 install. I did wipe all three before trying to flash 0704 and I was using the 'fixed' recovery.

Update 4: Tried flashing build 7 and this time catching the reboot into recovery and it tried to start CWM 4 but ends up in a boot loop again.

Guess I'll go back to stock for try 6. At least now I know to do 04 build before the 07. But question. Obviously I do 04 from CWM 3, but do I flash 07 from CWM 3 or 4?
[Fascinate Android Development] lane32x:
When you came away from the ED0X with Voodoo kernel (and I assume 'lagfix') did you remember to flash the PIT file in ODIN (and checkmark to repartition device) to put your Fascinate's partition table back in order?

As far as I have read, you must have your filesystem back to normal before you start the flashing process.
[Fascinate Android Development] .Ejekt:
Mind linking to the CWM3 you're talking about?
[Fascinate Android Development] lane32x:
It's in the first post in this thread.

...although I actually flashed the CWM from March and that seemed to get me started nicely on all of this.
[Fascinate Android Development] ezas:
I got her done now. The CWM I used is the one in the OP.

I used the EB01 stock package. Pushed the EC09 Radio, and the reg ol' cwm.

Booted into recovery, installed the cwm fix from OP. Rebooted recovery from CWM. Did my wipes, and flashed 04 build and let it boot.

Rebooted via shutdown menu to CWM 4 and installed 0707 builld with no wipes. I prolly should have done my Gapps then but forgot so im booting to get them.

I expect no troubles with that or the OTB flash.

I'm all set. I guess I just had to make all the mistakes first. I'm looking forward to playing with this.
[Fascinate Android Development] ezas:
Well I wasn't expecting trouble with gapps but from CWM 4 i'm getting an error about an /google/android/update-binary.

I got to this point by booting 0707 build. Rebooted to recovery using power down menu. From CWM 4 the usual choose zip, and apply zip.

The error is E:Can't copy META-INF/com/google/android/update-binary

Installation aborted.

No I did not wipe. Sometimes I think I wipe too much and cause problems for myself.

If this has been covered I'll find it in a search otherwise any suggestions appreciated.

Maybe reflash 0707 from CWM orange?

I tried wiping cache/cache, reflashing 0707, and from the same session Gapps and I have the same error. Going to try doing phone/market setup and see if that helps, then comeback and try the gapps flash again.
[Fascinate Android Development] ludevious:
Some of us are getting terrible microphone gain. Could you clarify what you did to obtain "great" microphone pickup?
[Fascinate Android Development] reloaded89:
clockword mod loop + on mac (temp)

okay, so i tried to install CM7 test build 8 onto my phone. the install got up till checking BML/MTD and then failed. i was already on test build 7. anyhows, clockwork said the rom failed to install and then rebooted. now the phone is stuck in a loop of booting into clockwork and then aborting an install.

i would normally have just started up ODIN and flashed down to stock DJ05 or EB01 and then do the lovely root process; but alas i sent my PC into HP today for repair and stuck using a Macbook for a week or two. (no one else in my family uses PC anymore; iPad and Mac family now...sigh)

does anyone know of a way to fix this? i'd like to avoid going back to my old droid 1 (so laggy).
[Fascinate Android Development] Hymizzle:
What is GAPPS???? Do I really need it??

Keep me Fascinated.
[Fascinate Android Development] jkat797:
gapps - Google apps. AKA Gmail, maps, etc
[Fascinate Android Development] Grimis:
Smart ass lol
[Fascinate Android Development] Grimis:
Thank you very much
[Fascinate Android Development] ezas:
I'm all set. Installaling the OTB kernel solved the problem with flashing gapps.
[Fascinate Android Development] jerkules:
Maybe try downloading gapps again too.
[Fascinate Android Development] :
I had to flash build 7 in red cwm (three finger salute). Then I rebooted into the orange one and flashed build 8.
[Fascinate Android Development] jbarcus81:
Not sure about some of the issues with sound, in-call audio/mic issues.. I'm running 100% flawless!! All I did was flash the rom, gapps.. moved on.. Love it jt!!
[Fascinate Android Development] chrisexv6:
Just went over to the CM7 side.

Had an assert error at first, realized I needed to flash build 7 first. Did that, cleared cache/dalvik, flashed build 8. Everything is up and running.

Havent checked out the gain issues and havent gotten any calls yet, but hopefully some testing today will show this is my new daily driver.

Thanks jt!
[Fascinate Android Development] ssewk2x:
I just tried to go this route and ended up becoming intimately familiar with odin...like I might have to marry it, lol!

Anyway, can you maybe post exactly what you did? I'm now thinking I should do something like:

1. Flash bld 7

2. Reboot and let it do its thing.

3. Reboot to orange recovery

4. Flash build 8 and gapps in same session (?)

5. Reboot again and profit

What I'm unclear on is precisely when to flash gapps and when I need to reboot and let things happen before proceeding.

Thanks!

Ps: build 7 is the july 4 version, and build 8 is the july 7 one, right?
[Fascinate Android Development] dopepope:
Same exact thing. Not sure what the issue is?
[Fascinate Android Development] chrisexv6:
Yes, build 7 is july 4, build 8 is july 7.

Im coming from CommROM 2.0:

Used Odin to update the radio to recommended version for use with JTs CM7.

Then used Odin to update CM recovery to the version attached in OP.

I let the phone boot, then used TiBackup to back everything up

Rebooted into recovery, wiped data, cache, dalvik x3.

Accidentally flashed build 8 first, got the assert error. Since I hadnt downloaded build 7 and put it on my SD card, I had to re-flash CommROM 2, boot it and then pushed build 7 to my SD card.

Rebooted into recovery again, wiped data/cache/dalvik x3.

Flashed build 7. Rebooted phone and let it boot all the way up.

Rebooted into recovery again. Wiped cache/dalvik x3 (NOTE: I did NOT wipe data, you need build 7 in place to flash to build 8).

Flashed build 8. Rebooted phone and let it boot all the way up.

Rebooted into recovery.

Flashed gapps.

Profited :)

The basics of the phone are verified as working. I havent checked out the mic gain issues or possible in-call audio issues. I did test bluetooth streaming to my car head unit and it works great (seems to connect faster than ComROMM, but that might just be the new radio version). Downloaded a few apps without issues. DSPManager has changed my life.

NOTE: just checked and Im getting no audio in my calls. Looks like my mic is dead too, will try the OTB kernel shortly.
[Fascinate Android Development] lane32x:
I disabled the "high quality recording" in the Voodoo control AFTER I installed the .13 kernel. That seems to yield excellent in call microphone pickup.

Unfortunately, call volume through the earpiece is still quiet. i.e. they can hear me just fine, but I can't hear them as well.

*edit* also, you do not need to wipe more than once. This isn't a trip to the porcelain throne. Go read the article that nitsuj posted in his ComRom GB thread.