yashsingh1/xdaforums huggingface dataset:
[Fascinate General] TheSpecialEd:
I keep getting stuck after flashing both Miui 6.24 and Cm7 test 5, I must be doing something wrong somewhere.

I started out trying to flash from UKB 2.1 with OTB 1.6, didn't work, so then I tried to Odin and Heimdall the fallowing packages with atlas 2.2 pit, DI01, DL09, EB01; ED03, reboot, then flash navenedrob-nemesis2all-OTBv2-CWM3-recovery.zip, reboot, and flash the Miui and CM7, and then it restarts and displays the Galaxy S Cyanogen Mod boot animation, but then it brings up an screen that looks like CWM that says:

ClockworkMod Recovery v4.0.0.5

Waiting for SD Card to Mount (20s)

Waiting for SD Card to Mount (19s)

(counts all the way down) then bootlaps back to the same screen indefinitely.

So any Idea on how to remedy this?
[Fascinate General] Headcase8911:
That's fine because you wouldn't likely be assigned to the fascinate and then we wouldn't have you here to help.
[Fascinate General] kidserious:
Try this method exactly the way I have layed it out and see if this fixes your problem. http://xdaforums.com/showthread.php?t=1124391
[Fascinate General] TheSpecialEd:
Okay, just have to wait for my slow ass internet to download the files. If you don't mind my asking, whats the difference between using your method and the way I was doing it?
[Fascinate General] kidserious:
I don't really know because it was hard for me understand what you wrote, and I'm preoccupied also. But, I think that if you follow that method to the t, it will probably fix your problem.
[Fascinate General] TheSpecialEd:
Oh, sorry about that.

Well it worked to get me back to stock, so I flashed times_infinities cwm3 with odin, then navenrobs cwm3 from times_infinities cwm3. Tried to flash cm7, it reboots shows the bootanimation, then a screen pops up that has a cwm background:

ClockworkMod Recovery v4.0.0.5

Waiting for SD Card to Mount (20s)

Waiting for SD Card to Mount (19s)

Waiting for SD Card to Mount (18s)

Waiting for SD Card to Mount (17s)

Waiting for SD Card to Mount (16s)

Waiting for SD Card to Mount (15s)

Waiting for SD Card to Mount (14s)

Waiting for SD Card to Mount (13s)

Waiting for SD Card to Mount (12s)

Waiting for SD Card to Mount (11s)

Waiting for SD Card to Mount (10s)

Waiting for SD Card to Mount (9s)

Waiting for SD Card to Mount (8s)

Waiting for SD Card to Mount (7s)

Waiting for SD Card to Mount (6s)

Waiting for SD Card to Mount (5s)

Waiting for SD Card to Mount (4s)

Waiting for SD Card to Mount (3s)

Waiting for SD Card to Mount (2s)

Waiting for SD Card to Mount (1s)

Then reboots and does the samething over and over.
[Fascinate General] kidserious:
Are you using the standard 16gb SD card or a 32gb?
[Fascinate General] TheSpecialEd:
Standard 16gb that it came with.
[Fascinate General] kidserious:
Have you tried re-downloading the rom that you are flashing that is causing that problem? It could be a corrupted download. And I don't know if you did this or not but after you odin and you get back to stock, flash the ext4 formatter from navenedrob's recovery. Once that flashes, do a wipe data/factory reset then flash the rom you are flashing that you have hopefully re-downloaded.
[Fascinate General] times_infinity:
Try a different sdcard. Lol
[Fascinate General] TheSpecialEd:
Tried to redownload, then flash ext4 formatter, wipe data, flash cm7... Got Section 7, failed to assert getprop. Oh and I tried with a 8gb sd card this time :/ so?
[Fascinate General] kidserious:
Hmm.....let me think. If I can think of something else, I will post it.
[Fascinate General] times_infinity:
Remove the asserts from updater-script in the zip.
[Fascinate General] TheSpecialEd:
How would one do that?

*Edit* Nevermind, I flashed Test 3 and then Test 5 and it works so far, so thank ya'll for the help
[Fascinate General] nemesis2all:
Extract zip. Go to META-INF/com/google/android/updater-script and remove first 4 lines. Save file. Zip it back up. Flash and enjoy.

Someone please put this somewhere for everyone to see.
[Fascinate General] slayer214:
Ok I am getting install errors in clockwork. Everytime I try to install, it says error installation aborted, something about "status 7." I have never had this problem before. I saw were you need to delete the 4 lines in the update script, but what exactly do I need to delete? Or what do I need to do to be able to install?

