• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Comprehensive list of known issues?

The really sad thing is 1.5 was Samsung's fault because it was the wrong version to run on the Moment, and 2.1 is Samsung's fault because they just didn't try hard enough to do it right. They even spent months working on it, and still screwed up things that worked in earlier betas.
 
1) I have had the issue Hotani has had with random pocket stuff, etc. This seems to be a natural for smart phones across the board - it's a new tech and we are learning the ergonomics, functionality with pragmatism, etc.

2) I haven't really posted, and I wanted to start a new thread... but have lurked for months and have waded through 100's of posts and don't really see the same problem or logical progression I am making with my specific issues with the phone

3) I commiserate, patiently, with all of you.

Probs:

a) I have had the call issue Ms_Kady, anthromat, sboggus have said with the phone not ending the call. Good times on work calls, let me tell you. The second aspect to this is sometimes you aren't confident it is *really* off, and have to turn it back on to make sure it's off. This is my neuroticism, I am sure. =)

b) The Dialer, Google Voice, Bluetooth, some of those, or more are making my phone lag and almost dysfunctional. I know Bluetooth gets laggy and weird sometimes, but my phone is usually beyond laggy, force closes programs, or offers to "force close or wait". The dialer won't even come up sometimes, and when it does I almost want to throw the phone against the wall. I have noticed - i) I deleted google voice and re-downloaded once, and my phone was breezy and so gratifying ii) trying to make calls on the road with BT & GV were damned near impossible, and hear is the real drama....

it seems like my phone will make one call, once, fairly competently. The app opens, takes a bit to let me maneuver to "favorites"... call goes through fairly simply, and then ends. After that it is almost impossible to make a phone call.

But, more than 75% of the time, even on the first try, my phone will lag so hard that it will take me (from freshly booted, sitting and ready to go for at least 5 minutes or more) 8-15 minutes to make *ONE FREAKING PHONE CALL*

Is that my phone? Is that dialer? Is that the GV app?

I didn't want to bore people with this rant, but this is the end of the line, and only place to go, methinks? I hope not to add more minor, non-reproduceable errors that may be due to a faulty phone or app.... but something is going on here, and I think it may be a frustration to a larger group of people not isolating or thinking about the issue. I know a lot of people that return this phone almost immediately for a multitude of reasons. I think it might be because of some lousy apps that aren't helping the hardware perform. I know of consistency and app issues within the market....

can this thread also identify known issues with apps that destroy the functionality of the phone? I started deleting apps a couple weeks ago. When I took out Pandora, it operated faster for a bit. I am wondering what might be eating up my bandwidth, memory, etc. Nothing seems to work right. ARGH!

/rant
Thank you. =)
 
On issues with the phone unlocking in a pocket, I can see how it can happen after seeing how a 17 month old can quickly unlock a 2.1 moment.
The issue is caused by using the slide to unlock mechanism, on a phone that does not have multitouch enabled. Pressing the unlock side with one finger, followed by the speakerphone side with another finger, and releasing the first does it. A toddler holding the phone in both hands, presses buttons until the screen lights up, then presses the bright areas on the screen repeatedly until something more happens.
It's shocking that a baby can unlock a phone in seconds on their first try, faster than an adult could interpret the symbols and unlock it.

Basically on a non multitouch phone, a slide can be substituted for with 2 touches.
 
kevinrs said:
On issues with the phone unlocking in a pocket, I can see how it can happen after seeing how a 17 month old can quickly unlock a 2.1 moment.
The issue is caused by using the slide to unlock mechanism, on a phone that does not have multitouch enabled. Pressing the unlock side with one finger, followed by the speakerphone side with another finger, and releasing the first does it. A toddler holding the phone in both hands, presses buttons until the screen lights up, then presses the bright areas on the screen repeatedly until something more happens.
It's shocking that a baby can unlock a phone in seconds on their first try, faster than an adult could interpret the symbols and unlock it.

