yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] Dan Ang:
If it comes across as having "attitude ****," it wasn't intentional, and this certainly isn't meant to be asking the dev's for more. They have done a great deal, and I've even donated to JT at one point, he's a miracle worker.

I assure you, I'm not a dev or expert by any stretch of the imagination, but I know what I'm doing. I've flashed tons of roms, kernels, successfuly got to CM7 multiple times and back with no trouble in the process.

My exasperation is with the phone in general. Early on it was a long wait for a decent froyo leak, months after anyone on any respectable phone got it. And even once we had that, there were still ridiculous problems, random reboots, terrible battery life, and that's obviously not the dev's faults, they do what they can.

Like I said, my phone, on CM7, was having phantom softkey presses, terrible service cutting out, keyboards popping up, and after literally doing no modifications to the phone in at least a week, I woke up to it being in a bootloop that I could not get out of.

I'm not asking for more from the dev's, it seems like a ton of people have been having much more stable experiences than me. I just wish I could have a completely stable, relatively problem-free experience for a period of time. Hell, when I originally had CM7 it was great. Maybe I screwed up something recently to give me these problems, who knows. I'll probably go back from stock to CM7 or AOSP variety soon.

Anyway, yeah, this is just a long winded way of saying that I really dislike samsung and wish I had gone with the incredible.
[Fascinate Android Development] Jazz848:
That being the case, it gives the wrong impression to post that sort of general dissatisfaction in a specific rom thread. If you have any info that could help with troubleshooting, though, I'm sure someone (myself included) would be happy to assist where able ;)
[Fascinate Android Development] bigjobber69:
+1 my friend +1
[Fascinate Android Development] xgunther:
How do we turn off the backlight notifications for text messages? It is driving me NUTS.
[Fascinate Android Development] ckrenek23:
Go into cm settings/profiles and make sure you turn it off under you current profile. Hope this helps. I personally like it so I don't have to turn the screen on to check for messages and kill battery faster but it's not for everyone.
[Fascinate Android Development] anon_72:
Thanks. I have the nitrality app that changes my dpi, I resized back to stock and was able to download the app I needed.
[Fascinate Android Development] Azuma73:
My girlfriends Fascinate does the same thing in the Market, apps run fine but cannot update some of 'em? I don't get it? I tried different versions of the Market and even tried activating on my old Ally then re-activating her Fascinate to change ESN or whatever? Didn't do anything!! I'd like to know more about this, and how to fix it. I have hers set up pretty much the same as mine and I've never encountered this issue?:confused:
[Fascinate Android Development] Jazz848:
Have you tried clearing both data and cache for the market app? Also, would any of those missing apps happen to reside on the SD?
[Fascinate Android Development] Azuma73:
Actually, yeah, I did clear data/cache from market app. Even un-installed/re-installed. I did make sure to move them back to internal, if needed. It's not that they're not showing up, it just says "not compatible wit this device". They'll run fine, market just won't allow them to be updated to current versions??

Thanks man!
[Fascinate Android Development] Jazz848:
Is she using CM7? I only ask for sake of thread relevance; if she's not, we may want to take this to PM to avoid confusion.
[Fascinate Android Development] Azuma73:
Yeah, she is on build#57 I think? And yeah, you're right we should move this! My bad!:rolleyes:

OOps, she is on CM7 so I guess we don't have to???:rolleyes:
[Fascinate Android Development] Dan Ang:
Well it didn't really start that way, I was really kind of asking for help, but in a terrible, whiny way.

So let me start again. I am currently on stock. If I go to CM7 now, will I get a completely stable experience? What do I need to do to make sure that I do? Or, if I'm for more stability over other features, should I just go for an AOSP rom like pool party?
[Fascinate Android Development] Jazz848:
While it's entirely possible for you to have a stable experience with CM7, it's essential to remember that our phone doesn't yet have a release candidate; nightlies are pretty much beta by nature and mtd in general isn't native to the Fascinate (we have jt to thank for busting his arse to give us an excellent port, though). Lots of people are quite happy with nightlies, but that whole scene is for testing by its own nature. Lots of folks have found individual nightly builds that happen to suit their "daily driver" needs, but it takes trial and error.

