yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] GizmoDroid:
Haven't looked around yet to see if there is a solution, or done much troubleshooting, but I thought I would drop by to report some oddities.

Currently running:

Nightly 93 w/included kernel

Stock Clock and UV settings

Notification ringtone stopped working somewhere along the way. I saw on the changelog mention of it being fixed, so I flashed the nightly 93 (w/o any wipe). Reboot... They work! Now, 4 hours later, they've stopped working.

In the past week, I have had to pull the battery once due to the Sleep of Death (i.e., no response while locked, screen black).

Also, as long as I can remember the "Mute camera shutter" option has not been working. It still makes the shutter noise, even if it's checked.

And of course, there is the standard random errors that seem to plague this phone all the way back to the eclair days, with the radio connection getting stuck and having to toggle airplane mode. Not that frequently, but it still happens from time to time. At this point, I think we just need to blame Samsung for this.

If these bugs have been reported already (chances are, they have, unless I have something weird in my setup), then don't worry about correcting me :p. I will be reading up through this thread soon. Like I said, I haven't done any investigating, so they may very well be fixed by a wipe or something of that nature. (just needed to get this post written while I have the chance)

As always, thanks to the devs for your hard work. The above errors are the .1% of time, which does nothing to take away from the other 99.9% of the time that I have a blazing fast, feature rich, and stable phone.
[Fascinate Android Development] dallas6672:
just a quick fyi, its better on the phone to hold Volume Up & Power button (hold for several seconds) to force a reboot than to do a battery pull.
[Fascinate Android Development] froalskiner:
Yeah I figured there was an issue in there somewhere. So i'm on Stable, is the best method for updating to nightly:

Reboot using power button into recovery

Nandroid backup

run the "ultimate kernel clean script"

wipe partition cache

wipe dalvik

install nightly(89 perhaps)

reboot

?
[Fascinate Android Development] Syndacate:
Yeah, that's pretty much what I do, less the backup.

I save the zip on the phone, reboot into recovery via hold power >> reboot >> recovery mode, clear cache partition, clear dalvik cache partition, run kernel clean script, install zip from sd >> install nightly, reboot.
[Fascinate Android Development] froalskiner:
Ok, that seems to be doing the trick so far. No FC's after following the steps above. The only issue I have right now is with video recording. Granted I haven't searched to see if this is a pre-existing issue for anybody yet. When I record HD video it starts to get jumpy if I record over a minute of video. The audio is good but the video skips around quite a bit. I haven't tested lower quality video settings yet but hopefully this is something the devs know about and can at some point address.

Other than that it's looking great! Great job devs!!!

EDIT: Looks like others have video recording issues as well any may be a hardware acceleration problem...?
[Fascinate Android Development] Syndacate:
It sounds like a memory leak, but I don't use the recorder, so I haven't experienced this problem.

EDIT: It doesn't really sound like a HA problem to me..I don't even think the viewport decoding for the video stream is HA in the first place, doesn't make a lot of sense to do so, IMO.
[Fascinate Android Development] erivnocmc:
Who knows what sound is played during an incoming call, before the actual call?
[Fascinate Android Development] dr_w:
No i didn't....never have. Should i?
[Fascinate Android Development] DevinLeFevere:
ringtonez.
[Fascinate Android Development] Syndacate:
Can't hurt.
[Fascinate Android Development] erivnocmc:
logical)) Why are two sounds playing?
[Fascinate Android Development] dr_w:
Thanks...it didn't fix any of my issues. Also my haptic feedback doesn't work.
[Fascinate Android Development] azpirin1:
Are we talking about the phantom rings? If so, it's like a factory setting connecting ring sound. Yesterday which happened only once but my incoming call wouldn't display no alerts except that continuous phantom ringing. I couldn't turn it off. I rebooted the phone and thats when I knew it was an incoming call because there was voice mail waiting.
[Fascinate Android Development] erivnocmc:
Yes, the phantom rings. How to get rid of it?
[Fascinate Android Development] saps:
The truest answer is that it just happens on random occasions with MTD ROM's. I've seen this myself a few times and it didn't matter if I was on VGB CM7 or PoolParty. Mind you its not consistent, that is, at least for me it comes and goes. The solution escapes us as changing modems doesn't solve it. Many MTD rom users haven't ever seen the problem even once. But too many of us have it on the aforementioned random occasions it's a definite problem. Having said that and to put it in perspective. Since July I've had maybe 4-5 phantom calls, that's it.
[Fascinate Android Development] chopper the dog:
To add to this. It has only happened to me right after rom flash. After that it never happens again till next rom flash.

