215 replies to this topic

[TomTcom]

No problem. I'll do what I can.

[AtrusNex]

Eatthis, on 05 August 2011 - 09:03 PM, said:

The kernel is left untouched. I am guessing the radio is the same by extension. You say you're using the EC09 radio, is that something you installed yourself, or is it the stock? I am using build 9 right now with stock kernel and didn't even know the radio was something outside of ROM. I haven't had any issues with my GPS as of late, though rampant issues have indeed existed in the past (as I am sure all Fascinate users can attest to..). Have you tried the GPS Status app? It was a godsend when it came to locking my location.

Yes, I pretty much always check my GPS performance with GPS Status first.
So I gave it a shot again. I re-flashed the JT1134 CM Alpha again and, once again, the GPS worked flawlessly. I then tried re-flashing both nightly  8 and 9 and I had the same GPS problem on both. The GPS cuts on and off never getting more that one satellite lock, much like many people complained about when the Fascinate first came out. If nobody else is having the problem then it must be something  I did. Could it be that I used Rom Manager instead of installing it straight from the SD card in the recoverie like I did the original Jt1134 rom?

[Kaik541]

jackgagliano, on 06 August 2011 - 03:14 AM, said:

Hi TomTcom,  I have done all of the above.  I installed the driver on Win7 64 and also tried it on an XP machine to see if that was the problem.. on both cases (on two seperate phones btw) I watched the blue line go across.  i will try adb reboot and see if that works.  thanks for the help

edit:  tried another recovery app, but same thing... i know it has to do with the 3e vs 2e.  i ran across another post that had some files in it for converting the stock recovery back to 2e to get cwm to install correctly.

you must use 3 button salute to recovery for the first install. on top of that, make sure you put the recovery.bin in the Recovery partition and not the kernel (zImage) partition.

[Eatthis]

AtrusNex, on 06 August 2011 - 04:59 AM, said:

Yes, I pretty much always check my GPS performance with GPS Status first.
So I gave it a shot again. I re-flashed the JT1134 CM Alpha again and, once again, the GPS worked flawlessly. I then tried re-flashing both nightly  8 and 9 and I had the same GPS problem on both. The GPS cuts on and off never getting more that one satellite lock, much like many people complained about when the Fascinate first came out. If nobody else is having the problem then it must be something  I did. Could it be that I used Rom Manager instead of installing it straight from the SD card in the recoverie like I did the original Jt1134 rom?

I wouldn't say that it is impossible that it did; there was one install of a nightly I did with ROM Manager ended screwing stuff up, yet a re-flash through recovery left it working fine. I tried out my GPS earlier today and hadn't a problem with locking my location within a matter of seconds and I don't think I've ever had a issue with it arbitrarily turning off.

@jackgagliano  It sounds to me like you have the wrong CWM recovery installed on your phone. http://wiki.cyanogen...ll_Update_Guide. Just follow every step of "Installing the ClockworkMod Recovery" as it sounds like you are doing a step wrong. After installing the zadig (which you said is done) the "recovery.bin" is to be extracted onto your desktop and chosen through Heimdall under the 'Recovery" section. Then hit start (make sure your phone is in download mode) and once it is done you are all set. Your recovery should indeed be teal, and once it is, you can go ahead and clear data/cache and "choose .zip from sd card" and install Cyanogen. I hope this helps.

[cyonsinn]

jackgagliano, on 05 August 2011 - 10:54 PM, said:

Hey guys, I use CM7 on my droid x and i love it!  i'm trying to get my other phones, samsung fascinates to CM7 as well, but running into some difficulty.  I followed the instructions on the upgrade guide, but can't seem to get Clockworkmod recovery installed.  i flashed via USB cable the recovery.bin file as instructed, rebooted the phone, went into ROM manager.  when i go to select the phone model to flash clockwork recovery, there is no option listed for Samsung Fascinate (MTD).  There is a Galaxy S Fascinate listed.  I've tried that one, but no success... it just reboots into regular android recovery mode and says that the file isn't verified.

Thanks a bunch!

