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
Related
Hey guys,
I updated my SGS to Froyo 2.2 yesterday and it all went smoothly (at least I thought it did). i used Odin to flash the Froyo 2.2 update and it did. Everything was going fine and I rooted the SGS and applied the one click lag fix (via the OCLF app).
The problem lies with answering incoming calls. When someone calls me it disconnects the call before it comes up on the screen, and shows a no-service icon. This then disappears after a few seconds and the phone returns to its "normal" state as if the phone call never took place. i then get a call reminder text from my carrier (Orange) which says I have a missed call from whoever rang me.
I have searched for hours and not come up with anything useful so I am really hoping you guys will be able to shed some light on the situation.
Thanks for your time,
Charles
I'm postivie i received two text, from my self, and my friend sitting next to me; They were delayed until i made a phone call. Any fixes? Surely would appreciate it!
Rom - Stock 2.1 Rooted
I'm thinking of going back to Cyanogen 6.1 when this problem is fixed
Thanks!
Are you going through a SMS app, like Handcent, or using the stock messaging program? I had a huge delay in sending/receiving texts when I used those programs. If you are using a non-stock program, try using the stock one to see how it responds first.
Yeah, i am using the stock app, but ill try using handcent and see if it works like that
Sorry, Handcent was the one giving me problems, not the stock app. How is the other data flowing, like browser and what not? Seen any drop in data coverage or anything? Do you have the newest baseband radio?
jlopez512 said:
I'm postivie i received two text, from my self, and my friend sitting next to me; They were delayed until i made a phone call. Any fixes? Surely would appreciate it!
Rom - Stock 2.1 Rooted
I'm thinking of going back to Cyanogen 6.1 when this problem is fixed
Thanks!
Click to expand...
Click to collapse
Do you have a "low space" warning? I know I've had problems receiving mms/texts when I'm low on internal space. Once I cleared up the space (>19MB Free I believe) by uninstalling a bunch of apps I never use, all the texts came in
Just a thought
Well, i got it fixed, went to the sprint store, (unrooted of course) and they fixed it within an hour, they reset the entire phone, not the same reset as Settings>Privacy>Factory Data Reset.
text and phone calls not getting through
my wife and i both got HTC incredible with Verizon service, this been almost two months ago. my phone is completely awesome, hers on the other hand has an issue her phone will stop receiving text, and or phone calls out of the blue. we will be texting back and forth and all the sudden hers just stops getting my text, so i will call her and it will ring on my end, till her voice mail picks up. this has happen few times a day ever since she has had the phone. if she makes a call out or restarts the phone then she will get all the texts, and voice messages at once. this happen with stock phone apps and ones like handcent. it happen when phone was s-on and after i rooted and installed new kernels and all that jazz. i have talk to Verizon and they talk me through reset and few other things but still doing it. guess i am going to have to see about taking it in, unless anyone has any other advise i have not thought of. all of her software versions are same as mine.
Azag Thoth said:
my wife and i both got HTC incredible with Verizon service, this been almost two months ago. my phone is completely awesome, hers on the other hand has an issue her phone will stop receiving text, and or phone calls out of the blue. we will be texting back and forth and all the sudden hers just stops getting my text, so i will call her and it will ring on my end, till her voice mail picks up. this has happen few times a day ever since she has had the phone. if she makes a call out or restarts the phone then she will get all the texts, and voice messages at once. this happen with stock phone apps and ones like handcent. it happen when phone was s-on and after i rooted and installed new kernels and all that jazz. i have talk to Verizon and they talk me through reset and few other things but still doing it. guess i am going to have to see about taking it in, unless anyone has any other advise i have not thought of. all of her software versions are same as mine.
Click to expand...
Click to collapse
You might have better luck asking on the dinc forums.
-----
Sent from my CDMA Hero. I got some hot Gingerbread-on-Hero action here!
not just a dinc issue...!?
yea, i know, i put it here because, it seems like same issue this guy was having and i have been searching around and have found many instances of the same problem on many different android phones.
i am un-rooting it and reinstalling the original software and taking it into Verizon tomorrow to see if they can do anything. should have done it sooner but every time i would try a fix it would seem like it was fixed for a day or so and then back to the same thing.
i will copy it over there just for posterity, and hopefully i can amend it tomorrow evening with the fix and a solved!
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...
Ok well I had a post before that I was having problems texting after update and root. well we thought it was the phone so verizon sent me a new one. I can receive perfectly fine but I cant send even on the new phone. I got the phone yesterday afternoon got it all set up on gingerbread rooted it then flashed with gingervolt v 1.2. Everything was working great last night then first thing this am bam no texting again. I got the v7 tot file and re flashed and it seems to be working again. For how long who knows but I am hoping someone may have a little info. Verizon has a ticket on it but something tells me it wont go anywhere.
jfl14609 said:
Ok well I had a post before that I was having problems texting after update and root. well we thought it was the phone so verizon sent me a new one. I can receive perfectly fine but I cant send even on the new phone. I got the phone yesterday afternoon got it all set up on gingerbread rooted it then flashed with gingervolt v 1.2. Everything was working great last night then first thing this am bam no texting again. I got the v7 tot file and re flashed and it seems to be working again. For how long who knows but I am hoping someone may have a little info. Verizon has a ticket on it but something tells me it wont go anywhere.
Click to expand...
Click to collapse
Are you using any 3rd party programs for texting or just stock?
I've had this problem before but only with a single person, my uncle, who uses AT&T (Only person with AT&T I text. AT&T has horrible service in my area so almost no one has them here) To make it so he'd receive my texts, I would have to completely delete my text thread and send a new message. He's the only person I've had problems with and deleting the thread fixes it every time.
Perhaps Re-flashing is working because in the process it is deleting your thread? Hope this helps!
I wish it were that simple when it goes it goes and i cant text anyone
So I am guessing no one has this issue with rooting or gingervolt? I am just curious because I love the speed and stability of gingervolt but I have been afraid that its somehow the cause. Now using the tot file v7 restores it to stock right so if it were a problem with the root or gv 1.2 this would get rid of it because its 100% stock right?
http://forum.xda-developers.com/showthread.php?t=1331603
Your previous post (For other users)
I've been lurking the gingerbread mod forums a lot and this is the first I've heard of this specific problem. Though that doesn't mean someone else isn't having the same problem.
You only get stuck when going into Gingervolt, but V7 seems to work for you? Have you tried staying in V7 w/o gingervolt for a few days just to see if the problem comes back or not?
Been on just straight v7 and it did it again man this is getting frustrating
I've had this problem on and off with the phone ever since i got it (so stock v4, R1.5, GV1.2). For me, it occasionally sits with the outgoing arrow moving, as if it were trying to send in area with no service. The workaround that i've used has been going to airplane mode which sometimes works, or more frequently, eating a reboot. Sometimes this results in them receiving duplicate texts. when i complained to Verizon they claimed it was common...
pendragon11 said:
I've had this problem on and off with the phone ever since i got it (so stock v4, R1.5, GV1.2). For me, it occasionally sits with the outgoing arrow moving, as if it were trying to send in area with no service. The workaround that i've used has been going to airplane mode which sometimes works, or more frequently, eating a reboot. Sometimes this results in them receiving duplicate texts. when i complained to Verizon they claimed it was common...
Click to expand...
Click to collapse
I used to have this issue, but it either resolved itself or something I did fixed it, but I have no idea what that something might have been.
I'm currently waiting on a replacement phone due to my USB connection no longer working, so we'll see if this problem makes a comeback. If you see me on IRC feel free to hit me up...I have some vague ideas as to what I might have changed that eliminated the issue, that's not a service guarantee though.
Looks as though its time to change forums. Verizon is switching me to a droid charge cant wait to see how this goes
Hello!
My first thread on this one of a kind forum! So here's my problem: sometimes, when I get a call, the phone lights up and shows the caller name and call receiving interface, but no matter how many times I swipe left or right, it hangs and eventually the call drops. But on the other side, the call keeps on ringing. Which means the person on the other side thinks I am a lazy bum who never picks up :| (ie. My mother :|) There are good days and the bad days, meaning, I experience only one or two call drops on some days and then there are days when every freaking call gets dropped.
Solutions I have tried:
1) I noticed the problem first when I updated my phone to lollipop (official update). So I figured maybe the update was at fault. When the problem got severe I decided to roll the version back to kitkat. So I unlocked the boot loader and flashed the firmware.
2) Unfortunately, the problem persisted even then. It's important to understand this problem only started after the update. First four months with original firmware were total bliss.
3) Since even the original firmware gave me a lot of hell I decided to bid adieu to the whole institution of moto firmware and flashed cyanogen 12. The problem is still sometimes evident. Not as much as the moto firmware. But it's still there.
What to do? Is my hardware at fault? I hope not. If not the hardware, then how to fix this software problem? And why is it happening in cyanogen if it's a moto firmware issue? What can I do? Please help! Thanks.