good day.
[Fascinate Android Development] Syndacate:
Yeah, pretty much dead-on. I've seen it on CM7 and VGB, only used PP for like 2 days, so I can't say much about it.

I've got phantom ringtones on both since probably about the same time maybe collectively < 10x, completely random, completely modem independent. Def. gone a really long time without hearing it, both before the first time I heard it, and after the last time I heard it.

---------- Post added at 01:00 PM ---------- Previous post was at 12:59 PM ----------

Yeah, that's probably a good point. I never really notice in the long term, as I just spoke about, so that really kind of only leaves the short term...and seeing as I haven't been on VGB for more than 2 weeks, definitely begs the question of an unknown state part of the OS is in after flashing.
[Fascinate Android Development] Justice8908:
Any fix for the NFL mobile bug yet?
[Fascinate Android Development] dug-e-fresh:
Latest build (#96) observations...

Quadrant is down to 1800 @ 1.3 ghz (from 2400-2500)... but the textures are loading on the 3D modeling test. I haven't had it render the textures since early this year... welcome sight!

During Quadrant, the I/O test seems to be lagging on #2 like it did when stock. ie- no "lag-fix".

With "lag-fix" my phone typically scores 2700-2800 in the I/O category. Now its down to 850-950.

Does the latest build revert back RFS? Or is it something else?

def
[Fascinate Android Development] Jazz848:
Quadrant scores are very unreliable and rarely provide a true measure of performance. Are you noticing lag in real-world use? Also, are you wiping cache and dalvik between builds? Do you have your governor set to Powersave or Conservative, per chance? Finally, based on your comment about this being the first time it's successfully loaded 3D textures since "early this year," I'm also curious as to when you last did a full wipe.

As for lagfix and rfs, those are completely out of the picture on an AOSP rom. A switch from MTD (especially between nightlies) just isn't gonna happen.
[Fascinate Android Development] exzacklyright:
How do you turn off the camera sounds?
[Fascinate Android Development] Syndacate:
Settings >> CyanogenMod Settings >> Sound >> Mute Camera Shutter
[Fascinate Android Development] dug-e-fresh:
I understand the inherent "shortcomings" when using benchmark software, but to dismiss the results entirely, IMO, is silly... especially considering with the incremental changes (for the most part) in the nightlies... its a nice way to get a snapshot of how things are coming together. Again IMO.... globally.

90% of the time when my phone has "issues"... it shows up in benchmark testing as lower values than typical. When running Glitch's kernals, I've noticed better 3D performance (fps) compared to the CM7/JT kernals... and I've attributed that to Glitch overclocking the gpu... whereas so far as I know, CM7/JT kernals do not. Being able to put a number to it also justifies what I am seeing when using it. ie- in this case 3D performance is kicked up a little but in REAL world as a result of gpu OC... and the change is obvious when looking at the Quadrant 3D score.

And as noted, these are simple observations. I don't know how many times something's been going on with my phone and I wasn't sure if it was JUST me or others as well. By posting what I see... it can help others determine if that behavior is "normal" or not. The textures not loading has been a fairly common problem.

As for wiping... I always wipe dalvik/cache... every flash... and know that I am not new to this. I've been flashing successfully for over 2 years on numerous phones (not bricked a one). I am no guru... but I am certainly not a newb.

Regarding full wipes... I usually only do this when there is a problem... or a significant change. Last time I did a full wipe? Probably 3-4 weeks ago. But know this, the 3D textures have been absent since I switched to a gingerbread rom w/lagfix. I'd say that was back in April/May, if memory serves. And I have wiped MANY times since then and NEVER to have the textures load.

The governors... when I test, I test right after a flash, without changing anything and I don't take the first number (which in my experience is when you'll see the greatest delta caused by governor tweaks). I'll do 3-5 back to back to get a good idea where it consistently hits.

And you say that lagfix, rfs, etc is out of the picture here... I have no idea... but what I am saying is that based on what I am seeing during a Quadrant test (again just simple observations), the test is hanging on I/O EXACTLY like a stock Fascinate without lagfix, ie- rfs and coincidentally is now loading the textures... just like a stock fascinate on rfs.

