621 replies to this topic

[Neezy13]

aliastx, on 09 October 2011 - 06:16 PM, said:

Did anyone try test calling 911? I think that is a fairly critical issue. Can people please try and reply to the thread?

You do realize that test calling 911 is illegal in some areas, right? You should not tie up 911 lines with non-emergencies.

[voicebyjack]

theyurtingyeti, on 08 October 2011 - 08:34 PM, said:

I had the same issue after #136 I believe. I had to go into the app and clear data. Then it started working again.

Thanks, that worked. I tried downloading a newer (Honeycomb) camera, which worked, but lacked the "wide" feature of CM7's Gingerbread camera.

[illustrator11]

earendil1979, on 06 October 2011 - 08:10 PM, said:

I've got a question regarding music playback stuttering or skipping when the screen is shut off. After a few seconds to a minute or two it will stop. I've tried several music players and it appears to happen regardless of app in use. I'm running nightly #140 now and this behavior has been going on for a few months through several nightlies. Not sure if anyone else can replicate the issue or not. It's obviously a minor issue and an annoyance rather than a major functionality issue but I'd like to figure out why it's happening.

If anyone can replicate or has any ideas on troubleshooting I'd appreciate it. Thanks!

i had the same issue and figured it might have been fixed by #144. But what a mess.. things are force closing left and right, browser  pretty  much non functional, facebook locked my phone twice after force closing.  constant error messages popping up left and right..

so i went back to #141. wiped the dalvik cache, cache, uninstalled google music and double twist and youtube (because it was giving me the same trouble as the music apps) and reinstalled all of them. seems to be working fine now.

[aliastx]

Neezy13, on 09 October 2011 - 11:21 PM, said:

You do realize that test calling 911 is illegal in some areas, right? You should not tie up 911 lines with non-emergencies.

If you have a better way to test to see if Cyanogen Mod on T-Mobile leaves users unable to access emergency services in time of need, I'm sure the forum would appreciate hearing it. For some users on this network, NOT calling and uncovering more information about this could be catastrophic if the need should ever arise!

Edited by aliastx, 18 October 2011 - 03:05 AM.

[Neezy13]

aliastx, on 18 October 2011 - 03:05 AM, said:

If you have a better way to test to see if Cyanogen Mod on T-Mobile leaves users unable to access emergency services in time of need, I'm sure the forum would appreciate hearing it. For some users on this network, NOT calling and uncovering more information about this could be catastrophic if the need should ever arise!

I think the best thing you could do would be to call your local PD's non-emergency line and ask them if they have a 911 testing protocol. If you explain your reasoning for wanting to test it, they may work with you. Telephone and security system installers test systems in this way, AFAIK. I definitely wouldn't just call 911 to test it without contacting them first to let them know.

[jkl555]

When I was on 7.1 stable release, my external sdcard is mounted at /emmc and the internal SD card is mounted at /sdcard. Now when I upgraded to nightly 158, they are swapped, that is, external card is mounted at /sdcard and the internal card is mounted at /emmc.

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.

C:\>adb shell
# df
df
Filesystem    1K-blocks   Used Available Use% Mounted on
tmpfs    173052     32    173020   0% /dev
tmpfs    173052 0    173052   0% /mnt/asec
tmpfs    173052 0    173052   0% /mnt/obb
/dev/block/mtdblock2    192000    142120 49880  74% /system
/dev/block/mtdblock3 81920 36124 45796  44% /cache
/dev/block/mtdblock5 16384 14600   1784  89% /radio
/dev/block/mmcblk0p2   1935192    437216   1497976  23% /data
/dev/block/mtdblock6    176128 95680 80448  54% /datadata
/dev/block/mtdblock4 12800   5752   7048  45% /efs
/dev/block/vold/179:9 3868768    329824   3538944   9% /mnt/sdcard
/dev/block/vold/179:9 3868768    329824   3538944   9% /mnt/secure/asec
/dev/block/vold/179:1   13660864   2479136  11181728  18% /mnt/emmc
#

Is that intentional ?

[cdhgold]

I'm haivng more and more FC issues on nightlies since #144 now on #158 155 and 157 were unusable thinking of doing a data wipe and fresh load of #158 or maybe going back to stable 7.1 .. my udpates are done thru ClockworkMod Rom Manager and have it wipe davilk cache each time - anyone have any other suggestions other than complete data wipe and reload?

[theyurtingyeti]

I'm seeing a strange bug? On the stable ROM... I have my ring tone set to A, but it always plays B. I can't figure out why it's playing a different tune than I've selected as the default (I've checked to see if it's specific to one or two contacts, but they all list 'default' as the ring tone to use.)

Funny thing is that if I  hit my power button to mute the ring, it will finish with the one ring tone but then the one I chose goes off w/out any call coming through so I can't turn it off. It's super strange and it just started with the stable release.

It did it when I first installed (kept data), and I did a clean install and it still does it.

Thanks for any ideas!

[maverick999]

I'm seeing a weird issue with the notification power widget on Nightly #161.  The 'Toggle Sound' button isn't doing anything when pressed.  I've tried to remove the button and then re-add it, but still no luck.  Reboot didn't fix it either.

