yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] ImDonly1:
When I plug my phone in at night to charge, the screen turns off and it charges fine. But when it is done, I get a battery charged notification and the screen will stay on and not turn off again. I have to go and unplug it from the charger and turn it off.

Is there a way to disable the battery charged notification or make the phone go back to sleep after it is charged? I don't want the screen to stay on all night.
[Fascinate Android Development] sol_671:
Try checking your screen time out. Had the same problem until I looked at screen timeout and was set to 10 min.
[Fascinate Android Development] pospower:
voice to text keyboard

How do I get the keyboard with the microphone that allows voice to text back. I had to go back to 9/28 version of this rom to get it. Is there anyway to install it?
[Fascinate Android Development] ImDonly1:
Its set to 1min but the phone will stay on all night for hours because of the battery full notification.
[Fascinate Android Development] rjskalet:
Cant you turn screen time out off so your screen stays on during a call? I would try that and see if it freezes after a call. Cause then you could determine if its a hardware or software issue. Also as someone else said, a data wipe could never hurt
[Fascinate Android Development] Syndacate:
What does ML and HL stand for?
[Fascinate Android Development] droidstyle:
Medium Leakage, High Leakage= different versions of Glitch Kernal.
[Fascinate Android Development] Syndacate:
Gotcha, thx
[Fascinate Android Development] azpirin1:
Just downloaded latest build 85. Great gps data wifi all works well. Gps instant lock in less than 5 sec.
[Fascinate Android Development] Charm8er:
I updated to 83 the other day and all is well so far. The GPS finally locks pretty quickly.
[Fascinate Android Development] sam.assad:
Hi can any body tell me please is it suppose to say 2.3.7 or it just 2.3.5 cos i flashed #85 1st boot went to about phone it shows 2.3.7 flashed Gapps reboot about phone 2.3.5 and i cant see any differents in performance ..is it just meeeeeeeee
[Fascinate Android Development] DevinLeFevere:
The base is 2.3.7.. the GAPPS are still 2.3.5 as they have not been updated since August. Hopefully we will see an update soon though.

Your Android version should still show 2.3.7 though.
[Fascinate Android Development] sam.assad:
nop it shows 2.3.5 i dont know why

thanks
[Fascinate Android Development] azpirin1:
I am using the latest build 85. It shows 2.3.7

So far, it runs like the final version. Stable.
[Fascinate Android Development] Shakes The AssClown:
Any ideas why I have auto brightness turned off and it cranked all the way down and it still says that 49% is being used by the battery?
[Fascinate Android Development] dug-e-fresh:
Has JT's 10/17 kernal been integrated into the lastest nightlies (86)? Or are there improvements still to be had with flashing it over-top?

def
[Fascinate Android Development] azpirin1:
Question -

Where can I find out about the change log for new builder? I like to know what's been updated on the newer build.

Updating from previous build to new, do I have to delete data and dalvik (? no idea what it is) cache? It's such a hassle to redownload and install new apps and contacts.

I am currently running happily with build 85. What's this new 86 have?

Cheers
[Fascinate Android Development] dallas6672:
Change Log - http://cm-nightlies.appspot.com/?device=fascinatemtd

Most recommend wiping Cache and Dalvik when upgrading to a new nightly.
[Fascinate Android Development] azpirin1:
Ok. So far it's been great with build 85 for past 2 days.

Here is a problem I just ran into which just happened twice on consecutive incoming calls.

For incoming calls, I hear my ringing sounds and another sound which sound like connecting alert ringing sound. When answering this incoming call, I kept hearing this connecting alert sound which I have to ask caller that I will have to call back. Just happend twice first time after installing this build 85.

Before this incoming call, I was browsing through Facebook. Data was on Wifi for your information.

Anyonw have had this problem? Is there a way to resolve this?

Please advice.
[Fascinate Android Development] deafptl4ever:
Same here. I will Nandroid backup this one for sure before upgrading.
[Fascinate Android Development] LovellKid:
Was gonna send a friend JT's 10/17 kernel but my sdcard corrupted all my files. Anyone wanna throw up a link for me? PM if possible...
[Fascinate Android Development] shag_on_e:
I got the 10/16 didn't know about a 10/17.

~~~~There is no spoon~~~~
[Fascinate Android Development] sfobrien:
I think that is what is referred to as the "Phantom Ring". It has been an issue with CM7 for awhile, maybe from the start. I don't think a fix has been figured out yet.
[Fascinate Android Development] DevinLeFevere:
I find it so weird I have yet to ever have a phantom ring (knock on wood). I'm still on 85 and this is probably the most stable rom so far(minus the random application killed issue)
[Fascinate Android Development] exzacklyright:
yeah i got the phantom ring on the stable version.
[Fascinate Android Development] LovellKid:
maybe that's it.. is that the one he threw up on twitter to test gps? Can you toss me a link?
[Fascinate Android Development] sam.assad:
can anybody post their (about the phone software info so i can figure out whats wrong whith mine please ...last installed #85
[Fascinate Android Development] azpirin1:
I also notice my phone not waking up. Before I gone to bed, I plug the charger. This morning I wake up and see my phone won't wake up. Thank god it's Saturday no working day for me. I had to hard pull the battwry to restart. However, four buttons were lit up when I press. But screen won't turn up. Power button no response.

Using build # 85

Anyone experienced similar?
[Fascinate Android Development] phatmhat:
turn off or have blink the notification lights

on build 86.

so how do i make the notification lights blink instead of just staying on forever? or if that's not possible, how do i turn them? i actually did go into the settings and turned off notification led and even notifications. but i still get the lights turning on (you know, home, back, etc).

sorry if this is answered elsewhere, i just cant find it.

oh and i tried bln or blinky or whatever it's called and it said my rom didnt support it.

help. thanks.
[Fascinate Android Development] j555:
Had the same issue, with the phone not responding after charging over night, two nights ago. Pulled the battery and the phone came back up just fine. Haven't had the issue since then.
[Fascinate Android Development] mattw951:
Has anyone else had callers complain about static? I've noticed it only happens when my screen is on. I'm also getting complaints from callers about them echoing when I have them on speaker.

This has happened on the stable and latest nightly with stock and glitch kernels.
[Fascinate Android Development] baron4406:
I'm on build 83 after the "stable" build totally crashed my phone. This build has the same problem of data dropouts like the stable build did, its very frustrating having to toggle airplane mod 20 times a day. Think its the ED05 radio?
[Fascinate Android Development] Tkun:
I'm currently on build 85 with the built-in kernel, but I don't think either has to do with my problem.

The official Facebook app is apparently using 45 percent of my battery, I'm not syncing anything nor having it refresh automatically, so is my phone the only one suffering this problem, or is everyone else who has the app also experiencing it?
[Fascinate Android Development] MattRussNC:
Its not the ed05 radio. I went back to stock dl09 and reflashed to nighlty keeping the radio dl09 and still have the data drop out issues.

Oh running jts included kern, but also had the same results with glitch.
[Fascinate Android Development] baron4406:
Ok I might reflash the EB01 radio then that radio gave me the best 3G performance of anything
[Fascinate Android Development] Syndacate:
You have to go into your profile and disable it there.

I'm on VGB at the moment so I can't check, but IIRC it's under settings, and I think profiles is a menu off of that, it might be under CM7 settings though.

Once in there there's a setting to disable it...sorry I can't give you more detail.

Known as the sleep of death, currently a problem on all GB AOSP phones ROMS as far as I know, not just a CM7 problem.
[Fascinate Android Development] baron4406:
FYI- even with a change of radio the data dropouts are still there. Bummer.
[Fascinate Android Development] chopper the dog:
You need to do this. http://xdaforums.com/showthread.php?t=1051543

good day.
[Fascinate Android Development] baron4406:
Yes I know about the DMU Reset or ESN swap however this only happens on the latest CM7 builds. Never happens on stock or Powerwashed ROMs, Want to report this to try to help out the CM7 community
[Fascinate Android Development] azpirin1:
Anyone using the latest build 89? How is it? I read the change log but it is not in terms that I understand.

I am currently on build 85. Only issue I have with, phantom ring and sleep of death. I think that's all I have so far which is far better than when I was on the stock rom.

What build you guys are using?
[Fascinate Android Development] Justice8908:
Ok I'm on build 86 I think and I have a quick question....does anyone know about the issues with the video apps like NFL mobile? I go to pull up the live stream of NFL network and it does one of two things, it either just sits there and says it's loading or it will act like it's about to play then return me to the home screen.

The only way I know of to get it to work is to return to update 35 on sundays for NFL red zone and then flash back to the latest nightly where NFL Mobile doesn't work again.

Does anyone know of a fix or is anyone working on a fix for this?
[Fascinate Android Development] Justice8908:
I've also had somewhat of a problem with push notifications from apps like Score Mobile and Facebook.
[Fascinate Android Development] DevinLeFevere:
Facebook has never really worked. EVER. You can try Freindcaster.
[Fascinate Android Development] Syndacate:
Yeah, sometimes ESN swap doesn't fix as much as some people think.

I just lost data with the latest VGB, had to reboot to get it back (I'm sure I could have used airplane mode, but I didn't, that's equally as annoying, though).

It's definitely an issue with a few selected AOSP ROMs. I don't believe the issue exists on MIUI, either, but I could be wrong.

Also, I have my suspicions (though no actual proof to back it up) that the data issue has something to do with recovering from a very low signal. The problem began for me at the last place I was working, very very very Verizon unfriendly, 0-1 bar, data always would cut, then the problem went away for a bit, but Sunday, right before I saw this ugly bug again for the first time in a couple of months, I was in a place that had the same kind of reception...and the same thing happened. Many have claimed BS to what I've said, but I highly doubt this is the case, I definitely think there is something wrong with selected AOSP ROMs that causes this issue that an ESN swap will not fix.
[Fascinate Android Development] mattw951:
I am on build 86, does anyone know how to fix the video recording? I keeps repeating itself in short bursts (sorry thats the best I know how to describe it)
[Fascinate Android Development] davwman:
Is it possible to install cm7 with the blue voodoo recovery?
[Fascinate Android Development] Justice8908:
So does anyone know how to fix the NFL mobile problem?
[Fascinate Android Development] Syndacate:
If you're talking about clockwork mod (ie. when you reboot into recovery mode), that'll get installed with CM7. You can get clockwork recovery mod for CM7 in order to install CM7, you can download it here, then flash it with heimdall or Odin.

NFL?

---------- Post added at 11:37 AM ---------- Previous post was at 11:07 AM ----------

I'm using 89 with the ED05 radio (been too lazy to re-flash, but will flash EC09), stable & good, I didn't bother to look at the change log like I did any of the other change logs, don't even know where they are for the nightlies.

Yeah, the data drop isn't relate to the radio and I don't think it's related to the kernel, it's a GB issue....possibly only AOSP ROMs but I haven't even used a non-AOSP GB ROM.

No, it's not the radio, probably not the kernel, either. Try pushing over build 89 and the kernel cleaner script, doing a factory reset, clean the kernel, clean cache, clean dalvik, clean battery, run kernel cleaner script, install nightly 89, then run it. See if issue persists...though if you're in a data with bad coverage for awhile it just might :-\.

NOTE:

Yes, I'm well aware of the heavy redundancy in the amount of clearing I told you to do.

I'm running 89 and it says 2.3.7.

EDIT:

I'm running gapps 2.3.5, though.
[Fascinate Android Development] Justice8908:
Yeah, the NFL mobile app, the one that lets you watch NFL network and NFL red zone on your phone, after build 35 the video hasn't been working on it. Even on the stable build I still can't watch anything through that app. It will either freeze on the loading screen or close out and return me to the home screen when I try to watch a video.

A MIUI dev tried to come up with a fix on CM7 because he had fixed the same problem on MIUI but it didn't work. Apoarently there's other video apps like Verizon Video that aren't working either
[Fascinate Android Development] Jazz848:
You can haz changelogs: http://cm-nightlies.appspot.com/?device=fascinatemtd

Edit: Alright, so apparently the API is borked at the moment, but that's where you'll normally find all the CM7 change logs.
[Fascinate Android Development] Syndacate:
Ah, gotcha, don't know anything about that - sorry :(.

Yeah, it just hangs for now, but thanks, I'll keep an eye on it when I have some free time.
[Fascinate Android Development] Justice8908:
No worries man, I know a few people that this would be a deal breaker for them on CM7, I love it personally but this NFL mobile bug is a little annoying.

If you want to check it out and see what it might be please do, someone told me that it might be a kernel issue. The last nightly it worked on was nightly 35 which was the one before JT's kernel was added. Glitch Kernel isn't getting it to work also
[Fascinate Android Development] Syndacate:
Meh, too bogged down with school work, unfortunately, to look at community projects in depth :(.

What was CM7 using beforehand?
[Fascinate Android Development] Justice8908:
Honestly I don't remember ill have to flash back and look at it
[Fascinate Android Development] sol_671:
Is the sdcard issue been fixed? Like corrupting 32gb speed 4 microsds. I had these problems on the stable release not sure if its still there. I'm on a touchwiz base rom at the moment and really hate to try to go back to a mtd rom and setup everything (because of the hassle) and find out that its still there and end up flashing back to touchwiz base rom. Thanks..

Btw is the nightlies now more stable than the CM 7.1 stable release?
[Fascinate Android Development] SmokeyDP:
Anyone else have a problem using call waiting on bluetooth? The phone beeps when the second call comes in, but the screen gets overlayed with the 'current call' screen with the 'incoming call' screen on top and you can't do anything on the phone until the 2nd caller stops calling you. You can't even 'ignore' the call.
[Fascinate Android Development] Syndacate:
As far as anybody knows, the SD card bug has been fixed a mad long time ago. It hasn't resurfaced. The only problem is once every couple of months somebody's SD card will die (as they normally do), and they'll flip **** and cause a fake scare saying the bug is back. It was fixed by JT, apparently somebody added code to make the SD card work better for another phone under CM7.

As for "stable" - I don't know, I haven't tried the 'stable' build, but the nightlies are perfectly stable as far as I can tell. Only hiccup I had was for some odd reason last night it restarted, though this is an oddity as far as I can tell, I haven't seen it do this until last night.
[Fascinate Android Development] droidstyle:
the cm7.1 is very stable if you take the time and do a full wipe then reflash. I believe alot of folks problems is beig lazy and not following the proper steps, and then they jump on here *****ing about how something don't work lol. The only issue I have is once in awhile I get the sleep of death or "phone coma", and only have had 1 data drop in 2weeks on cm7.1. I find it to be far more stable than the eh09 roms, with the constant reboots/lag/freezes/browser always closes...jmo
[Fascinate Android Development] Syndacate:
Yeah, I haven't had sleep of death with this ROM, but I know it's still an issue, seemingly very rare, though.

It's stable, even the nightlies are.
[Fascinate Android Development] azpirin1:
Which build?
[Fascinate Android Development] Syndacate:
If you were talking to me I was mixed up, I was thinking of the VGB 8/29/11. Took a slight vacation there to try it again in between CM7 nightlies - gotta keep up with how the other ROMs are doing =).

I'll modify my posts to reflect that.
[Fascinate Android Development] sol_671:
I ran CM 7.1 for a week,I know how stable it was, but if I remember correctly we were in the same boat with the sd card issue and you had to format yours multiple times, my 16gb never had an issue with it just my 32gb and would really want to use it. So I'm wondering if the nighties are better than the stable release, if they're just the same or less then I'll just flash the stable release and try Jt's newest kernel or glitches v13 since I haven't tried those yet :p
[Fascinate Android Development] sol_671:
I knew sd bug was fixed long ago, it's why I decided to go to the late cm nighties then back to touchwiz then to CM7.1 stable then sd card gets corrupted by the end of the day, it just corrupts it or says sd card damage, it doesn't fry it like back in the day. Can't say my sd card is the issue because I'm using it right now with touchwiz for 3 Weeks now. And yes I've formatted it like 6 times in one day, just to get it to work like my 16gb. Well thanks for the reply sounds like it's all good now,btw how much gigabyte of sd are you using for cm7 nighties?
[Fascinate Android Development] Holliday:
Could it be an issue with the file system? Don't TW roms use RFS still? Just trying to find other possible variables.
[Fascinate Android Development] Syndacate:
Ah, that may be a different deal, I haven't dabbled there. I'm using the SD card given to me by Verizon (16GB?) - I don't know how the others deal with it, sorry.
[Fascinate Android Development] sol_671:
Yeah my 16GB Samsung micro sd has no problems with CM7, but when I put in my 32gb SanDisk it would either run for a while before reporting it's damage or corrupted or just says damage after a reboot, then when I put in my 16gb it corrupts it too, lol. Anybody here running a 32GB without a problem? Maybe I'll just try it tonight since I'm off tomorrow from work. All day flashing while drinking corona, lol.
[Fascinate Android Development] sol_671:
Is that question for me? If it is then I say I have no idea, I highly doubt it but I'm using ext4 not rfs.
[Fascinate Android Development] froalskiner:
I just went from the 7.1 stable to nightlies and all last night I was dealing with a mountain of force close windows and Disk I/O messages on the screen. I know the issue was supposed to be fixed but is the best resolution to backup and format the SD card or do I need to reflash?
[Fascinate Android Development] Syndacate:
You did clear your caches and run the kernel clean script before flashing, right?
[Fascinate Android Development] froalskiner:
I cleared my cache, dalvik cache, and did a factory reset but didn't read anything about a cleaning script in the upgrade page on the wiki. Can you point me in the right direction?

EDIT: Is this what you are talking about? http://xdaforums.com/showthread.php?t=1166954 I'm going to try that now...wipe, run this, then reflash the nightly.
[Fascinate Android Development] Syndacate:
Doing a factory reset is mega overkill. If you did that, it should be fine. If you were still getting error messages I don't know what the problem is. You're getting all these FC's and IO errors with the 89 nightly?

Just factory reset, then install that without booting.
[Fascinate Android Development] froalskiner:
I tried the 91 last night then today I tried switching to 92. It looks like they may be the same however. I'm still getting FC's although it's nowhere near as bad as yesterday.
[Fascinate Android Development] DevinLeFevere:
Something Is very wrong then. Nightlies is stable as a damn rock.
[Fascinate Android Development] Syndacate:
Yeah, what Devin said, I have no idea what's wrong.

The only thing I can suggest is using the old partition map, go back to the OEM firmware from Verizon (DL09 IIRC), get the OTA Verizon updates, then flash CWM fixed for CM7, then do factory reset, and install CM7 from there.

~.5-1 hour
[Fascinate Android Development] froalskiner:
I made a backup after I switched to 7.1 Stable so I restored and tested it out the rest of the afternoon yesterday until right now and I'm getting zero FC's. When I was trying to flash CM7.1 originally I tried the ROM Manager method so I flashed that recovery. I didn't realize it until last night but I apparently have 2 recoveries. 4.x if I 3 finger to restore mode and 5.x if I go to restore using the menu. I don't remember if I 3 fingered into 4.x or rebooted into 5.x to update to nightlies...

I'm guessing this may have something to do with the issue I was having. Also when I went from stable to nightly I restored both user apps/data as well as system data using Titanium. I suppose either of these problems could have contributed to the problem.

I'm on ED05 if that makes a difference.
[Fascinate Android Development] dr_w:
Nightly 93 FYI

FYI: I'm running the solid, arguably stable nightly 93.

3 issues so far.

1. The swype keyboard doesnt stay after a reboot. I have to reactivate it every single time.

2. The wallpaper wont stay either, I have to reactivate it everytime I reboot. Defaults to the nexus wallpaper.

3. Just now, went into boot loop on its own. First time in about 698 ROM installs i've done. Strange.
[Fascinate Android Development] Syndacate:
ED05 doesn't make a difference (radio version).

You're never supposed to use 3-finger recovery on this for that reason - it'll send you into the wrong backup. It's very possible things were corrupted due to that. So maybe see how things work out now that it's fuxed.

Yeah, NEVER do 3-finger recovery. If you get sleep-of-death, battery pull. Right now I've only been running 57 hours but in said 57 hours I haven't had as single hiccup. The post above mine makes me iffy as to whether I want to go to the latest or not, running 89 at the moment. Typically the nightlies are rock stable.
[Fascinate Android Development] raymechanic:
That is odd. I did the standard cache/dalvick wipes on 93 and no problems.
[Fascinate Android Development] dr_w:
It is odd. The ironic thing is, is I've never done the delvic/cache wipe thing til this build. Now I have problems. Historically I've just installed from SD Card.
[Fascinate Android Development] raymechanic:
Silly question did you try fixing permissions thru CWM