That's all I am saying.

def

PS- haha... #96 has otherwise been VERY snappy on my phone. Very smooth. thanks devs.
[Fascinate Android Development] GizmoDroid:
This doesn't work for me.
[Fascinate Android Development] Jazz848:
Apologies, was not trying to imply lack of experience on your end or otherwise offend. Just wanted to verify background of your current installation.
[Fascinate Android Development] Justice8908:
Anyone else having problems with video apps like NFL mobile?
[Fascinate Android Development] Syndacate:
What does it do? Just doesn't do anything - shutter sounds fine?
[Fascinate Android Development] TomTcom:
Nightly 98 fixes the camera shutter sound to actually be off when the option is selected.
[Fascinate Android Development] Syndacate:
Awesome.

I didn't even know it didn't work, haha.
[Fascinate Android Development] joshkoss:
nightly 99 was the first build i actually had some stability issues with.

I always wipe data, Every day when i update and test these.

Just reporting for ya. :cool: bring on build 10 :eek::cool::rolleyes:
[Fascinate Android Development] bigwilly90210:
hey so i noticed in the nightly changelog that build 100 brings "fixes for 3 button recovery". i'm flashing this either way, i've been updating via rom manager premium automatically every night just because i have a problem... lol. hope it really does. just curious if anyone had any more information... jt? :P i'll stick with this till that ICS port has radio functions. then i'm sold. android 4.0 is damn near perfect...
[Fascinate Android Development] Syndacate:
JT probably won't respond here, all the major devs have had it with xda and have moved onto rootzwiki.

Active thread is here:

http://rootzwiki.com/topic/1889-nightly-romgrj90-cyanogenmod-7-for-samsung-fascinate-fascinatemtd/
[Fascinate Android Development] mtw4991:
my daughters fascinate can receive mms but not send. is this a common problem?
[Fascinate Android Development] DevinLeFevere:
Not at all. MMS has been fixed for a long time now.
[Fascinate Android Development] mtw4991:
she may have her messaging app s

et to iphone instead of android I'll check thanks
[Fascinate Android Development] bigjobber69:
also try another messaging app...handcent or gosms
[Fascinate Android Development] joshkoss:
When I record video in HD on any of the nightlys I have tried it stutters when is played back.
[Fascinate Android Development] mtw4991:
umm, she is using Handcent. Is there a setting to set it to Android or iPhone there, didn't see one?

Edit: dug thru my Nexus One, she probably has the custom-user-agent in the stock messaging app set to iphone or something else. Will check!
[Fascinate Android Development] Shakes The AssClown:
Joshkoss look on rootzwiki. There is a tutorial to reduce the bitrate and clear up the choppiness.
[Fascinate Android Development] joshkoss:
Thanks... ill check it out.
[Fascinate Android Development] azpirin1:
On build 101.

I noticed major phantom ring with incoming calls all day today. Almost all incoming calls. I think it caused it during the time when I was on wifi. I didn't notice it when I was on 3g. Any thoughts?
[Fascinate Android Development] froalskiner:
I'm trying out this... http://scottlinux.com/2011/08/14/cyanogenmod-cm7-fix-for-choppy-720p-video-recording/

It reduces the bitrate for hd recording
[Fascinate Android Development] joshkoss:
works for me! :cool:
[Fascinate Android Development] mtw4991:
Ok, got the MMS send/receive thing worked out...I think it was her wifi connection constantly connecting/disconnecting. However, she can't send video via Handcent or the stock app without using the Handcent network. Anyone else having issues trying to send video clips using the messaging apps?
[Fascinate Android Development] Schmarvin:
Anyone else having problems with the app market loading? It just stays on the "loading screen" when I try to download apps.
[Fascinate Android Development] sarkozy:
Clear market data.
[Fascinate Android Development] Tone_Capone:
Hello everyone. I just bought and flashed cm7 nightly on the phone. After flashing, usb isn't working at all on the phone. Ideas?
[Fascinate Android Development] bgoodwin:
Nexus drivers?
[Fascinate Android Development] droidstyle:
Shouldnt need them imo. my device works fine with the samsung drivers...
[Fascinate Android Development] Kaik541:
*sigh* CM7 is based on AOSP and will not work with Samsung drivers... install the nexus drivers like the FAQ on the CM wiki states.
[Fascinate Android Development] Syndacate:
No, you have them if it's working.

