Related
I am in Baltimore Maryland... Ever since i upgraded to jf's rc33 firmware, i get aloooooooooot of " undelivered message" notifications. This never used to happen to me, maybe once a week with 2 messages. In most cases people ask me why the F am i triple texting, and it happens when i try to resend the messages and the phone keeps saying "message cannot be delivered". Is anyone else experiencing this? In maryland only perhaps?
I have tried keeping message count below 100, reseting the phone seems to be the only quick fix. One other thing, when i try to make phonecalls every now and then, the **** just hangs up as soon as the call is placed and when i receive a call sometimes and i press the answer key, it takes about 10 seconds to answer and continues to ring. suggestions buddys?
Make sure you delete your SMS threads if they get too long. Typically once threads get past 150 they are slow and take a while to open. If you are using the stock sms try chomp seems to handle threads better. I have JFRC33 and have not issues.
My wife and I have the exact same problem with the phone hanging up and not picking up a call for while. And dropped calls - almost always. And we live in the heart of Dallas.
yea the g1 is a nice phone, but either android or t-mobile blows..
every now and then people call me, and i get a missed call, but the phone never rings,
and sometimes when i call people, they pick up but one of us cant hear the other,
and sometimes, the g1 will ring, but when i press the green button to anwser, the phone continues to ring
im getting pissed off,
rc29, rc33 both fail to work
I am in Baltimore as well, and I have JF1.42 RC33, without any of the problems you have. Sorry, can't be of more assistance, but maybe your SIM card is old and needs to be replaced? I have heard of them causing issues sometimes.
yup same thing is happening to my phone. it is really starting to piss me off. i thought it was cuz i dropped my phone but i guess others have been getting the same thing. i hope theres a fix for this
I had this happen to me about two days ago. SMS failed to send to anyone. I restarted the phone and havent had a problem since. They are still developing this unit, so try to be patient.
i've had some calling issues recently, both making and receiving.
sometimes when receiving a call, i'll pick up and my phone will reboot, and take absolutely ages to boot up. and when making calls the other end will sometimes go completely dead and it's the same for the other person.
only happens very occasionally but it's happened with a few landline calls and different mobile networks. only been since RC33 too. not saying it's related but it is kinda annoying.
Wipe fixes all
unless the problem's firmware/hardware related, then it does **** all.
Wipe and wait
Could be too many apps eating memory on the G1 and/or buggy apps crashing buggy android. The best you can do is download mybackup from market, back up all data +sms+ageda etc, Wipe the phone. An dont install a single app from the market in 1-3 days and see if problems dissapear.
Personally, i never install any app who claims to "start at boot" Never. MyBackup is one of them and always delete it after backup. i may be wrong but i thing resident in memory apps and apps who starts at boot degrades performance over time, because many of them are buggy so i avoid using them. Well my phone runs fine with this.
buggy behavior
well i think this happen when phone memory is full, try to delete least used applications, clear applications cache like browser and youtube , then do a reset.
Ive had the issue more than a few times where the phone will start ringing but the screen will stay dark, i wait until it turns on to see who is calling after a few rings and then it wont respond to pressing the answer button unless i press it a few times, and even then it takes its sweet time answering. Ive dropped plenty of calls due to this, and yes it has only started happening after the radio firmware/RC33 update.
unrafa said:
Could be too many apps eating memory on the G1 and/or buggy apps crashing buggy android. The best you can do is download mybackup from market, back up all data +sms+ageda etc, Wipe the phone. An dont install a single app from the market in 1-3 days and see if problems dissapear.
Personally, i never install any app who claims to "start at boot" Never. MyBackup is one of them and always delete it after backup. i may be wrong but i thing resident in memory apps and apps who starts at boot degrades performance over time, because many of them are buggy so i avoid using them. Well my phone runs fine with this.
Click to expand...
Click to collapse
Oh... don't even start my on "MyBackup"... I kept trying to figure out why my phone was lagged so much when I was going back to home screen. Uninstalled apps that were running all the time one by one. MyBackup and Phonebook were 2 biggest memory hogs. Phone runs oh so smooth after I unistalled those 2. Backgrounds app still autostarts for some reason but I like that app too much to uninstall and it does not cause as many problems.
bleomycin said:
Ive had the issue more than a few times where the phone will start ringing but the screen will stay dark, i wait until it turns on to see who is calling after a few rings and then it wont respond to pressing the answer button unless i press it a few times, and even then it takes its sweet time answering. Ive dropped plenty of calls due to this, and yes it has only started happening after the radio firmware/RC33 update.
Click to expand...
Click to collapse
I still have this problem after another wipe..
why does android suck...
i wish tmo would come out with a winmo 3g phone, so much more stable and with more features =(.. i miss my shadow now
I started running into the issue of the phone not actually responding to the "answer call" button, but found it was only happening when I had auto-rotate set up with the DroidSans tools and the display had been rotated to landscape. It seemed like it would start trying to switch to portrait, then lock itself up long enough for the call to go to voicemail, then flip to portrait and be responsive again. I haven't had the problem since I disabled auto-rotate.
However, on the "too many apps" thing, I've suddenly started noticing that my phone will start a good 15-20 apps on startup, including things like AK Notepad. I didn't notice if this was something that started with RC33 or if I've done something else to make this happen...does this happen with anyone else?
I have had a similar issue with my g1 dropping calls and will sometimes see a force close while on a call as well. I did a wipe and did not enable auto rotation and so far it seems to be running more smoothly.
Been there done that...I am having the same issues and it is beginning to drive me nuts. I make heavy heavy use of my phone on a daily basis. Dropping calls where they just go to la la land...or the phone rings and I cannot answer for about 10 to 15 seconds, the phone just reboots for no reason... stupid things like that. I have RC33 rooted, radio upgraded with JF 1.41 and this has been happening daily about 3 times or so a day. I love my G1 and I have a hard time parting with it...I am trying to be patient while it develops but...I am about to go get the 8900 curve...
I forgot to mention...I had to do a wipe on my phone also due to a problem with the accelerameter and that did not help this issue either.
-Tonloc69
it seems to me that it is tmob related, since i`ve had that b4 on my lil nokia phone.
About half the time, when I try to answer an incoming call, my Verizon TP2 will only mute the ring without answering the call. It responds the same whether I use the touch screen to answer or press the send key, and whether or not the phone is locked or unlocked when the call arrives. Has anyone had a similar problem or know of a fix? Thanks.
I got this behavior the first time I finished getting the phone set up how I wanted. I eventually had to hard reset to fix it.
I think it was probably s2u2 interfering with the nonstandard dialer / answer bits on the phone. Even uninstalling it didn't help though. I have not bothered to try reinstalling s2u2 after the reset though to see if it causes the problem again.
i have this same problem. as i recall there was some registry tweak you could do to fix it, but i cant remember it to save my life. I have the worst problem with being on the internet and trying to answer a call. anyone know of a fix? whenever i am on opera and try to answer an incoming call it just freezes and i have to exit opera and call the person back. anyone with a fix for this other than a hard reset?
i had the same problem before i flashed to 6.5 on my vzw tp2. I also suspected that it was because of s2u2: I followed to uninstalling and i kept on getting a message about s2u2.exe not being a valid app or something. I also thought it could have been because of the dialer i had. The dusk dialer...for sense2.1 while i had manilla. after the flash i reinstalled s2u2, and will see if this persists to happen again.
It happened to me for the first tiem twice yesterday, my phone awoke and I could see my taskbar icon switch to 1x but I didn't see a call then I got a voicemail, when I called the person back they said it rang 6 times and went to voicemail, and it happened again later where i saw the call box and slide to answer come up but the screen was stuck and I couldn't answer it, not even with the hardware key.
Same thing is happening to me. The first time someone calls it won't answer whether I use the soft key or the hard key and the screen just freezes. However when the person calls back, it answers immediately when I click the answer button. I don't have S2U2 or any other phone/lock apps which interfere with answering a call.
Same here guys, I have been having the same issue, but as I can see for weeks now I haven't been able to nail down a solution either...
I too have had the same issue for several weeks. More prevalent when the screen is locked. Rings once and goes to voicemail.
stupid double post.
I've only run across this issue when I am using too much RAM. Try using cleanram and closing out tasks that you are not using.
I have virtualized my RAM so that it never utilizes over 50 % available and have also made sure that all applications utilizing memory were closed down. The problem still persists and can not identify its cause.
reddington said:
I have virtualized my RAM so that it never utilizes over 50 % available and have also made sure that all applications utilizing memory were closed down. The problem still persists and can not identify its cause.
Click to expand...
Click to collapse
have you tried s2u2 and their call answering interface?
Hey guys!
Samsung Focus is having problems during calls. Many people has this annoying problem where the call completely MUTES apparently randomly. In other words, you are talking and you stop hearing everything (and so the other party) UNLESS you press MUTE and MUTE again (to MUTE and UN-MUTE).
It's completely annoying and Samsung/AT&T are not willing to replace the units because "they can't repro". References:
http://answers.microsoft.com/en-us/...one-call/23bd1b3b-035b-e011-8dfc-68b599b31bf5
http://answers.microsoft.com/en-us/...ed-calls/62ce2e8d-649a-4fa4-bb1e-9aea41c9f5a3
http://answers.microsoft.com/en-us/...ng-focus/771cdafb-1c4e-43d5-bcb7-da70edb5e5f7
http://forum.xda-developers.com/showthread.php?t=1030024
So, I would love to build a program that really MUTES and UNMUTES the phone, not by turning down the volume but doing the exact same action that happens when you press the real MUTE button.
Is there any way to achieve that? I would love to detect the 100% mute while speaking, and if that happens, just run the little program which MUTES/UNMUTES and by doing so, corrects the problem that lovely Samsung and AT&T can't repro.
Thanks!
Magic.
my samsung focus never had a problem so far...i got it in jan of this year and never had a problem ..u sure its all or just one disinfected one
Hi rdsjuggalo!
I'm not saying 100% of Samsung Focus have that problem. I'm saying that many people have the same issue and so do I. I've provided links to other places where people from around the globe have the same problem.
Now, this has nothing to do with infections. My wife's phone and mine are 100% originals without a single program installed, and that happened from day 1. Also, I've sent the device to Samsung and AT&T two times and it came back with their own installation of the OS, but the problems are still with me.
So, yes, I'm sure this problem is happening to many people and that it does not have anything to do with programs/infections.
Thanks!
What the hell is going on. I tried resetting and everything, even exchanged the device and the new one is doing the same thing! Also vibrating and force closing it is getting on my nerves! The followig seems to happen after a while I am TIRED of having to turn of my phone and turn it back on! ~ I go to play a .mp3 it says " FIle type not supported"...My .mp3 ringtone does not work the phone just vibrates the selected ringtone doesnt work. I got too take a picture or record video it says "Camera Failed"....I get a visual voicemail....the "play" button is grayed out and I have to turn off phone turn it BACK On just to check my voicemail. Also occassioally my sms wont work either. I turn my phone off and on every morning and throughout day I notice this and its getting REAL annoying !
Well first off, this isn't a software flaw, this is specific to you, as we have many users here including myself who are using these phones daily without the issues you are describing.
You had said that the issue was with an mp3, can you upload that somewhere for us to test on our phones?
As far as the camera and visual voicemail, I've never heard of that issue before, perhaps you ended up with a bad phone again?
I am getting the frequent force close with messaging. I also have had problems with the camera and idk about the mp3 stuff I haven't put any ringtones on the phone yet. This is getting really annoying I agree.
I don't have any issues with mine? Have you guys done anything like rooting or flashing anything?
Nope, completely stock. The most I have done is take a screen shot lol.
hmm maybe some have a defect? It's not all SK4g's though, as some of us have no issues at all. I would suggest getting it replaced by T-Mobile, as this is a factory defect. not sure why that happened to you guys. has anyone else had these issues and found any fixes?
That's kinda tough the hearest t-mobile is like 4 hours from here /:
One of my friends who went with me on the trip to get the SK also got one and he says he's never gotten a force close so you may be right. But could it have anything to do with the amount of texts I send/receive? Because I have to admit it is pretty excessive. The failing to send messages when I am receiving one simultaneously is expected, but not the force closes in my opinion.
It shouldn't force close on you. I know mine fails to send every once in a while too, as I text a lot (kinda the reason I got the phone). failing to send isn't as big of a deal, as it notifies you and you just have to click resend. Not entirely sure why it's force closing though? I wonder if a logcat might help? if you have adb installed, you can try adb logcat and see what shows up when you force close? if we can find the issue there, it might be fixable from our end. all depends on where the flaw lies/if it's just a bad apk somehow or if there's an actual hardware issue or something.
I'll do a log next time there is a fc, I'm having another issue or it may be related, but this one is with WidgetLocker I believe. Sometimes when I go to unlock the phone it'll freeze up and then I dont know how to explain it, but it almost seems like it resets but it really doesnt. The phone will blackout for a little then the homescreen will pop up and service will gone for a while until the cards are read just like if I rebooted.
That might be a function of WidgetLocker, I used it on my old G1 and it always hung and black screened at me.
sduvick said:
That might be a function of WidgetLocker, I used it on my old G1 and it always hung and black screened at me.
Click to expand...
Click to collapse
Yeah I know it does that from time to time, but on my previous phone it wouldn't do that reboot thing where it would lose connection then resend my latest text messages once it reconnected.
I'm not sure why it's doing that. My guess would be that the issues are caused because the SK4G doesn't use a normal lock screen. widgetlocker uses some modification of the system file for the lock screen, and perhaps it's not sure what to modify? just my 2 cents.
sduvick said:
I'm not sure why it's doing that. My guess would be that the issues are caused because the SK4G doesn't use a normal lock screen. widgetlocker uses some modification of the system file for the lock screen, and perhaps it's not sure what to modify? just my 2 cents.
Click to expand...
Click to collapse
That's what I was thinking too, I'm gonna uninstall it for a bit and see if anything changes.
is anyone else having an issue with notification volume? everytime i reboot my SK, my notification volume gets pushed all the way down to nothing, so i don't get a sound notification for texts, emails, etc, until i move the notif. volume back up in my settings. i did root with the one-click for the Epic 4G.
This is a new UI so alot of the apps i.e. widgets you may put on will cause issues. If you like certain apps contact the dev so your device is supported correctly. Still to new to get mad at it till sum of the bugs get worked out. I did notice a couple of times when I left screen on in pocket on accident that when I go to use it again it doesn't respond to any touch but can move courser around till rebooted then its ok. If some don't already know the sk4g is almost the same as the epic. The sk4g is still a badass phone for 100bucks.
Same as the OP
I know this is a little old, but I've experienced the same problem as the OP so it seems they are not alone with this problem.
I actually tried two different newly formatted SD cards (because I thought it may have been the SD card), and still would have the problem. Then I actually did swap phones about a month ago and it seemed the problem would now take several days to resurface instead of several hours. And I could deal with that.
Since the OTA update about 2 weeks ago, the phone has been back on it's original BS as the OP posted and it's driving me nuts. I actually missed some emergency calls last night because the mp3 ringtone didn't work so I'm finding a solution to this issue today or trashing this phone.
My belief is that there is something interfering with the phone's ability to read the SD card for media. Because other apps I have that save to the SD card or read from it work fine. So I'm going to master reset it and not download any of my apps and see what happens when I set an mp3 ringtone. If it makes it through the day with no hiccups, I'll slowly add back one app at a time until hopefully I can find the culprit.
bipoler if you'd like, we can exchange via PM what apps we both have downloaded and see if we have some in common that may be problems.
I'll post back with any progress.
I've been having the problem with ringtones not working, just getting silence when I get a call. for me it seems to happen when I set a ringtone from the app Zedge, I don't think it happens when I use ringtones from the Android System, which would make sense if the issue is related to reading the sdcard. gonna go back to a system ringtone and see what happens today.
Yeah my phone had all those problems, but I installed the Lightning rom and all those problems went away, except for the ones about messages failing...I text A LOT
Lightning ROM
Thanks for that info on the Lightning Rom. I will check that out. Phone has been working flawlessly all day with the mp3 ringtone and no extra apps besides the master reset. I might give it until the morning before I start putting them back on.
On stock id install so many apps that ran on the background that id get delay from opening closing swiping and turning onthe phone.. so I wiped it installed a custom rom and just kept the essentials.. havnt had a problem since... well.. occasionly ill have to odi but that's on purpose
Sent from my SK4G
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
c4sh said:
After upgrading to lollipop, I have noticed when recieving a call that sometimes my phone will ring for about 1 second and then stop but continue to vibrate. I am not using any quick cover or anything. This doesnt happen all the time but it does happen quite often. Has anyone else had this problem? I'm completely stock on 5.0 (i have deleted my cache partition and the problem still persists)
Click to expand...
Click to collapse
Are you using a custom ringtone?
Aerowinder said:
Are you using a custom ringtone?
Click to expand...
Click to collapse
No, just the stock tones. I find it happening sometimes with my SMS messages as well but not all the time.
Update: I have since unlocked my bootloader (wiped) and rooted my phone and the problem still persist. Seems like I'm not alone, I have starred this so hopefully someone can see it. https://code.google.com/p/android/issues/detail?id=81178#makechanges
Anyone have any suggestions that I could try?
update
I had thought I had fixed the problem by re flashing the stock image of lollipop, the problem went away and my phone started to ring again but shortly its back to only vibrating. I noticed that the little vibrate symbol was popping up in the status bar whenever I received a call, even when I turned off the also vibrate for calls option. I then remembered that when I use the volume butler app and set it to my vibrate profile that symbol would also pop up. I uninstalled volume butler and everything seemed to be working fine. Next I Checked the play store for comments regarding the issue and I noticed two things: There was a recent fix "ringtone changing to silent upon first install" and it said that the app was installed onto my device and not requiring an update even though I had just uninstalled it. So I decided to open it up and it was as if I was starting the app for the first time as none of my previous data was in there for testing purposes I decided to set up the same profiles that I had before and try calling my phone and my phone rang like it should, weird. Perhaps I had two versions and that was the one that I originally uninstalled is that even possible?( I could have sworn I had updated it,as it was under the up to date app list) Regardless, I uninstalled it again and everything is still working as it should. Hoping that this was was the culprit I will continue to test my phone and see.