There's a lot more that could be said, but based on what you're looking for, you should probably wait until we at least get an RC (ETA: when it's done). If consistent stability is THE driving factor in your choice, you may want to stick with a TW rom built from the source of an officially-released build such as ED05 (as opposed to a leak such as EC09). In it's current phase of development, though, CM7 probably isn't what you're looking for.
[Fascinate Android Development] Dan Ang:
I can deal with bugs, I mean sometimes I don't notice certain things. Honestly the only thing that's a dealbreaker is the keyboard popping up, and truthfully, it seemed like I was the only person who was consistently having that problem (other people said nightlies would fix the problem for them), so I probably did something wrong. Obviously automatic reboot is bad too, but that might always happen.
[Fascinate Android Development] fstbusa:
I currently run a nightly build of CM7 with the glitch kernel and although there are a couple minor things I don't like, its still the fastest setup I've run.

I'm undervolting insane amounts with the same stability as if I didn't and getting decent battery life.

My only "gripe"(if you could even call it that) that ever since froyo was leaked, battery life has sucked compared to 2.1. Guess if thats my only issue, I can live with it.
[Fascinate Android Development] Jazz848:
Have you tried installing and updating the apps in question on yours as well? I'm curious to see if the exact problem can be duplicated on a different phone of the same model.
[Fascinate Android Development] isaacws:
I just updated to CM7 build #67. This is so awesome guys! Thanks to the devs with all the hard work! I love how well it works! And the video chat working with the camera is amazing! I had searched to see if the new gtalk with video worked with the fascinate camera but didn't find any info. It is a nice surprise that it does!

What is the best radio to use with this set up? I am on EB01 but was thinking of changing to EC09.

Thanks again guys!
[Fascinate Android Development] exzacklyright:
Correct me if I'm wrong but when you flash these nightlies you have to also flash glitch kernel again, gapps, and redo all your voltage settings?
[Fascinate Android Development] Syndacate:
No, gapps, just like every other app, is preserved.

As for flashign glitch, last I checked, I thought CM7 didn't have a kernel, but I could be wrong, so you shouldn't have to flash glitch either.

Not sure about voltage, but seeing as you don't have to clear any caches, I'm going to assume that includes voltage settings. I didn't mod the voltage settings of my phone since I came to CM7 nightlies, though :-\.

---------- Post added at 12:31 PM ---------- Previous post was at 12:30 PM ----------

I'm using EC09, no problems here.
[Fascinate Android Development] Jazz848:
JT's kernel is built into CM7. Just an FYI.
[Fascinate Android Development] sfobrien:
Installed 68 yesterday, best yet for my device. I also went from EC09 to ED05 radio just to see if there was any difference, don't see any. FYI
[Fascinate Android Development] shag_on_e:
No this isn't the case. Even if you aren't wiping data, the packaged kernel will overwrite any previous kernel. Since wiping data/cache/dalvik cache is known as standard procedure for proper flashing, you will have to flash gapps again. It's definitely worth it because it eliminates problems due to leftover files and modules. I change roms constantly and wipe every time. Takes like twenty minutes for a complete fresh install.

~~~~There is no spoon~~~~
[Fascinate Android Development] Syndacate:
Ah, okay, good. I like his kernel.

I wipe every time I change ROMs too, but when I'm going from one nightly to the next I do not. I don't have 20-30 minutes every day to wipe and start from the ground up to keep up with the nightlies. I was told by somebody around IRC that you don't need to clear the data/cache/dalvik for flashing a nightly over a previous nightly, and I haven't experienced any problems by not doing so.

Though I'm glad it comes with the updated kernel. I think I was thinking of the radio, which I believe it doesn't have bundled in it - just a fake (so your old one is retained).

Are you having the volume problems with EC09?

I had problems with the EC09 radio on nightly like 15..but the problem was fixed. Perhaps try clearing data/dalvik/cache and install from the ground up?
[Fascinate Android Development] shag_on_e:
Right on, as long as it works all is good. :-D

~~~~There is no spoon~~~~
[Fascinate Android Development] euklid:
Does the latest nightly have voodoo in it like on nexus s??
[Fascinate Android Development] mirrinigma:
Any news on hardware video decoding in the past 50 builds? For high profile h264 and DivX/xvid.
[Fascinate Android Development] erivnocmc:
not works:(
[Fascinate Android Development] fstbusa:
what voodoo are you referring? Sound, Color, lagfix??

Lagfix is not required because of the MTD file system.
[Fascinate Android Development] dr_w:
anyone try build 70 yet?
[Fascinate Android Development] saps:
70:confused: did we skip 69 ....that's not good to skip 69 :p
[Fascinate Android Development] dragonzsoul:
i'm on build 57 (old i know, but i don't like to run that close to the bleeding edge :P) with the latest (AFAIK) glitch kernel. i've been noticing my 3G cutting out more and more (several times a day). anyone else notice an increase with their phones? with that said, does the latest nightly have any major issues and does it work with the glitch kernel? my phone will lock up probably once or twice a day, but it's something i deal with.
[Fascinate Android Development] sarkozy:
70 is running fine with Glitch V12.
[Fascinate Android Development] vlucchetti:
70 is running fine without Glitch. :)
[Fascinate Android Development] fifreak:
Does anyone have issues with /datadata filling up? This has happened to me on a few roms, most recently the 9/24 build w/glitch v12. The symptom I see is pretty much everything force clsoing. Usually i just adb shell and kill some stuff in that directory. But why does this keep happening to me?
[Fascinate Android Development] chopper the dog:
http://rootzwiki.com/showthread.php?6625-Problems-with-datadata-Causing-force-closes-for-Google-apps.