I am currently running jt's 5/18 build port to showcase if that helps.

Thanks,
[Fascinate General] slayer214:
For some reason I cannot get the edited updater-script zip to flash. Maybe it is because I am using a showcase, so there is other parts to delete, or I am doing something wrong. Can some post an edited updater-script that would work with the showcase? Or even the zip file that has been edited?

Thanks
[Fascinate General] BTownTKD:
Has JT indicated that he might have an idea what is causing the deep sleep/phantom ring issues, and just needs to get around to it? Or is it a real head-scratcher?
[Fascinate General] kidserious:
JT has stated that he believes the problem lies in the gpio (general purpose input/output) sleep/wake settings in the kernel. I'm sure troubleshooting this problem will be similar to trying to find a particular needle amongst a TON of other identical needles. It will take time and looking but he will get it eventually.
[Fascinate General] kuronosan:
I seem to be having issues with the light sensor not working. I downloaded a sensor tester just to see if everything was kosher and the light sensor is always active even when I block out the phone. Proximity sensor seems to work fine (when close it returns a 1, when distant it records a 0).

I made sure I downloaded the right file, wiped the cache accordingly, and reflashed everything to be sure. Is there any other thing I might be doing wrong?
[Fascinate General] lammers42:
I will confirm that when brightness is set to auto that changes in ambient light doesn't change brightness. I haven't tested it to see what the sensor output actually is when ambient light changes though. I don't use auto brightness though, so for me it doesn't really matter.

I would rather use this rom from jt though because I have the same missed calls/deep sleep issues with the Comrom series and stock ED01 builds also. I haven't tried ED04 or EC09 because nothing crashes when I use this CM7 rom. Before he fixed the accelerometer and proximity sensor to work at the same time I used Screebl which worked about 80% of the time for keeping the screen locked on during a call. I use Softlocker for wake lock and you lose about 5% battery life an hour while idle. This means with my moderate use I get about 10-12 hours of battery life at minimum brightness settings.

It still is the best daily driver I've used since froyo got leaked though! I just would like speed dial with more than 9 speed dial locations. I would use Go Dialer if it did have this or the Samsung dialer if anyone can confirm that we can install it and it work and not force close/interfere with the stock CM7 dialer.
[Fascinate General] landshark68:
Everyone having the Status 7 or get.prop errors when trying to flash CM7 test 5, read the OP. I updated it with nemesis2all's instructions on how to remove the asserts from the updater-script file so you can flash the ROM successfully.
[Fascinate General] sageDieu:
Hey guys, I'm the one that started the Droid X argument a few pages back. Totally forgot about this thread for a bit. Just wanna say, I have used the X just as much as the Fascinate/Mesmerize and yeah. I know what I'm talking about when I say it is better. Everything is just much more stable. So... yeah. But I'm also running the new CM7 from 626 and I gotta say, it puts me pretty close to the Droid X in terms of performance. Their nightly from yesterday fixed MMS so that is all they have on us at this point. That and our kernels I guess, voodoo and everything is great.

Sent from my CM7 SCH-i500
[Fascinate General] kidserious:
I beg to differ. Stock kernel = stock suckiness. Just my opinion, not trying to start an arguement.
[Fascinate General] 420fan:
Random soft keys, random keyboard showing up and lots of haptic feedback, anyone else or is thus hardware related?
[Fascinate General] Dread This Day:
Has the 6/26 build/kernel ****ed up anybody else's Wifi? Mine just will not connect to KNOWN networks, and randomly the Wifi period just shuts off. Any suggestions? My only thought is to flash the next latest kernel.
[Fascinate General] anon_72:
After 36 hours

I have to say, that after running the latest CM7 rom and OTB kernel, that my fascinate is running absolutely amazing. No force closes, no bootloops, decent battery life. I have voltage control running on bfq scheduler, on demand CPU governor 1200 Max 200 min. With this setup, my screen doesn't shut off when I make outgoing phone calls, and I've gotten only 1 phantom ring and have received 5 calls with my screen off without softlocker or any other wakelock program. :)
[Fascinate General] SOTK:
Noticing that after shutting off wifi my 3g isn't coming back. I get the 3g icon but no movement in arrows. Have to reboot phone in order to get 3g back and working. FYI