i ran in to the same problem you need to use clockworkmod 4.0 not hte 3.3 one rom manager downloads for you

[jackgagliano]

ok here is an update... i decided to try to flash from linux and got the same thing... the little blue bar flashes across and then the phone reboots... the trick is to pull the battery right after it starts to reboot, then immidately boot into cwm recovery... this came up the normal teal that i'm used to.  new problem is now that if i reboot the phone and try to enter recovery mode again, via the 3 button method, it reverts back to the stock blue... making progress, slow but sure, but damn this is a hassle! lol.

[jackgagliano]

hi all, just a quick update, i got it to work... the key is to do the following:

pull the battery just after the reboot starts after cwm is flashed via heimdall
put the battery back in, and then boot to recovery, it was teal for me.
install the cm7 rom from the zip file, i used nightly build 10, and it is working great so far!  (awesome job guys)
after cm7 is installed, i rebooted to recovery and it is now orange, but at least it isn't stock!

hope this helps anyone that has had the same problem i did... maybe someone can update the wiki for alternative installation ideas or something.

thanks again everyone!

jack

[TomTcom]

jackgagliano, on 07 August 2011 - 02:35 AM, said:

hi all, just a quick update, i got it to work... the key is to do the following:

pull the battery just after the reboot starts after cwm is flashed via heimdall
put the battery back in, and then boot to recovery, it was teal for me.
install the cm7 rom from the zip file, i used nightly build 10, and it is working great so far!  (awesome job guys)
after cm7 is installed, i rebooted to recovery and it is now orange, but at least it isn't stock!

hope this helps anyone that has had the same problem i did... maybe someone can update the wiki for alternative installation ideas or something.

thanks again everyone!

jack

Glad you found a work around.

[Quincy2001]

jackgagliano, on 07 August 2011 - 02:35 AM, said:

hi all, just a quick update, i got it to work... the key is to do the following:

pull the battery just after the reboot starts after cwm is flashed via heimdall
put the battery back in, and then boot to recovery, it was teal for me.
install the cm7 rom from the zip file, i used nightly build 10, and it is working great so far!  (awesome job guys)
after cm7 is installed, i rebooted to recovery and it is now orange, but at least it isn't stock!

hope this helps anyone that has had the same problem i did... maybe someone can update the wiki for alternative installation ideas or something.

thanks again everyone!

jack

I had a similar issue with flashes from either Odin our Heimdall. Mine ended up being the usb ports on the pc. After 2 days of failures following known good instructions, I switched to my laptop and it worked the first time. After coming from an OG Droid, I've missed a good working CWM recovery. Thanks to the Cyanogen Team for getting this together.

Edited by Quincy2001, 07 August 2011 - 03:28 PM.

[AtrusNex]

I think I've traced down the problem somewhat with the GPS. It appears that the connectivity of the radios (at least the Wifi, CDMA and GPS) stops actually transferring data even though it appears to be properly connected. The only thing that seems to fix the issue is a battery pull. Other than that, the GPS does occasionally turn off while in use but it's usually just a short blip and it usually recovers without causing any issue. Other than that the ROM is working great, I believe I've even found an application to give back some of the functionality of the Samsung camera app as well.

[LordJim]

Problem Description:  Proximity sensor turns off screen during phone call, won't turn screen back on when phone is removed from face.


There's not much more to say about my problem.  During a call, or after a call has ended, I have to push the power button to get the screen to come back -or- wait for the other party to hang up and the screen will come back on its own.  I ran CM7 on my OG Droid since the beginning and this was not an issue on that device, so I'm assuming that it's particular to the Fascinate.

Anyhow, I found a user on XDA who seems to be having a similar problem, but with MIUI (is that based off of CM, perhaps?)

http://forum.xda-dev...d.php?t=1201225

So, what I'm after is this:
  1) Am I the only one having this issue?
  2) If you've had it and fixed it, what did you do?  


Thanks,
Jim

[AtrusNex]

LordJim, on 07 August 2011 - 11:21 PM, said:

Problem Description:  Proximity sensor turns off screen during phone call, won't turn screen back on when phone is removed from face.


There's not much more to say about my problem.  During a call, or after a call has ended, I have to push the power button to get the screen to come back -or- wait for the other party to hang up and the screen will come back on its own.  I ran CM7 on my OG Droid since the beginning and this was not an issue on that device, so I'm assuming that it's particular to the Fascinate.

Anyhow, I found a user on XDA who seems to be having a similar problem, but with MIUI (is that based off of CM, perhaps?)

http://forum.xda-dev...d.php?t=1201225

So, what I'm after is this:
  1) Am I the only one having this issue?
  2) If you've had it and fixed it, what did you do?  


Thanks,
Jim

I can affirm I also have this problem. Just tested it a few times.

[cyonsinn]

i have the same sensor problem to. but i just noticed after updating to nightly 11 my incall volume is so low i can barely hear people. anyone else having this issue?

[TomTcom]

Out of curiosity, what is the criteria for a stable or RC release? For example I believe the Captivate was up to 67 nightly releases, are those just additional tweaks to a stable mod?

[AtrusNex]

Pretty sure a Release candidate, is when the developer can no longer find any errors on his/her own. Stable is when the test group from the release candidate can find no major errors. Could be wrong though, and I'm sure the definition varies from one developer to the next. My Droid had a release candidate pretty much after it stopped regularly crashing and more than 80% of the features, with all the main ones, worked.

Edited by AtrusNex, 08 August 2011 - 10:53 PM.

[TomTcom]

Thanks for the reply, I figured that...it's just difficult to see where the Fascinate stands at this point even looking over the nightly change log. I know a comment was made earlier that the nightly for the Fascinate is pretty well done so just wondering.

[AtrusNex]

Well the OS has been stable on many other phones for a while now which certainly helps speed up the development on this phone I would guess. Instead of having to write an entirely new section of code instead you just have to adapt the code and drivers that already exist to meet this phone's specifications. This is evident by showing that the fascinate is as stable at only 4-5 nightly releases as other phone were after ten times that amount of releases.

[Quincy2001]

LordJim, on 07 August 2011 - 11:21 PM, said:

Problem Description:  Proximity sensor turns off screen during phone call, won't turn screen back on when phone is removed from face.


There's not much more to say about my problem.  During a call, or after a call has ended, I have to push the power button to get the screen to come back -or- wait for the other party to hang up and the screen will come back on its own.  I ran CM7 on my OG Droid since the beginning and this was not an issue on that device, so I'm assuming that it's particular to the Fascinate.

Anyhow, I found a user on XDA who seems to be having a similar problem, but with MIUI (is that based off of CM, perhaps?)

http://forum.xda-dev...d.php?t=1201225

So, what I'm after is this:
  1) Am I the only one having this issue?
  2) If you've had it and fixed it, what did you do?  


Thanks,
Jim

I also have this issue. It is annoying, true, but I love this ROM!

[nospam2k]

First, I just want to say thanks for everyone responsible for CM7. My fascinate is actually usable now. Incredible battery life, clean. Everything works. I only have one thing that I'd just like to watch for. I know the LED as a flashlight isn't working. Not a major problem for me with all the other improvements but, is there a changelog somewhere that I can watch just to track changes to the nightlies so I can know when/if this gets addressed? Again, I really want to express my appreciation to all involved in CM. You've have really made the Samsung Verizon Fascinate a usable phone.

[Kaik541]

nospam2k, on 09 August 2011 - 02:52 PM, said:

First, I just want to say thanks for everyone responsible for CM7. My fascinate is actually usable now. Incredible battery life, clean. Everything works. I only have one thing that I'd just like to watch for. I know the LED as a flashlight isn't working. Not a major problem for me with all the other improvements but, is there a changelog somewhere that I can watch just to track changes to the nightlies so I can know when/if this gets addressed? Again, I really want to express my appreciation to all involved in CM. You've have really made the Samsung Verizon Fascinate a usable phone.

http://cm-nightlies....ce=fascinatemtd