good day.
[Fascinate Android Development] Syndacate:
I've seen some issues on 68 that weren't on 35.

- Once I got the random start-up screen while running without reboot issue

- Once messages fc'ed

Thought there was something else but I can't recall atm.
[Fascinate Android Development] Mod57:
I haven't ran into this problem with my mesmerize yet but my work phone is a HTC Desire which has very limited data memory. Not sure if this will work on the Fascinatile because I haven't tried it but you may try S2E which can be found in the market. You will need to put a partition on your SD card and that is where your data is stored. How it works is through script it allows the data in your SD partition to think it's internal memory. The bigger your partition the more apps you can install. A fast SD would be better but I used the factory one on my HTC and it worked fine. I did format the partition ext4. This may not be the right solution but may be worth a try if all else fails.
[Fascinate Android Development] Sorvisa:
New nightly 70 seems to be working good. I've had a problem with no GPS

lock since 65 and I still have the problem now. Any suggestions ?
[Fascinate Android Development] Syndacate:
I got a lock on 68. Took quite a bit, but it happened.
[Fascinate Android Development] isaacws:
Has anyone had a problem with the camera on cm7? The shutter takes a good second to fire and the video camera introduces stutter into the video. The stutter is almost more like a reverse effect where the frame goes forward then back. Anybody else had this issue? Can a different camera.apk be installed?
[Fascinate Android Development] :
The MIUI camera can be installed. You will have to find it yourself, im to lazy to look for it. Sorry...
[Fascinate Android Development] Syndacate:
You using the hold to focus feature? I use that and it works great.
[Fascinate Android Development] erivnocmc:
Really stable?
[Fascinate Android Development] dr_w:
Why? You don't think so?
[Fascinate Android Development] sam.assad:
any body knows what going on in CM7 site its acting funny today
[Fascinate Android Development] erivnocmc:
Again, missed calls.
[Fascinate Android Development] Skrazz:
This is why.
[Fascinate Android Development] exzacklyright:
stable o.O
[Fascinate Android Development] Syndacate:
Oh boy, never seen a stable build there before !! O.O

I might try that, right now I'm trying MIUI and I'm <3'ing it, guess I'll have to see how my MIUI experience turns out to decide whether or not to go back to CM7.
[Fascinate Android Development] Azuma73:
Whoa, is that an "official" CM7 update? That'd be quite nice!!:eek:
[Fascinate Android Development] DevinLeFevere:
Its on Rom Manager. Guess I'll be leaving nightlies!
[Fascinate Android Development] Azuma73:
Any special install instructions needed, wipes and wutnot? Di I need to flash GAPPS? Can I still flash Glitch like before?
[Fascinate Android Development] Mikes30000:
Anyone try build #4 yet?
[Fascinate Android Development] speedingcheetah:
just flashed #4...don't notice anything different from build 3...so far

EDIt: Yep...same bugs as before....no signal bars, in-call volume touchy, data and incoming calls seem tad more stable...maybe...wasn't expecting much though..seems to be a little more free memory than before..