Basically on a non multitouch phone, a slide can be substituted for with 2 touches.
Click to expand...


Guess I'll just have to remember to put the phone in-pocket screen out.
 
I am on my third moment and I am still having problems with the proximity sensor. My phone's screen randomly lights up when I am on calls which drives me nuts. Does everyone have this problem with their phone?
 
I haven't had the proximity sensor issue. I did have video camera issues on 2.1 stock if I installed FXCamera. Reflashing DE03 fixes the bug, but the phone gets completely wiped in the process.
For the M900, the most stable root and ROM configuration I have found is the Joeykrim SDX kernel with recovery.
 
#1mom said:
I am on my third moment and I am still having problems with the proximity sensor. My phone's screen randomly lights up when I am on calls which drives me nuts. Does everyone have this problem with their phone?
Click to expand...


Yes. It randomly stops shutting the screen off about 5 mins into a call.
 
#1mom said:
Do you know of anything that can be done about it?
Click to expand...

At this point, nothing. There is a rare chance SDX will solve all the issues with custom ROMs but Samsung has demonstrated they aren't very interested in the phone or its users. This has aroused a state of apathy in a fair chunk of the community, and I think those of us that probably wanted to see the phone reach its potential most are now resigned to move on to a different-branded phone as soon as we can. I mean, the phone came out, had a ton of issues with core functionality, it took them 4 months or so to patch that, and it took 5+ months after announcing a version upgrade to get that out the door, and it's broken just like 1.5 was. In fact, the final version of 2.1 seems to be more troublesome (to me anyway) than the beta I tested (DD03).

There's still a couple of users who think the Moment is the bees knees and will keep with it and push others in the community to develop fixes... but I think many of the most brilliant minds feel burned.
 
Has anyone ever gotten their phone replaced for a different kind of android phone through assurion or sprint due to the proximity sensor defect?
 
