Related
Ever since I've updated my 8125 to use any of the various 2.x firmware updates out there, I keep having a real annoying problem where calls drop, my antenna symbol shows a little x and I keep hearing these little blips through the speaker even though I'm in an area where there is a good signal. This never happened to me on the original 1.x rom, and there have been several times where this happens and people who have tried to call me can't.. then I notice the x next to the antenna symbol.. if I do a soft reset of the phone, my service is restored when the phone boots back up. Anyone else experiencing this? If so, anyone know what ROM version is the most reliable?
http://forum.xda-developers.com/viewtopic.php?t=53432
Can someone help me how come every so often I place press call after entering a number there can be a delay of 5 to 30 seconds where nothing happens. Or of I push the name of a recent call it has the same delay. If I push it many times sometimes it will continue placing new calls while I'm already called. I'm running Sprint 2.1 official. Thanks
you probably don't have very good service where you are, unless you deny that statement.
Only hit it once and you'll only make one call.
Sprint's rom is ridiculously slow and laggy.
More peopel could probably help you out with specific problems with sprint's rom on sprintforums.com or somewhere like that. NOT that we don't want to help, but problems often have different levels of depth, if you know what I mean. Or root and get ever CRAZIER problems and then stick around here!
EDIT: that is, http://www.sprintusers.com/
rt1oo said:
you probably don't have very good service where you are, unless you deny that statement.
Only hit it once and you'll only make one call.
Sprint's rom is ridiculously slow and laggy.
More peopel could probably help you out with specific problems with sprint's rom on sprintforums.com or somewhere like that. NOT that we don't want to help, but problems often have different levels of depth, if you know what I mean. Or root and get ever CRAZIER problems and then stick around here!
EDIT: that is, http://www.sprintusers.com/
Click to expand...
Click to collapse
thanks, but i think its the phone, because now when I click the green button the phone comes up immediately but nothing on the screen works. Its almost like clicking an image no beeps nothing.
Below is more detail of my problem
Can someone help me. How come every so often I try to place a call their is a long delay.
For example I will push the green call button to bring up the phone. Then I will click on a name from my recently used numbers and I will click the number I want to call and it will highlight then nothing. After 10 to 15 seconds does it vibrate and place the call and go to the screen with the timer and the end button. If I get impatient and keep pressing the number (selection goes green for a second) nothing happens for 10 to 15 seconds then the call is placed and it will continue dialing, holding, and conference call as I try to talk to that person.
This delay also happens when I dial a number, and the number keypad is slightly sluggish when dialing.
Please note I a running Sprint Official OS2.1 and even though the Phone Application is sluggish outside phone mode the device seems to run when when using other internet. I am also getting strong bars and EV.
I would really appreciate your help; I just got this phone 2 days ago and really like it, but this one fault is killing it for me.
Please Help me.
Thanks
please somebody help me other than that i really like this phone.
integra144 said:
thanks, but i think its the phone, because now when I click the green button the phone comes up immediately but nothing on the screen works. Its almost like clicking an image no beeps nothing.
Below is more detail of my problem
Can someone help me. How come every so often I try to place a call their is a long delay.
For example I will push the green call button to bring up the phone. Then I will click on a name from my recently used numbers and I will click the number I want to call and it will highlight then nothing. After 10 to 15 seconds does it vibrate and place the call and go to the screen with the timer and the end button. If I get impatient and keep pressing the number (selection goes green for a second) nothing happens for 10 to 15 seconds then the call is placed and it will continue dialing, holding, and conference call as I try to talk to that person.
This delay also happens when I dial a number, and the number keypad is slightly sluggish when dialing.
Please note I a running Sprint Official OS2.1 and even though the Phone Application is sluggish outside phone mode the device seems to run when when using other internet. I am also getting strong bars and EV.
I would really appreciate your help; I just got this phone 2 days ago and really like it, but this one fault is killing it for me.
Please Help me.
Thanks
please somebody help me other than that i really like this phone.
Click to expand...
Click to collapse
Since you are not rooted and not running a custom ROM, this is probably not the best place to ask for help. You should call Sprint directly or check out the website/forum listed above.....
This lag is common on this particular phone. Just look at all the threads about dialer lag. 2.1 made the dialer lag even worse IMO. A custom ROM may or may not fix it for you.
i'm run Aloysius and Darchdroid I have the lag too. I dont know the problem i just wait.
i run DC and its laggy too... i bet its the dialer app...
that huge delay in actually dialing the number is an issue with all of the ROM's based on the official 2.1 (and the last leak as well I believe). No idea why it happens, but I hope a dev manages to figure out how to fix it soon, because it's the biggest annoyance for me
lag everywhere
i agree, the dialing lag is very annoying. also I have issues when im using the web browser while trying to tap on the url bar or in a search field the phone just hangs and doesn't bring up the keyboard.
while my buddie is already looking at a web page or search results on his very responsive palm pre webos im stuck waiting swearing at my phone lol.
But given all the things you can do to androids compaired to webos ill take the lag.
It was so bad for me that I took my phone into a sprint store and showed them how f'ed up it was. They said that it was happening a lot...evidently they have an internal forum where these issues get posted and the tech I talked to at the store said he saw a ton of posts referencing this same issue. They told me, however, that my phone passed diagnostics and that I could make and receive calls, to which I responded, "sure, I can make calls, but it barely functions as a phone." They sent me on my way, and I figured that was that until I got a text 2 days later saying that my replacement phone was in.
When I went to pick it up, the store rep said, "We'll have to reload the update for you" and I told him not to bother. Whatever issues 1.5 had, they were better than the enourmous issues with 2.1. Of course, as soon as I got it home, I rooted it (the 2.1 root came out the next day) and had 2.1 running quick as a fox anyway.
I have had the same issue, but have discovered one important thing by looking at the logs and just observing... This does not happen when using WiFi. I have a log showing that this problem is related to turning the radio off in order to make the call. For those who do not know, this is unique to CDMA in that it cannot use both data and voice at the same time. For some reason it is taking forever to turn data off in order to make the call. This has been reported to Flipz and he is looking into it, but until then I guess you just have to put up with it or go back to a 1.5 rom.
For those to say that the problem doesn't exist on rooted phones or that he should go somewhere else is not giving any good advise.
I have been rooted for several months and never really had any problems with an extremely long delay until recently. . I know if I am rebooting my phone I have to wait a little bit to do anything, even after Sense has finished loading or i will have the same problem. I'm sure you were not rebooting your phone when this happened.
Here was my experience 2 days ago...
I tried making a call and pressed on the contacts name. It was just sitting there. After 20 seconds it still wasn't calling, so I pressed the name again and after 15 more seconds it began calling the person. And then it started dialing again. I hit End Call and attempted to do it again. I had the same problem. I then rebooted my phone and waited 5 minutes and tried again and had the same results. In between pressing the contact and the phone actually calling it just sat on the contact screen. I have had the same ROM running on my phone for 3 weeks and this was the first problem I had like this.
At first I thought it was with Sprint, but it should have atleast gone to the calling screen and said dialing if it was even attempting to call.
If you have had this problem was it just stuck on the dialer/contact screen or was it on the screen that says dialing/calling?
It gets stuck on the dialer/contact screen. I had this problem slightly with 1.5, but it is far worse in 2.1 including all official 2.1-based roms. The problem is present in all 2.1 based versions of Fresh and Fresh Toast.
I had this problem on every 2.1 ROM. It went away with Fresh Toast and the 710 Kernel. Now the most lagg I get on the dialer is between 1 or 2 seconds. Before it could be 10 seconds before the call placed. I am extremely happy with that overclocked ROM. Try it out if you want.
Hi everybody.
I'm having this strange issue since FROYO update (first one that came with radio). Everytime I put a new update (or anything involving going to Recovery), when my phone boots up, I can get no sound during a call (I can't hear and can't be heard also) and more, the proximity sensor is not working either (screen remains lighted when close to ear).
If I put the phone on speaker, I can hear the other and I can be heard. Looks like the upper part of the phone is not working. The only solution I found until now is to turn the phone off, take out the battery for a minute or two and then, when I start the phone, everything is back on its track.
I've tried everything, going back to stock, getting the new (now old) FRF85b signed from Google (with radio in it). I received no errors during updates, I did wipe everthing, but the problem is still there.
Today I've updated to FRF91 and after the phone booted up, same problem.
Could be the radio of FROYO? Anyone else have this issue?
Regards,
Alin.
I'm having this exact same problem and I'm kind of freaking out because I have an unlocks bootloader and no warranty, however this just happened to Me today and I've been on froyo for almost two months
ok so i just solved my problem... by smacking the speaker end of my phone on my hand a few times..
I just have updated my mobile from 2.2.1 to 2.3.4, i used this forum tutorial - http://forum.xda-developers.com/showthread.php?t=1139050
I have issue - my phone is turning off for no reason, you know i don't have lots of apps only fb,twitter,skype and 'advanced task killer'
actually when I am doing Skype video calls, writing SMS or anything else my phone just changed to 'black screen' every couple hours and afterwards my Samsung turning off with sound. To turn on I need take battery off and then into back then he allow to turn on...
before I updated I had little bit similar situation, my phone had 2.2.1 version and i didn't have black screen, but my phone just had 'freezing' for 10 sec or more...
what's problem for? what's your suggestions ? thank you a lot.
Ed
I have this issue as well, although it doesn't happen as much since I upgraded to gingerbread. I did have it happen once the other day. I was listening to music and I needed to make a call and when exiting the music app, it froze. It then went black and I had to take battery out and put it back in. It's annoying if you got a otterbox case on it with two layers. I had heard updating to gingerbread stops this but so far I don't think it's 100%. I use my phone as my alarm and one time it went dead with a full charge and I was almost late for work.
Let me know if you figure something out.
what can say experts about our issue ?
I will take some day my mobile to repair centre.. it's sad if couple of people have same issue and nobody can tell us the problem reason.
Try to flash a custom kernel and see if it the problem is still there
can you tell me or give information what's is 'flash custom kernel' ?
I have also encountered this problem, very frequently if i may add.
the problem actually first occured a few months ago, after i updated my firmware to gingerbread.
In my case the phone does not freeze, the screen wont turn on or respond to any gestures (hardware/capacitive button won't too), however any running process still runs, in specific i can still recieve phone calls, or at least hear the ringer.
I know of many other people that encountered this problem, all came from different ROMs (MIUI, SH 3.5 and up, Stock, PilotX etc..) and i, for one, can say that in the past two-three weeks it atarted appearing a few times a day.
So - does anyone have any ideas for the nature of this BUG??
BTW I use the i9000t which i own for over 7 months now.
Same problem
Hi, I have the same problem here.
and have seen this myself on stock roms too.
It doesn't happen very often (only once on my phone for now) but it is getting me pissed off as no one knows the nature of this BUG.
could it be a problem with the latest 2.3.4 version ? or an update of one of the applications?
I don't have too many apps on my phone only skype and 2-3 games.
the only thing I can think of right now is that all people who had this bug had skype on the phone but I don't really think it's from that.
Hi, And-roid if u ll update to 2.3.4 your mobile will working deffo better, i suggest you update your mobile to 2.3.4
Hey eddys, i have 2.3.4 for over two months now, and the problem just go worst...
Hi eddys,
I have the 2.3.4 (and my brother and sister in law have it too with a stock rom).
this is happening on all roms and all kernels...maybe a problem with the 2.3.4?
I don't know but it is very weird, no one has an answer for this....
edit:
just checked this with my phone supplier and of course they have no idea what so ever about this bug.
come to think of it they didn't even know how to fix my brother in laws "problem" when the 3G internet didn't work (settings-->wireless and network-->mobile network--> check the V on Use packet data ) so no surprise there.
Anyone???
Maybe theres another forum that this problem should be posted at??
I have this bug too, but only while tethering. I've found a solution to the tethering related crashes - after you start tethering, go to the SuperUser settings, and disable root permissions for android wifi tether. Your phone shouldn't crash anymore.
hey zyczu,
unfortunately, I do not use tethering at all, do you suggest i should disable ALL root permissions?
This bug is really getting on my nerves!!!
Everything else, but this, is working great...
Since upgrading my i9000m to 2.3.3 through Kies, my phone has exhibited similar symptoms 3 times: freezing, not responding to touch etc.
The first time I had pulled the battery when it did this, but the 2nd time I had just put the phone down a minute or 2 earlier so display was off so didn't notice it(about 2 weeks ago). And the 3rd time(today), I was using it at the time, and so started taking off my rubberized case, only to have it restart before I got the chance to pull the phone back off.
Startup took much much longer than normal, which I recall the startup was similar during the 2nd "freeze & reboot". For some reason today, I randomly though maybe its an OTA update so I checked "Settings..About Phone" and found my kernel version listed as:
Code:
2.6.35.7-I9000UGKG3
[email protected]#2
I have no idea what it was before, but September 8th was 2 days ago... It is possible it said that before today's restart but no idea. I have a PIN on my SIM so when starting up have to enter PIN for it to work, but on these auto restarts I never got asked for my PIN so it could have restarted other times too without me noticing(ie. middle of night).
Hmm, mine used to something similar when I would leave Bluetooth on but would move out of range of a paired device. After a few minutes it would just shut down or stop responding. Haven't had that issue since moving to Milkys rom.
hi guys, i just used this tutorial http://androidadvices.com/how-to-up...0-to-stable-gingerbread-xwjvh-2-3-3-firmware/
first I installed 2.3.3 XWJVB then 2.3.3 XWJVH
just doing step by step...
my phone was working fine 2days then i had same issue and then I changed to original SAMSUNG battery and it's working perfect.
try this..
p.s. what kind of batteries you have 'original' or 'non-original' ? thank you
madmigs:
I did not notice the kernel version ive had before, however i took my phone to a service center today, and for what i can see i have the same version as you do, take aside the i9000t instead of i9000m...
eddys:
Ive been using different batteries orig/non-orig on and off, although since ive noticed it hurts performance i stopped doing that, do you suggest that this might be the cause of the problem?
If so, the factory wipe i just did (formatted the internal SD card) should do the trick.
try reading this it helped me since i turn the wi fi off when i go out
http://androidforums.com/samsung-galaxy-ace/312084-randomly-turning-off.html
Are you guys experiencing turn-off issue while phone is in the locked state. I mean you locked the screen and then after a while when you picked it up for unlocking it was powered off. If anyone has this issue, then I found a solution. Just let me know
my turning off issue went back and it's getting every time more annoying, I don't know what to do...
I have been having troubles with my O2X ever since I did the LG online upgrade to baseband 0725-V10? with Froyo.
The main problem was dead periods for approximately 3 to 4 seconds while on calls.
I tolerated this and waited for the official LG Gingerbread update thinking it would fix the problems.
After upgrading to Gingerbread, not only did the dead periods continue, but I had a few new problems:
- people were sending me SMS messages which never arrived
- people would try to call me and get a disconnected signal
- I would occasionally get failed SMS messages when trying to send
- I would occasionally get a dead tone when trying to make a call
- people were complaining that they could hardly hear me during a voice call
Last weekend I decided to try fixing it myself.
I followed Paul's instructions and back-graded to the old 0622-V20a baseband for Gingerbread to see if this would fix things (I left LG Gingerbread on the phone).
I thought I had smashed the problem until today... when I had the phone tethered to my notebook, the phone "locked up" and would not allow me to call or send an SMS.
Going in and out of airplane mode was enough to fix this... but it was very disappointing that the phone is still not working properly.
In addition, for some reason, the phone now sometimes switches to a strange screen after sending an SMS.
I am afraid to forward-grade to 0725 again because it seemed to be worse than 0622.
Does the problem sound like the baseband, Gingerbread or other?
I have downloaded 0725-V20l and 0725-V20q and am toying with the idea of installing one of them.
Judging by the symptoms, does anyone know whether one of these two basebands would cure the problem?
If not, do I have to bite the bullet, root the phone and lose warranty, and maybe install Modaco or another version of Gingerbread?
Thanks