The color is a tad warm on stock CM...whites aren't pure white...but that maybe from the absence of Voodoo color and all the extra stuff...

EDIT: phantom ring strikes again..and again...hope they fix that soon, getting annoying..

I was just looking through CM downloads...man...some phones are over 150 nightly builds without an RC or Stable release...I get the feeling it will be a long while before we see major progress...sigh..hopefully I'm wrong..
[Fascinate Android Development] speedingcheetah:
DSP Mananger???

What is DSP manager...is it necessary to have running in the background all the time..I have tried using its settings to adjust audio...but doesn't do anything...so I just used Bloat Freezer to Freeze app..may be it will be functional in future build..
[Fascinate Android Development] Toddw:
No phantom rings yet. GPS ok. No MMS still, no signal bars. Volume seems OK. Wifi is working. More later...
[Fascinate Android Development] ecsnead69:
Latest stable build?

The thread for the last stable build was closed and had the link to this one... is the 7/17 build the latest stable build with everything working? I really want to try this rom but I don't want the experimental builds, I need my phone to work fully...

Thanks....
[Fascinate Android Development] djlim4:
7/17 is probably more stable than some of the nightlies, but if you want everything working, stick to comrom

don't expect to come to any of the GB builds and have everything working like it did on froyo.

everyone seems to have different types of issues... i went back and forth btwn EF, CM7, and OMFGB, but i'm fortunate to not have had the major bugs affect my day to day needs.

as far as stable build of nightlies go, i was on CM7 for my nook color for a while now, and back in april/may it seemed like there was a release candidate or stable build coming out every week if not more.

What i'm trying to say is, and seriously, no offense to anyone, but i check these threads much less frequently than i used to when i first got my phone and it seems like people are complaining about bugs and whatnot a LOT more these days

I dunno when everyone got their phones, but for those of us that have had it from the start, or at least the beginning of the year, it's a miracle that 2.3 is actually available

there was a time when we weren't even sure a fully stable Froyo would be available. So just be happy we're even getting development still and deal with it or just move back to what works
[Fascinate Android Development] JuniorBevins:
...yes, its stable and everything works. Call volume is a little low bit, who calls anyone anymore ;)

I would also recomend glitch's kernel as well.
[Fascinate Android Development] Bubbadogg14:
Imnuts 7/26 version is the latest stable build w everything minus signal bars wrkin cuz its 2.3.5 I reverted back 2 it for now
[Fascinate Android Development] ecsnead69:
Do the signal bars work in the 7/17 build?
[Fascinate Android Development] gunm3tal:
It improves sound quality coming out of your headset, bluetooth., and speakers.

I don't think it needs to run if you're not using it.
[Fascinate Android Development] Mikes30000:
Yes they do work
[Fascinate Android Development] speedfrk:
I think 7/17 is more stable with more bells and whistles than ComRom. The only thing I miss is being able to dial a few letters and it pull up the names of people. Don't know what that is called but it is a must have feature.
[Fascinate Android Development] mwestendorf:
have you played around with the lock screen gestures? That might work for you

Sent from my I500
[Fascinate Android Development] doctorj1:
download GO contacts and use that as your primary contacts app and dialer, it has this feature and works great with CM7, i was missing the same thing as well as having the letters on the side when you open the contact list so you can jump to say S or T without scrolling the whole way or having to grab the slider on the side
[Fascinate Android Development] xactnode:
Or you can simply use the standard aosp search function in contacts.
[Fascinate Android Development] ssewk2x:
I dunno, man. My cm7 build has never actually crashed. I get zero fc's, No random reboots, no bluetooth wonkiness which plagued me on comm rom, crazy fast performance, and pretty damn good battery life.

to each his own, but I'd put cm7 above the comm rom in terms of suitabilitu as a daily driver. And that's saying a lot, because comm rom is awesome in its own right, too.
[Fascinate Android Development] Bubbadogg14:
The nighties may not be daily drivers yet but 7/17 n 7/26 sure is
[Fascinate Android Development] StDevious:
that's def saying someting man, good for you. When I tried CM7 7/17, it worked fine for an hour, then I started getting all sorts of FCs
[Fascinate Android Development] Toddw:
I went back to 7/17 because of no MMS and I did start getting the dreaded phantom ring. I'll wait for a while til mms is fixed.
[Fascinate Android Development] mwestendorf:
That is what I was trying to get across, if people want a daily driver stick with the stable releases not ones built by a bot every night.