FYI: I did a full wipe (data & cache) before installing this build.

[12andy]

maverick: Currently on 159, and had the same issue as you.

What fixed it was going into the notification bar settings, and toggling what sound modes to trigger/ cycle through whenever the button is hit.

Not sure if you've tried this already, but figured it's worth a shot.

[maverick999]

12andy, on 27 October 2011 - 06:28 PM, said:

maverick: Currently on 159, and had the same issue as you.

What fixed it was going into the notification bar settings, and toggling what sound modes to trigger/ cycle through whenever the button is hit.

Not sure if you've tried this already, but figured it's worth a shot.

Where are those settings?  I can't seem to find them.  

Also, does anyone know how to boost the in-call volume in CM7?  I've always had very low handset volume when on phone calls.  It would be nice to be able to boost this.

[12andy]

CM settings > Interface > Notification power widget > Widget buttons > Sound modes > tick away

[Doodly]

Neezy13, on 18 October 2011 - 08:41 PM, said:

I think the best thing you could do would be to call your local PD's non-emergency line and ask them if they have a 911 testing protocol. If you explain your reasoning for wanting to test it, they may work with you. Telephone and security system installers test systems in this way, AFAIK. I definitely wouldn't just call 911 to test it without contacting them first to let them know.

I use my AT&T Captivate on the T-Mobile network. I recently had cause to call 911, and I attempted this with my fresh installation of CM 7.1 (stable) on the Captivate. It DID NOT WORK. An automated voice told me the service was not available, but I can't remember the exact wording, and I can't remember the error code the voice told me. I hung up and called again; no luck. I did have proper reception as I made several other calls from the same location.

[maverick999]

12andy, on 28 October 2011 - 04:20 PM, said:

CM settings > Interface > Notification power widget > Widget buttons > Sound modes > tick away

Don't know how I missed that!  Thanks!

[12andy]

maverick999, on 31 October 2011 - 05:04 AM, said:

Don't know how I missed that!  Thanks!

NP!

In all honestly, this was the only major quirk I could find with the ROM, considering its current state.

Still trying to find ways to get better battery life (just calibrated), but other than that, it's pretty much flawless IMO.

[theyurtingyeti]

12andy, on 31 October 2011 - 01:05 PM, said:

NP!

In all honestly, this was the only major quirk I could find with the ROM, considering its current state.

Still trying to find ways to get better battery life (just calibrated), but other than that, it's pretty much flawless IMO.

My battery life became awesome when I flashed the current glitch kernel (v12 I believe). I can usually go 12 hours with moderate use. Heavy use depends on what apps I'm running, but I haven't been disappointed yet.

[12andy]

theyurtingyeti, on 31 October 2011 - 02:37 PM, said:

My battery life became awesome when I flashed the current glitch kernel (v12 I believe). I can usually go 12 hours with moderate use. Heavy use depends on what apps I'm running, but I haven't been disappointed yet.

Was reading some guide for installing a Kernel not too long ago, and it suggested flashing from a clean slate (wipe, flash ROM, install, etc.).

The Glitch FAQ doesn't indicate that this is necessary. Think it's a good idea to just pull the trigger, as is?

EDIT: Oh neat, they have an app! https://market.andro....glitch.updater

Edited by 12andy, 31 October 2011 - 03:38 PM.

[theyurtingyeti]

12andy, on 31 October 2011 - 03:20 PM, said:

Was reading some guide for installing a Kernel not too long ago, and it suggested flashing from a clean slate (wipe, flash ROM, install, etc.).

The Glitch FAQ doesn't indicate that this is necessary. Think it's a good idea to just pull the trigger, as is?

I did... I had already installed CM7.1 stable (not a full clean install) and flashed the kernel successfully. In fact, I had tried to do a few kernels that ended up NOT being the right version so I had to use the 'restore' feature in CWM to get my phone back to a state that was normal again.

From there I got the correct glitch version and flashed it from there. In terms of recommended actions, those will help best with potential issues, but I always try without those. If I run into issues, I start working backward making each attempt more clean.

[12andy]

Just flashed Glitch, and things seem a tad snappier(!).

Are you using the default ondemand governor? There was mention of it reverting back to ondemand too (if changed), over at XDA...

Only issue so far is that my soft-button LED notifications no longer seem to work. Tried tinkering with the settings in CM settings, and saved a "misc" profile for SMS, but to no avail. Any idea?

[theyurtingyeti]

12andy, on 31 October 2011 - 05:57 PM, said:

Just flashed Glitch, and things seem a tad snappier(!).

Are you using the default ondemand governor? There was mention of it reverting back to ondemand too (if changed), over at XDA...

Only issue so far is that my soft-button LED notifications no longer seem to work. Tried tinkering with the settings in CM settings, and saved a "misc" profile for SMS, but to no avail. Any idea?

I'm pretty sure I'm "on demand" I haven't actively changed them. I'm running the "high leakage" version as it was a recommended starting point. I'm not sure what could be happening with your LED buttons. Mine have been working fine.

The biggest change I noticed in Glitch is that my kswapd0 process no longer hogs a ton of CPU so I'm running a lower %, cooler, and therefore faster/longer, with far reduced lags.