I need help. I puchase a used Samsung Moment (Sprint) that was rooted. I was able to activate the phone partially the manual way. (Updated ph# and MSID). But my data wont work and the phone itself will not 'self activate'. I have flashed and re-flashed, unrooted and re-rooted. Wiped and did hard resets. The phone simply will not activate the DATA. Also the MSL is ##000000# and some of the other sprint codes do not work, i.e ##775# (PRL) and the original MSL. Anyone have any ideas or suggestions on what I can try? Sprint already thinks the phone was 'modified' and thats why it wont connect.
 
blueox said:
I need help. I puchase a used Samsung Moment (Sprint) that was rooted. I was able to activate the phone partially the manual way. (Updated ph# and MSID). But my data wont work and the phone itself will not 'self activate'. I have flashed and re-flashed, unrooted and re-rooted. Wiped and did hard resets. The phone simply will not activate the DATA. Also the MSL is ##000000# and some of the other sprint codes do not work, i.e ##775# (PRL) and the original MSL. Anyone have any ideas or suggestions on what I can try? Sprint already thinks the phone was 'modified' and thats why it wont connect.
Click to expand...

flash it to cl14, get it activated, then root it after! or flash it to the kenel sprint provides, then reflash it, and root it then.
 
Zumaki said:
... I think those of us that probably wanted to see the phone reach its potential most are now resigned to move on to a different-branded phone as soon as we can. .
Click to expand...

I am sick of this phone. Just had it swapped out at sprint under their 1 year warranty, and the issue is occurring a lot less frequently with the new one, but still does occur (the issue where the phone stops receiving data). And I still feel the phone constantly vibrating from my face hitting it while on a call. I had a Samsung Rant before this, and that was a terribly bad phone as well, but the Moment "on paper" was far superior to most Android phones at the time, so I decided to try my luck with Samsung again. Fail. I refused to use another Samsung moment for the rest of my life. I can get a new phone in November, so I'm just going to suck it up and deal with crappiness until then.
 

Hello Nation,

I have a Samsung Moment and the trouble I am having now is I love the apps, but I have very little room to add anything to my memory. How can I extend my capacity for more apps and actually view and delete what's I don't need. My second and biggest problem is how to send a video, if it is to big to send.

:confused:
 
Okay, I'm just wondering if I can get an idea how common this issue is. When 2.1 came out, I flashed and the update went off without a hitch. Then the phone began crashing sometimes when the screen timed out. It would completely die and not reboot till I removed the battery. Had it reset at the store and they replaced the battery too. Crash! So I got it replaced. This one came with 1.5, so I reflashed after we got some other issues with my phone activation solved. Next day, the thing startes doing the crash on me. I take it in and am told that maybe it's cause of some third party stuff, free ringers, on my SD card. Well, they did a master reset and I bought a new memmory card, cause I wanted an 8 gig. Crash! Yesterday, I took it in and they are going to replace it for another one. This one will come with 2.1 already installed. Maybe the factory can succeed where I can't. My dad is still using 1.5 and isn't even thinking on updating anymore because of all my issues. So who else has the crashing phone? I know of one of you who posted earlier that it was fixed by a reflash, but I didn't get that memo till right now. Still, it's so freakish that I'd have the same issue with two phones. I didn't even use the same computer for both flashes! Total craziness.
 
I am having the crash issue as well. Phone completely shuts down (plenty of battery) and will not come back to life without pulling the battery. This has been happening more and more frequently in the past couple of weeks. I've had 2.1 since it was officially released.
 
My phone is new, came with 2.1. After it was turned off for 10 days during a trip (WI-FI only), it started the described crashing behavior. It was still within the one month return period and its replacement has not yet given any trouble.
 
Hmm, so possibly my replacement that comes with 2.1 will be alright. That's good. I mean, asside from all the crashing and the fact that I would like better battery-life, I like the phone. And I like android especially for it's affordable accessibility. I've been used to having to pay extra for a screen reader.
 
Not really a new problem that has developed for me, but it's making me SO ANGRY.

My texts go to the wrong contact if I'm talking to more than one person at a time. The software gets confused and sends it to the wrong person.

I'm talking to Contact A and Contact B.
I send a message to Contact A.
The software sends it to Contact B.

I am so close to buying another phone off of e-bay (honestly, doesn't matter what), and just ****ing throwing this one out the window until they fix that issue. It's the only issue that keeps me from wanting to use it any longer.
 
I am having a random issue with my Moment which is annoying the heck out of me. Some mornings(every couple of days) I'll wake up to no EVO arrows and also no signal bars. Basically the phone has no service whatsoever. When I press the End key to shut off the phone, I see the ubiquitous Airplane Mode is turned on message. I will turn it off and the message changes, but the service doesn't come back. I have no recourse other than to reboot or pull the battery out. I am running the Radioactive Froyo 1.8.6 ROM. Is there any fix for this issue other than to reboot?
 
hotani said:
Nope. Unfortunately the airplane mode bug happens on all builds and there's no way to fix but reboot.
Click to expand...

I know the Airplane Mode bug hasn't been fixed in 2.1 or any of the derivative ROMs , but before it was just the data service that used to get hosed, not the telephone service. Now I can't even make or receive a call without rebooting :mad:

I have another issue with the Moment that's aggravating. Basically the phone keeps jumping back and forth from WiFi to EVDO even when I am sitting right next to the WiFi router. The signal strength is at full bars. I know it has nothing to do with my router because my wife's Hero does not have this random switching issue.
 
samaruf said:
I know the Airplane Mode bug hasn't been fixed in 2.1 or any of the derivative ROMs , but before it was just the data service that used to get hosed, not the telephone service. Now I can't even make or receive a call without rebooting :mad:
Click to expand...

hmm, when I've had the airplane mode issue, the way I've known it was that and not some kind of lag or temporary internet issue, is by attempting to make a call. I get the airplane mode message when I try to make a call. Airplane mode is not turned on, and does not show as on in any other way.
 
You must log in or register to reply here.
Back
Top Bottom