Also, is it possible to have speed dials with cyanogen mod? Noticing that I have multiple contact entries for some of my contacts. Weird. Whats up with that?
[Fascinate General] sageDieu:
Try GO Contacts for speed dial.

I can confirm the previous posts as well, random haptic feedback and key presses as well as wifi not working... my wifi doesn't even turn on at all.

Sent from my CM7 SCH-i500
[Fascinate General] lammers42:
I do not have issues with WiFi and don't have random haptic feedback and button presses.

When I first installed the 6/09 update I lost my search and home capacitive button functions. I did a factory reset and cleared cache and all was back to normal.

Before I installed test build 4 I cleared data and cache again, flashed and cleared data and cache after install. I restored with Titanium and rebooted and all has worked great. I flashed the proximity .zip to test call functions with it and it worked but I missed not having auto-rotate so I flashed back.

I flashed test build 5 without clearing data and cache and everything has worked great except deep sleep/missed calls, issue with all 2.2+ rom/modem combinations, and the light sensor (may cause issues with pictures and flash detection for auto setting and auto brightness settings).

If you have issues try clearing data and cache . . .

edit: Oh and GO dialer and all other market dialers that I've found only have 9 speed dial locations. Favorites is just as good as that . . .
[Fascinate General] lukusb83:
install issue

So, I was on ComRom 2.1, and have been waiting until the censors were fixed to try this... did a nandroid backup, backed up my SD and was ready to go.

Edited the CM7 ZIP as instructed in the OP and flashed the file.

After it rebooted to do the install, it keeps boot-looping. It shows the Galaxy S/CM boot logo, and then does a count down from 20s waiting for the SD Card to mount. Tried pulling the battery without any change.

What am I doing wrong?
[Fascinate General] kidserious:
I believe the status 7 fix that is described in the OP applies to this as well. Read the Original Post by landshark in this thread.
[Fascinate General] lukusb83:
Okay, I will try again. Restored back to where I was and DL'd another copy of the ROM just for good measure. Will follow OP instructions again and see what I end up with this time.
[Fascinate General] lukusb83:
Well that didn't work either.

I am using a 32GB SD card... could that cause this issue?
[Fascinate General] Ianxcom:
What was the name of the app to prevent the deep sleep call issue again? Is the battery drain really that bad?
[Fascinate General] mwestendorf:
Softlocker and yes/depends

If you use your phone a lot anyways then I doubt you would notice since your phone would rarely enter deep sleep.

Just my opinion

Sent from my SCH-I500
[Fascinate General] dmaustin:
I haven't really seen anyone comment on audio issues yet. In call audio seems quiet. Everyone I talk to has trouble hearing me unless I talk loudly directly into the mic. Sometimes they don't even hear me answer the phone. And earpiece volume on my end seems low at Max.

Also the loud speaker on the back is definitely quieter when ringing and playing music.

Not complaining just posting because I haven't seen anyone else say it. Is there some work around or setting I'm missing?
[Fascinate General] SOTK:
I've noticed all of the same except I have no problem hearing others in calls. They just can't hear me very well. I've also noticed ringers, notifiers, and music is a lot quieter in comparison to touchwiz froyo. So far, I think I can live with these things but I do hope the call stuff is fixed soon as well as the deep sleep! Not complaining just hoping! :-)
[Fascinate General] rand4ll:
Does anyone have a way to use the hardware equalizer on the wolfson chip by chance? Galaxy tuner doesn't work...
[Fascinate General] kidserious:
Yes, actually I think that is the issue. Try it again with the 16gb SD.
[Fascinate General] sageDieu:
I've had the same issues. Not much can be done until it gets noticed by jt!
[Fascinate General] Headcase8911:
I believe cm 7.1 was released, is that what we're running or is that something different?
[Fascinate General] landshark68:
We are on 7.1.0
[Fascinate General] kuronosan:
I posted this in the other thread, but is there any chance cradle audio will be supported/fixed? Seems kind of pointless to have the app as part of the package if it never outputs any sound.
[Fascinate General] TheHobbyist:
Hi, it's been a long day and I'm feeling feisty, so here it goes:

It's kind of pointless to have the app as part of the package if it never outputs any sound? Really? Is that so captain obvious? Maybe if you are rude about it you will get what you want? Here is a hint: The rom you are running is ALPHA. What that means is that it is not complete and it is a work in progress, which is clearly stated in the OP. Furthermore, it's probably not a top priority until all of the basics are ironed out. Makes sense, right? If there is a feature not working, or there is a bug that you discover, AND the developer is requesting bug reports, try something like this:

