575 replies to this topic

[MAA-Bunny]

newbie75, on 11 June 2012 - 10:16 PM, said:

Also found today that I couldn't reboot into recovery mode

Reboot into recovery how? I just tried reboot into recovery from the power menu on beta4 and it worked just fine ...

[newbie75]

MAA-Bunny, on 12 June 2012 - 02:03 AM, said:

Reboot into recovery how? I just tried reboot into recovery from the power menu on beta4 and it worked just fine ...

I

Hold power button, select reboot, select recovery.  Usually it would bout into recovery but since update it just reboots.

[wxfisch]

Robbie Doo, on 30 May 2012 - 04:01 PM, said:

That's weird though?!
I have mine on manual brightness and the keyboard backlights come on upon slide.

I too have been having this issue, though It doesn't bother me much as I can type on it without needing to look

My real issue however is that I cannot seem to download any MMS and when I try to send one (either text or picture) I get the "process "com 'dot' android 'dot' mms" has stopped" this is on Beta3, Beta4pre5 and Beta4. I have cleared the cache and delvik cache but that has not helped, im hoping I dont need to do a fresh clean install to fix this. Can anyone offer some insight into this at all??

[pgn]

Where should bugs -- with supporting detail -- for CM9beta/Epic be reported?  This 'discussion' thread doesn't appear the right forum ...

[rundmcarlson]

Epic CM Issue Tracker

[MAA-Bunny]

newbie75, on 12 June 2012 - 03:34 AM, said:

Hold power button, select reboot, select recovery.  Usually it would bout into recovery but since update it just reboots.

Yah, rebooting into recovery that way works just fine for me. Do you have a USB cable plugged in when you try?

[newbie75]

MAA-Bunny, on 13 June 2012 - 11:14 PM, said:

Yah, rebooting into recovery that way works just fine for me. Do you have a USB cable plugged in when you try?

Nope.  I have booted into recovery many times this way and have never had this problem till my recent update to beta 4.

[jazzlover]

Hello and thank you for all of the work you do...we (wife and I) are running Beta4 and enjoying the sandwich! We are having some challenges with voice mail tho. We get a text message when there is voicemail but have only been able to access it by going to phone keypad and holding down "1". The little voicemail icon in upper left does not take us to VM. Is this operator error?

[Zeinzu]

Cm9 nightlies are rolling out baby!

Sent from my SPH-D700 CM9 ANDROID 4.0.4

[StoneRyno]

jazzlover, on 19 June 2012 - 01:34 AM, said:

Hello and thank you for all of the work you do...we (wife and I) are running Beta4 and enjoying the sandwich! We are having some challenges with voice mail tho. We get a text message when there is voicemail but have only been able to access it by going to phone keypad and holding down "1". The little voicemail icon in upper left does not take us to VM. Is this operator error?

You will need to download the sprint VVM app or an alternative. See the customization guide in the links at the bottom of the install guide for details on obtaining sprint VVM or what alternative VVMs are available. A 3rd party messaging app or text blocker app can be used to supress the notifications from the 4 digit VVM text. Normally those are handled by TW or something like that. I'm not sure if that is something they can do once RC stage is reached. I'm not familiar with how it is coded in the stock ROM.

Edited by StoneRyno, 19 June 2012 - 06:12 AM.

[Robbie Doo]

I thought the VVM was a free service from Sprint. Come to find out they charge $1.99/mo.

[StoneRyno]

Only the downloading of the audio voicemail is free. If you want them transcribed to text it is a monthly charge. Silly as that seems they get away with it. Google voice does it for free. But I don't doubt they start charging for stuff at some point. I personally rather listen to the message that read it. But I suppose there are times and reasons where some would need to know the message that listeng to it isn't an option.

[tehBIG]

I'm getting a phantom voicemail notification.  A google search turns up some limited discussion about this, even a potential fix on other forums, but I can't solve the problem.

I'm getting the same result with both AOKP and CM9 (properly flashed both twice now.)  After setting up Google Voice, I get a persistent notification of two voicemails.  There are no voicemails, either on Sprint, nor in Google Voice, I can't clear the notification, and it's crushing the battery.  Flashing the PVMfix.zip file (along with wiping Dalvik and fixing permissions) doesn't seem to do the trick either.

I don't see it in the bug tracker, or widely mentioned--so I figure it must be something I'm doing wrong/could fix.  Anybody here that might be able to point me in the right direction?

Thanks.

Edited by tehBIG, 05 July 2012 - 09:18 PM.

[Kosstheory]

Ever since RC1, I've noticed that the "Kill with long-press back button" option in Developer tools seems to require a significantly longer time to actuate. It used to take about a second, but now it seems to require a bout a 3 second long-press before the app will close out.

Has anyone else noticed this? I would put it in the bug tracker, but I'm guessing it's just a tweak, not so much a bug.

[Zeinzu]