It seems to me that not everyone grasps the concept of a nightly, they seem to think these releases are stable like the ones jt was updating periodically on his old thread.

a nightly may actually break more than it fixes in some cases that's just the way it goes with development.

Sent from my I500
[Fascinate Android Development] Syndacate:
It's most likely basically a nightly that has been determined stable enough for a stable build. I doubt any of the structure was changed for a stable build, kind of defeats the purpose, the Glitch kernel should work fine. Will probably need to flash gapps, you could probably get away with wiping the big three then flashing, but I would clear it.

I haven't tried glitch, I heard it's really good, but I <3 JT's kernel, currently using that with MIUI (actually I think it came with MIUI? Or else I'm not sure how else it got on my phone >.<). At some point I'll have to give glitch a whirl.

EDIT:

Just do a CWM backup before flashing, it if goes boom - restore =).
[Fascinate Android Development] Glocjt:
I went from nightly #57 to 7.1.0 (flashed the latest Glitch beta on top of it) last night, and no issues so far. Just wiped cache and dalvik, and everything went smoothly.
[Fascinate Android Development] exzacklyright:
Reboot from menu into cwm. Wipe. Flash ROM. Boot. Flash kernel. Flash gapps. That's what I do

Sent from E.T.
[Fascinate Android Development] Syndacate:
Well that will definitely work, the question is whether or not a wipe is necessary - not everybody wants to install all their settings and apps again.

@ People wondering:

You should be perfectly fine if you just clear dalvik, regular cache, and battery cache.

You can most likely get away with:

- Reboot into CWM

- Clear cache/dalvik/battery stats (or use the kernel cleaning script)

- Install CM7 Stable from Zip

- Enjoy
[Fascinate Android Development] saps:
Agreed though when in a doubt a data wipe will always make things groovy.

I had to do the data wipe since I was on VGB this morning before the 7.1
[Fascinate Android Development] Syndacate:
Yeah, if you're changing OS's I'd say wipe data, but from one nightly to the next, or nightly to stable or vice versa between one, you typically won't.

Hate losing all my apps and settings, lol.
[Fascinate Android Development] fstbusa:
if you're just upgrading versions, you can do a nandroid and wipe 3 and try restoring data from advanced restore and it will usually restore all your apps with your data without issues.
[Fascinate Android Development] Syndacate:
If you're upgrading versions, you don't need to wipe/restore anything IMO.
[Fascinate Android Development] fstbusa:
I always like to be safe.... :)

Sent from my SCH-I500
[Fascinate Android Development] geokhentix:
Just installed stable CM7 w/ Latest Glitch LL kernel, my proximity sensor don't work at all. After a call, I have to pull my battery to get my screen back on. I searched and saw people reporting working sensors. Any takers?
[Fascinate Android Development] Kaik541:
ask in the glitch thread, as it has nothing to do with this ROM now that you're off stock kernel.
[Fascinate Android Development] dallas6672:
Have you tried a different leakage or a reflash?
[Fascinate Android Development] geokhentix:
It actually does it with JT's kernel as well. :(

I have not tried a different leakage, but I've reflashed to stock, to runnymede, which also does it. I'm running out of ideas.
[Fascinate Android Development] dallas6672:
HL is the most common with the Fascinate. Have you tried wiping Data, Cache, and Dalvik?
[Fascinate Android Development] geokhentix:
Oh yes...more times than I've eaten since new years. :( I tried ML AND HL, nothing. Having to battery pull after a call is annoying...Doesn't matter if i'm on stock kernel, or glitches. I'm clueless...Doesn't do it on 2.2 though.
[Fascinate Android Development] dallas6672:
Are you undervolting/overclocking? Does your screen shut off when you hold it to your ear in a call and then not come back on or does it not shut off at all? I don't know if stock/jt's kernel has screen state scaling or not but Glitch's does. So if your screen is shutting off in a call but not coming back on, maybe try booting into recovery while in Glitch's kernel and go to GLITCH>Configure screenstate scaling and disable or change it to something other than conservative (conservative is default).