Hello JT, thank you very much for developing this software on your free time unpaid. You have done great work and it is much appreciated. I am running the 6/26/11 build of this rom with <insert modem> and <insert kernel> and I noticed that cradle audio does not seem to output any sound. Here is a logcat of my phone when I try to use the cradle <insert link to logcat> Let me know if there is any other information I can provide to help!

Thanks again!

So many ungrateful, impolite people on here that are absolutely not helpful and are sofa king rude.
[Fascinate General] tripacer99:
Err...I may be reading his post differently, but I don't think his intentions were to come off as ignorant or rude. He was just asking a question and pointing out something. If you saw some of his earlier posts, you would see him thanking and praising jt for his hard work.
[Fascinate General] Bensaved:
Totally didn't read his comment as rude. Flaming someone for a comment, perhaps. But that's just my perspective, as one who is still but a humble student in these forums.
[Fascinate General] kuronosan:
Woah dude. Go sit back, put down the sword and shield, and take a chill pill. I think you took my statement in a totally different direction than you needed to for very little reason.

And yes, it is a little pointless for me to have this car cradle if it cannot be used. What I said had nothing to do with the quality of the software, just pointing out that the cradle app should support usb out, not that jt is a scumbag for not hurrying. I don't want an ETA nor am I going to cry if he doesn't get around to it. He's already done fantastic work.
[Fascinate General] dablitzkrieg:
I love internet tough guys. Generally overweight men, living in mom's basement, with a stained wife beater on, picking there nose, and sucking on there thumbs in their underwear with skid marks on it. Cool story bro:p
[Fascinate General] skynet11:
Look, man, I'm PHAT! :D (Oh, yeah, I'm typing this from the top floor of my own house, but, then, I'm not an Internet tough guy to begin with :D)

Another Fascinating post by my XDA app...
[Fascinate General] TheHobbyist:
Am I really off on seeing this method of bug reporting/commenting as bad taste? Let's try a few more bug reports in the same style, and see if you still disagree...

IMO that comes off poorly. If your goal is to have a feature supported/fixed, the first thing that occurs to me is that I would want to provide the developer with the information he needs to investigate/address it, and to do so in a concise and polite manner (to encourage their attention and effort).

My post is constructive criticism to encourage a higher quality of posts that will lead to better results. The posts that I am seeing do not include BASIC information such as ROM version, modem, and kernel. They also lack logcats. As jt1134 said, he cannot "fly blind" on this stuff, posting without this information is not useful. As someone who is very familiar with the English language, "Seems kind of pointless to have the app as part of the package if it never outputs any sound" implies that jt1134 has pointlessly included the app, since it does not function correctly in this ALPHA build. I hardly think your goal should be to tell the developer that things he does are pointless.

Repeating myself, I propose something more along the lines of:

Hello JT, thank you very much for developing this software on your free time unpaid. You have done great work and it is much appreciated. I am running the 6/26/11 build of this rom with <insert modem> and <insert kernel> and I noticed that cradle audio does not seem to output any sound. Here is a logcat of my phone when I try to use the cradle <insert link to logcat> Let me know if there is any other information I can provide to help!

I don't have a sword or a shield, nor am I an internet tough guy. When I see people making bug reports/feature requests without any of the relevant information, and then going on to call the developer's actions pointless (perhaps unintentionally) I feel compelled to respond and provide constructive criticism.
[Fascinate General] kuronosan:
I'm sorry, that's a pretty poor way to defend your argument. Nowhere in JT's posts does he mention whether the car dock works or does not work, and as I've discovered it's a kernel feature that enables this and not a ROM feature. Gingerbread natively supports cradles.

You're taking my comment and turning it into something negative when it wasn't intended as any such thing. The app is pointless to me because it cannot be used. This isn't JT's fault. To me, the MyVerizon app is pointless. That doesn't meant the developers are retarded idiots who aren't worth my time.

I have told him plenty of times his work is greatly appreciated. I would like it if this app could be functional on the phone. Simple as that. There's no malice, no greed, and there's certainly no unappreciative overtones, let alone the "rude and impolite" tone you assigned to my post.

As if that wasn't enough, nowhere did you provide constructive criticism. Your post came off as jerkish and rude, acting like you were coming to jt's defense when nobody was attacking him. No logcat was posted and no feature was requested because it's not a bug and there's no telling if it's just me not thinking straight or if JT knows or doesn't know.

I'm not going to kiss somebody's ass because they're spending a lot of time on something that is free, but I am quite appreciative that these guys spend countless hours and days on this software and I would gladly pay for it if I had to.

Maybe you should put on somebody else's shoes before you start criticizing the way they tie their laces. It would certainly make you look less petulent.
[Fascinate General] rand4ll:
alright, so I am trying to flash back to commrom, and I have the atlas.pit file and check repartition in heimdall, however, whenever i check the repartition flag the start button to flash on heimdall goes gray and won't allow me to flash, any ideas why this is happening? It actually allows me to flash anything else, and it would let me flash the pit without repartition checked, if anyone has any clue on how to fix this that would be great...

edit:

nevermind, i just had to flash the entire package, including the modem, which I was leaving out to keep ed04, guess i will use the diff packages to flash back to ED04.
[Fascinate General] SOTK:
In case any of you have missed it, the official Cyanogenmod MTD thread has post where it shows the in call volume issues have been fixed. I should say rather they found the culprit to the problem. Uncheck hifi recording in Voodoo Control app. I've tested and it took care of the low volume issues I had. People are saying my voice now sounds more normal.
[Fascinate General] SOTK:
This thread has gotten long. Could somebody offer me some suggestions on how to setup voltage control with the latest nemesis kernel for this Rom? I'm experiencing some slowness/lag and I think it's due to me setting things up wrong. So, tips and suggestions please? Best performance and battery combo. Thanks much!
[Fascinate General] mwestendorf:
I know for me I never had that setting enabled. However, Pcpark87 also recommended I set the microphone gain presets to original. I've only made two calls but they could hear me clearly. Where as the 4 or 5 calls I made earlier today not a single person could hear me.

Sent from my SCH-I500
[Fascinate General] kuronosan:
I honestly think it depends on your phone. Someone from the last OTB said noop+Smartass worked pretty well, so I put my phone on that and I've gotten really good performance results.

I tried ondemand and every time I loaded up a game it was lag city.
[Fascinate General] SOTK:
Thanks. I will give that a shot and keep experimenting.

Do you or anybody else know how to disengage bln with cyanogen? The backlighting for emails and whatnot is eating up my battery.
[Fascinate General] iofthestorm:
I think the reason you still need to do this is because the defaults are to have it enabled, so if you don't change the settings that's what it'll be.
[Fascinate General] fortesquieu:
Phantom ringer is killing me! And I refused to use softlocker! :p

So when it happens, how do you stop it?
[Fascinate General] skategeezer:
Tweets indicate MIUI 1.7.1 in works today for fascinate. Go JT and andmer. The wonder twins :) we now have two stellar GB roms.

Also they may have the led flash working.
[Fascinate General] fortesquieu:
It should be out in next couple of hours, the thread is already created by andmer!
[Fascinate General] cwd500:
I flashed build 5 last night and installed softlocker, this morning I opens CPU spy and it said that I spent 89% in deep sleep.
[Fascinate General] mwestendorf:
Silly question but did you open softlocker and hit the big lock to enable it?

Sent from my I500
[Fascinate General] Headcase8911:
can anyone confirm that the deep sleep issue has been resolved? Also, what are the fixed recoveries all about that jt posted on the opening page?
[Fascinate General] Keithn:
It seems to be, mine awoke from a call. You may want to disable/uninstall soft locker and try calling or having someone calling your phone when in deep sleep just to see.
[Fascinate General] nemesis2all:
Fixed recoveries will allow you to flash cm7 builds without running into problems with asserts.
[Fascinate General] Headcase8911:
that's what I was hoping, thank you sir.
[Fascinate General] kallell:
So close to flashing. Come on mms issue :D

Good work devs!
[Fascinate General] lukusb83:
Does anyone know if the newest CM7 (build 7) can be flashed from a 32GB SD? I don't have the 16GB that came with it anymore and had issues with the SD not mounting during install. I tried flashing from the "CWM3_fixed_for_cm7-ODIN" with the same issue (SD wouldn't mount during install).
[Fascinate General] ssewk2x:
Aaaaaaazagh!

It figures, the day this comes out is the day my computer dies (and with it, my ability to odin anything). Don't want to flash this without a way back, so looks like I better hope I can fix0r my box...