Yup
[Fascinate Android Development] droidstyle:
I understand that cm7 is aosp... these are the only drivers I have ever used/installed with odin

http://dl.dropbox.com/u/25089906/Generic_CDMA_i500_Showcase_USB_Driver_V1.3.550.0.msi

or are we talking about adb and I missed that part?
[Fascinate Android Development] rock7632:
hi, I was thinking about flashing CM on my sister's Fascinate. Are the nightly's pretty stable for every day use or should I do the 7.1 stable build? I'm running the latest nightly on my Nexus one and its stable and running great. Just thought I'd ask about the Fascinate version. Any major issues that I should know about? Thanks in advance
[Fascinate Android Development] baron4406:
None of the CM7 builds are totally stable IMHO, but if i had to choose I'd go with the nightlies they are much more stable. However with CM7 after about a week running it your phone totally crashes. i woke up this morning to the phone bootlooping for no reason, So I'm deciding what to do. Just make sure you have everything backed up.
[Fascinate Android Development] Schmarvin:
Yea. I normally have the same problem.
[Fascinate Android Development] Syndacate:
You guys are a minority. There's many people including myself who haven't had as much as a hiccup with CM7 as of recent.

Yeah, just go with one of the known stable nightlies (I can attest to 89 running perfectly).

Yeah, but that was when there was Samsung SW on there. Now that you've flashed CM7 the Samsung drivers will no longer interface. Try connecting to it with ADB, it'll fail, same goes for Odin now. If either/both work, then you have the NS drivers installed. They're in the google SDK manager..maybe you accidentally clicked them or something, but it's an easy check.
[Fascinate Android Development] droidstyle:
Before I installed adb lastweek, my pc showed samsung generic driver installed... I used odin and went back to stock from cm7 due to a bootloop. Then I installed adb the next day so if that was to happen again I could reboot recovery thru adb and not have to go all the way back to stock. When setting up adb it left the samusung driver installed and obviously adb would not recognize my device...although odin still worked. Once I manually installed the google driver then both worked instead of just odin. Im trying to find the thread about this subject that stated some may not need the nexus driver when using odin... I infact didnt and was using it that way for a month before installing adb and google nexus driver.

I agree with you about the folks having problems being the minority! So far for me cm7.1 has been very stable. Yea I have had a couple small bugs and one bootloop, but it does not have anymore issues than the eh09/ei20 roms and the performance is better.
[Fascinate Android Development] Syndacate:
Yeah, I don't know much about Odin so it might communicate in a generic way because realistically it only needs to know the commands to flash, which are lower level than the OS, probably on a read-only partition so they can't even change.

Though to use ADB (any kind of straight up communication with the device, this include screenshots and logcat too) you'll need drivers for the OS - so the NS drivers...probably also need them for mass storage (at least to trigger it), but you may not.