Kosstheory, on 11 July 2012 - 06:06 PM, said:

Ever since RC1, I've noticed that the "Kill with long-press back button" option in Developer tools seems to require a significantly longer time to actuate. It used to take about a second, but now it seems to require a bout a 3 second long-press before the app will close out.

Has anyone else noticed this? I would put it in the bug tracker, but I'm guessing it's just a tweak, not so much a bug.

It makes entirely perfect sense that they would do that and I'm sick of hearing people complain. The delay before way way too short. I would constantly accidentally press on the back key for an instant too long while in an app and force close it.

Sent from my SPH-D700 CM9 4.0.4

[Kosstheory]

Zeinzu, on 11 July 2012 - 07:01 PM, said:

It makes entirely perfect sense that they would do that and I'm sick of hearing people complain.

First off, I'm not complaining; just asking, if it was an intentional modification. Calm down maybe?

In my opinion, it doesn't make entirely perfect sense to change something that wasn't necessarily broken. What if every other action was fixed the same way, like saving a change to a document add a three second delay before you save to make sure the user actually wants to save or delete, or open, or anything?

If I didn't want to long-press to close the app, I wouldn't have checked that option. At the very least a time adjustment would be a nice addition. Three seconds is excessive. It's like the difference between Siri and Jelly Bean Voice Search.

[StoneRyno]

Honestly that feature is meant for development purposes. I don't see the need to force close every app when exiting it to make sure it is closed. If this is being used for forcing misbehaving apps to close there might be a better option as it would seem to me taking this measure to be super annoying to bother with all the time. And if you want to turn android into a sigle tasking OS enable the don't keep activities option and then nothing well remain open once you leave the app. But defeats the purpose of a multitasking OS. Perhaps I'm just not understanding the reasoning behind using this option outside of app development testing.

[Zeinzu]

Kosstheory, on 12 July 2012 - 02:47 PM, said:

First off, I'm not complaining; just asking, if it was an intentional modification. Calm down maybe?

In my opinion, it doesn't make entirely perfect sense to change something that wasn't necessarily broken. What if every other action was fixed the same way, like saving a change to a document add a three second delay before you save to make sure the user actually wants to save or delete, or open, or anything?

If I didn't want to long-press to close the app, I wouldn't have checked that option. At the very least a time adjustment would be a nice addition. Three seconds is excessive. It's like the difference between Siri and Jelly Bean Voice Search.

That's a horrible comparison. One would have applicable sense, the other does not. There would be no reason for a three second delay to save a change to a document. A delay on force closing applications so you don't accidently press the back key and force close your app, however, does make sense. You're comparing apples to oranges. Just because you don't like it doesn't make it wrong. And yes, it was an intentional change and won't be changed back. If I were you I might just get use to it or not use the feature.

Sent from my SPH-D700 CM9 4.0.4

[Kosstheory]

Zeinzu, on 12 July 2012 - 08:11 PM, said:

That's a horrible comparison. One would have applicable sense, the other does not. There would be no reason for a three second delay to save a change to a document. A delay on force closing applications so you don't accidently press the back key and force close your app, however, does make sense. You're comparing apples to oranges. Just because you don't like it doesn't make it wrong. And yes, it was an intentional change and won't be changed back. If I were you I might just get use to it or not use the feature.

Sent from my SPH-D700 CM9 4.0.4

You do realize that your argument goes for your stance as well, right? Just because you can't see why I would prefer a 1 second delay over a 3 second delay doesn't mean that a 3 second delay is necessarily right either. My use case is to be done with the task completely, and quickly. I have never accidentally closed an app by holding back too long.

Here's hoping they add an option to adjust the time, so we can both be happy? Wouldn't want you to feel slighted, if they change it back to one second.

Edited by Kosstheory, 12 July 2012 - 09:02 PM.

[Zeinzu]

Kosstheory, on 12 July 2012 - 08:54 PM, said:

You do realize that your argument goes for your stance as well, right? Just because you can't see why I would prefer a 1 second delay over a 3 second delay doesn't mean that a 3 second delay is necessarily right either. My use case is to be done with the task completely, and quickly. I have never accidentally closed an app by holding back too long.

Here's hoping they add an option to adjust the time, so we can both be happy? Wouldn't want you to feel slighted, if they change it back to one second.

Obviously they changed it for a reason, and they are the developers. Also, doesn't seem to be a mass of following agreeing with you. So regardless of the fact that you want to "prove me wrong", or "argue your point against mine", it is what it is so get use to it. The feature isn't there to force close every app you use after you're done anyway. Android does that itself if you exit your apps properly or when ram is needed. That option is for cases when you have no choice but to force an app to shut down. Force closing every app you use constantly can be damaging over time. But I'm sure you're gonna argue that you know better than our devs, all the CM devs, Google's programmers and engineers, and anyone else involved in the projects surrounding Android, though.

Sent from my SPH-D700 CM9 4.0.4