Yeah, I'm using ED09 radio (I keep forgetting to flash EC09 back on since I last reverted to stock b/c MIUI ate my phone) with 89 and it's solid as a rock. Makes me a little nervous b/c I keep hearing about people having issues with 9X builds :(.
[Fascinate Android Development] rock7632:
Ok, I'll go with 89 then. Are there any other GB based roms there are more stable then CM7?
[Fascinate Android Development] ncwildcat:
Is there a place I can get 89? The link is gone from the cyanogen buildbot
[Fascinate Android Development] rock7632:
http://download.cyanogenmod.com/get/cm_fascinatemtd_full-89.zip
[Fascinate Android Development] ncwildcat:
Thanks but that link goes to a file not found error...only the latest few seem to work...
[Fascinate Android Development] rock7632:
oh you're right... in that case I need it too. Anyone have a working link?
[Fascinate Android Development] calebv2:
Can someone please post a working link to build 89 that would be most helpfull thank you.
[Fascinate Android Development] rock7632:
No one has 89? in that case I guess I'll just flash 7.1. If someone has 89 please post it. thanks
[Fascinate Android Development] Syndacate:
I'm sure there were some stables after 89. Though I haven't gotten around to trying any of them...crunch time - end of the quarter :(.
[Fascinate Android Development] Syndacate:
Got sleep of death on 89 just now. Running rock solid since it came out - only incident was a random reboot like 2 weeks ago. Either way, unless issue persists I'm not going to fuss, just thought I'd give you guys who are looking to 89 as a rock a heads up.
[Fascinate Android Development] CrucialBT:
Just for the record, nightly 106 has been running stable and fast for me for a number of days now. And while this is a matter of opinion, I love how good my battery has lasted on this nightly. Of course, YMMV
[Fascinate Android Development] joshkoss:
looks like a whole ton of changes in store for nightly 110 it appears to be a RC for 7.2
[Fascinate Android Development] Syndacate:
I just loaded 109, guess I'll see how it goes. I haven't really had any reliability issues in the past, I don't think I'll have any now.

Ah, nice, excited. Hope it turned out better than 7.1 :-\.
[Fascinate Android Development] droidstyle:
^do you really think 7.1 is that bad? Its been good for me.
[Fascinate Android Development] Syndacate:
No, I don't. Though people were reporting much better stability with the nightlies than with the 7.1 stable. That's not supposed to happen >.<.
[Fascinate Android Development] joshkoss:
works great for me.
[Fascinate Android Development] Syndacate:
I can't quote from personal experience, but I heard that some of the nighties were more stable than 7.1. I've had 0 problems with the nightlies. Once in awhile there's a hiccup, but meh, to be expected I suppose, they're few and far between.
[Fascinate Android Development] droidstyle:
Same for cm7.1... I think the people you hear post about stability issues were expecting 7.1 to be perfect. In all actuality its not going to be any better than the latest nightlies because its been revised 100+ times lol.
[Fascinate Android Development] badogg:
Flashed yesterday's nightly on my wife's Fassy yesterday. Everything is running pretty awesome, except every so often it doesn't want to wake up when pressing the power button or the volume rocker buttons (i enabled that in the CM settings). Is this something that is known about the nightlies? Or something funky with my wifes phone?
[Fascinate Android Development] droidstyle:
that's the sleep of death...the best thing to do is use voltage control and disable the 100mhz step and don't undervolt more than -50uv across the board.
[Fascinate Android Development] qw3rty3:
Can someone tell me where I can find old nightlies?

I really need "cm_fascinatemtd_full-98.zip"

Could someone upload it somewhere?

Thanks

qw3rty33@fastmail.cn
[Fascinate Android Development] sam.assad:
http://download.cyanogenmod.com/?device=fascinatemtd
[Fascinate Android Development] HybridByNature:
Currently running 110 with quite a few less battery pulls than on the RC. Every now and again I'll get a random lock-up or something abnormal but so far so good.

It seems to run smoothly and responsive with almost no lag. Reception is as expected but battery life drains about the same as on the RC. (10% / hour).
[Fascinate Android Development] badogg:
You know what I actually think it was, for some reason after flashing the cell reception was pretty much non-existent. Kept showing the cell meter with a little 'x' by it, also getting messages about no data connection. I think it was shutting down or something when it couldn't establish a cell signal. I have ran *228 option 2 and that seems to have settled the signal at my house - which typically has horrible signal, but a -92db signal has still been at least some signal before. I don't think it has slept to death since, even when I checked it this morning after being left alone all night it responded right away when I pressed the power button.
[Fascinate Android Development] droidstyle:
Dont pull your battery...all you need to do is hold vol. up/power at the same time till the phone powers off. This will reboot 99% of all freezes and lockup. this needs to be stickied in bold letters across the top of the page lol.
[Fascinate Android Development] qw3rty3:
I get file not found if I try to download anything older than a week.

I've looked everywhere and can't find nightly 98. Someone must have downloaded it when it was available on that website. Somebody has to have it on their phone.
[Fascinate Android Development] badogg:
Weird. I also checked one of their mirrors: http://goo-inside.me/cm/fascinatemtd/nightly

And it also seems to skip 98 for some reason. I wonder if it was pulled or something?

Why do you need 98 specifically though? why not 99 or the current?
[Fascinate Android Development] joshkoss:
I happen to have 98 on my sd card. you want me to upload it for ya?
[Fascinate Android Development] badogg:
I don't need it, qw3rty3 does though. :)
[Fascinate Android Development] joshkoss:
ok...

Here is nightly 98 uploaded to my ftp on xda :) :cool: