When making a call through Bluetooth with joyroom airpods, the airpods keeps disconnect and connect again. And this makes the call annoying. This issue happened when updating to the latest update. This issue never happened with me since I bought the air pods in January 2021. Please help.
Start with a network reset.
Clear system cache.
blackhawk said:
Start with a network reset.
Clear system cache.
Click to expand...
Click to collapse
Done these steps and nothing happened
Was it a major firmware upgrade?
If so, factory reset otherwise this likely won't help.
Try a hard reboot.
You can play with it and try to sort it out.
Otherwise flashing the last known good version is the only option.
Now you know why I don't do updates and upgrades... if you have a fast, stable platform that's fulfilling its mission, let it be.
blackhawk said:
Was it a major firmware upgrade?
If so, factory reset otherwise this likely won't help.
Try a hard reboot.
You can play with it and try to sort it out.
Otherwise flashing the last known good version is the only option.
Now you know why I don't do updates and upgrades... if you have a fast, stable platform that's fulfilling its mission, let it be.
Click to expand...
Click to collapse
This is happening after last update from 2 days ago.
However, how do I flashing the last known good version as I'm new at these things.
agohary30 said:
This is happening after last update from 2 days ago.
However, how do I flashing the last known good version as I'm new at these things.
Click to expand...
Click to collapse
I'm newer than you at flashing or at least soon will be... lots of people here who know how to guide you through it here
Just make sure you didn't miss a setting that got altered or upgraded.
Related
I have been discouraged from the Froyo ROMs for a while due to the problem with calls being dropped but then suddenly they aren't dropped. I really like the Froyo ROMs though so I decided to try it again and the first day I experienced it yet again on CELB 3.6. It only happened a couple of times then 3.7 was released and I flashed that and it happened again on the first call LOL. I then started looking through things in the settings and under the mobile data setting I turned on National Data Roaming, since then I have been on several calls ranging from 20 minutes to an hour and have yet to experience this problem since turning data roaming on, some of these calls were in areas that I know for certain I had the dropped and reconnected calls happen before. Maybe some others may want to try this out and see if it helps you as well. Hope this helps some people that have experienced this as well.
Has anyone else tried this yet? And if so, has it made any difference for you as well?
happens to me all the time. kaos froyo, tazz froyo, celb froyo, nonsensikal froyo. Only at my house tho. i have 3 bars there. not sure whats going on there but i have learned to live with it. Wont be long till we are on 2.3 anyway. deal with it for a month. by the new year kaos should have a completley functional 2.3 rom. maybe without camera, but still fully functional.
I've been messing around with the national data roaming for about a week now. When I have national data roaming enabled it doesn't happen, if I turn it of it does. Try enabling it and see if it makes a difference for you too. It's located under settings>wireless & networks>mobile networks
will enable it and see if it happens tonight.
Same here, after enabling it I have had no stopped call issues. Its been about a week, so far so good
Good information, I think I'm gonna try it, but first does this affect my billing at all? I'm on my parents plan and don't want to give them a heart attack if I incur extra charges
Scott586 said:
Good information, I think I'm gonna try it, but first does this affect my billing at all? I'm on my parents plan and don't want to give them a heart attack if I incur extra charges
Click to expand...
Click to collapse
It shouldn't but that would depend on what your plan is. If you have a nationwide plan with unlimited data and no roaming charges then it won't. I'd suggest checking on your plan first. Just a thought though lol.
CondemnedSoul said:
It shouldn't but that would depend on what your plan is. If you have a nationwide plan with unlimited data and no roaming charges then it won't. I'd suggest checking on your plan first. Just a thought though lol.
Click to expand...
Click to collapse
I also have this problem happen on non-Verizon based ROMs such as RCMix.
The call says it's dropped, but the person on the other end can hear everything that's going on.
Then the phone rings you back, but in reality, they were hearing everything going on around you in the meantime.
I almost lost my girlfriend because of it. Immediately flashed away from said ROM. Had the same problem with Froyo ROMs.
May switch to a CM ROM now, if this is a serious fix. Thanks very much for this.
I was hoping this would be a fix - I upgraded to CELB 3.9 a couple of days ago, and turned on National Data Roaming.
Tonight I had the same behavior - temporary call drop and reconnect along with the same symptoms that usually accompanies it (speakerphone mode toggles off, phone vibrated, yada yada).
Confirmed through examination of the (uncompressed) SYSTEM_TOMBSTONE file in /data/system/dropbox/ that yes, the usual cause is present: segfault crash of the "rild" process.
Rats! I was hoping this might provide a fix... but apparently not for me.
bftb0
bftb0 said:
I was hoping this would be a fix - I upgraded to CELB 3.9 a couple of days ago, and turned on National Data Roaming.
Tonight I had the same behavior - temporary call drop and reconnect along with the same symptoms that usually accompanies it (speakerphone mode toggles off, phone vibrated, yada yada).
Confirmed through examination of the (uncompressed) SYSTEM_TOMBSTONE file in /data/system/dropbox/ that yes, the usual cause is present: segfault crash of the "rild" process.
Rats! I was hoping this might provide a fix... but apparently not for me.
bftb0
Click to expand...
Click to collapse
Sorry ut didn't work for you.... so far now im at 3 weeks without it happening to me
I have still had this temporary dropped call problem occur just as frequently on CELBFroyo 3.6 with this "fix". And most of the time I'm in my apartment on the phone for hours when it happens, and it sometimes happens more than once during these extended phone calls.
Just as has been described before: the phone looks and acts like the call was dropped, I can hear nothing but the other person can hear everything, and then after several seconds everything is back to normal.
Oh well. Thanks for the suggestion, though.
Very interesting to hear others have been having this problem. I had thought it was due to my bluetooth earphone, because it used to happen to my wife on her old earphone with a standard cell phone. However, last night I lost my earphone and the same problem occurred while on speakerphone. Although annoying, most of the time I just deal with it. I just installed radio version 2.42.01.04.27 hoping it might help. Various versions of CELBFroyo (currently using 3.9) have done it. I will let you all know if this helps and keep checking back on this string to see if anyone else finds a fix.
farmdoc said:
Very interesting to hear others have been having this problem. I had thought it was due to my bluetooth earphone, because it used to happen to my wife on her old earphone with a standard cell phone. However, last night I lost my earphone and the same problem occurred while on speakerphone. Although annoying, most of the time I just deal with it. I just installed radio version 2.42.01.04.27 hoping it might help. Various versions of CELBFroyo (currently using 3.9) have done it. I will let you all know if this helps and keep checking back on this string to see if anyone else finds a fix.
Click to expand...
Click to collapse
Seems like its touch and go now. Works for some but not for others. I haven't had it happen to me in 3 weeks now but this hasn't worked for some others where some it has. Im using the new sprint radio now, I don't know if maybe it has anything to do with what radio you have too? I just flashed this radio about a week and a half ago though. Before that I was on the older verizon radio... not the one from july ota though... the previous one.
sent from the depths of hell
CondemnedSoul said:
Seems like its touch and go now. Works for some but not for others. I haven't had it happen to me in 3 weeks now but this hasn't worked for some others where some it has. Im using the new sprint radio now, I don't know if maybe it has anything to do with what radio you have too? I just flashed this radio about a week and a half ago though. Before that I was on the older verizon radio... not the one from july ota though... the previous one.
sent from the depths of hell
Click to expand...
Click to collapse
If I recall correctly, it has been seen on multiple radios. ( Have you seen this thread? )
bftb0
bftb0 said:
If I recall correctly, it has been seen on multiple radios. ( Have you seen this thread? )
bftb0
Click to expand...
Click to collapse
Thanks for the leads to the other threads. I had not seen them.
I have not had a chance to test with the current radio installed (2.42.01.04.27), but plan to tonight. Is there a newer radio for the Eris? Looking at the version numbers of some I have seen referenced would make me believe that there are newer ones. Where do you download these?
farmdoc said:
Thanks for the leads to the other threads. I had not seen them.
I have not had a chance to test with the current radio installed (2.42.01.04.27), but plan to tonight. Is there a newer radio for the Eris? Looking at the version numbers of some I have seen referenced would make me believe that there are newer ones. Where do you download these?
Click to expand...
Click to collapse
AFAIK, this is the most recent radio and is currently what I'm using:
http://forum.xda-developers.com/showthread.php?t=853868
roirraW "edor" ehT said:
AFAIK, this is the most recent radio and is currently what I'm using:
http://forum.xda-developers.com/showthread.php?t=853868
Click to expand...
Click to collapse
Thanks! BTW what is AFAIK?
farmdoc said:
Thanks! BTW what is AFAIK?
Click to expand...
Click to collapse
You're welcome! AFAIK = As Far As I Know
Just got the new OTA, but still no Jelly Bean. I777UCLL6
IMEISV is now at version 7. No other changes I can see.
ou812bkewl said:
Just got there new OTA, but still no Jelly Bean. I777UCLL6
IMEISV is now at version 7. No other changes I can see.
Click to expand...
Click to collapse
Maybe it fixed the sod problem, one can only hope.
Sent from my Zanpakuto using Getsuga Tensho!
It looks like it updated Kies Air, and now the Facebook app won't open. I haven't noticed any other changes yet.
Hey all,
As some of you have already noted, an update is available for the Samsung Galaxy SII.
The update includes fixes for devices that may become unresponsive and/or power down while sitting idle on rare occasions. It also enhances security to protect against malware vulnerability. You will receive a notification on your phone to update.
NOTE - You must have updated to Android version 4.0 to receive notification of the new software update
From community manager on ATT forums:
http://forums.att.com/t5/Android-Di...hutting-off-in-idle-mode/td-p/3247765/page/18
What a complete waste. Sprint just pushed 4.1.2 to their gs2.
cfili said:
fixes for devices that may become unresponsive and/or power down while sitting idle on rare occasions
Click to expand...
Click to collapse
By rare, they must mean multiple times a day... hope that finally fixes the problem...
Had my hopes up for JB even though I know the phone will not get it from AT&T.
I guess it is good that they are still trying to improve the phone.
scottwood2 said:
I guess it is good that they are still tring to improve the phone.
Click to expand...
Click to collapse
There's at least as much cya and marketing motivation involved as anything else.
I previously rooted and flashed Siyah 4.3.3 which resolved my issue with the sleep of death. This seems to prevent this new update from installing as when the phone reboots it shows the Siyah boot image and then boots back into the OS, when I unlock the phone it tells me that the update failed to install. I'm not in a hurry to install an update that resolves something I've fixed through other means, but I thought I'd share for those interested.
Notmare said:
I previously rooted and flashed Siyah 4.3.3 which resolved my issue with the sleep of death. This seems to prevent this new update from installing as when the phone reboots it shows the Siyah boot image and then boots back into the OS, when I unlock the phone it tells me that the update failed to install. I'm not in a hurry to install an update that resolves something I've fixed through other means, but I thought I'd share for those interested.
Click to expand...
Click to collapse
You really shouldn't accept OTA updates unless you are 100% stock.
nimper said:
You really shouldn't accept OTA updates unless you are 100% stock.
Click to expand...
Click to collapse
You really CAN'T accept them if you remove system bloat ware or change kernels far as I know.
Hopefully it fixes the SOD problem. I was getting ready to call or go to AT&T and demand I be let out of my contract.
NBA Brawler said:
Hopefully it fixes the SOD problem. I was getting ready to call or go to AT&T and demand I be let out of my contract.
Click to expand...
Click to collapse
That's the best joke I've heard today.
cfili said:
Hey all,
As some of you have already noted, an update is available for the Samsung Galaxy SII.
The update includes fixes for devices that may become unresponsive and/or power down while sitting idle on rare occasions. It also enhances security to protect against malware vulnerability. You will receive a notification on your phone to update.
NOTE - You must have updated to Android version 4.0 to receive notification of the new software update
From community manager on ATT forums:
Link Omitted
Click to expand...
Click to collapse
This has been happening to me for the past few months, on more than "rare occassions" though. I never knew what to call it until I saw people on here refer to it as Sleep of Death. Yep, sounds about right. And it would rapidly drain my battery when it happened.
I've successfully updated, so hopefully this will take care of it. It gets VERY annoying! And all the much worse since I use my phone for my alarm, haha. I have my wife's as a backup though.
Anyone pull the modem yet?
Sent from my SGH-I777 using Tapatalk 2
I'm only a curious now, about whether this fixes the SOD. After hours on the phone with ATT and Samsung, and a few factory resets and a new phone, it was still doing it. And each time I called them about it, they'd say they were not aware of such a problem. Anyway, not an issue anymore for me, since going to Task's AOKP ROM, which got me so many better features than an ATT update ever would have - warranty or no.
The only reason why this OTA was pushed was because a ton of users were posting this issue on the ATT forums for 4 months straight. Even then ATT pushes an OTA for 4.0.4 instead of using one of the many 4.1.2 firmwares from Samsung.
c0ldburn3r said:
The only reason why this OTA was pushed was because a ton of users were posting this issue on the ATT forums for 4 months straight. Even then ATT pushes an OTA for 4.0.4 instead of using one of the many 4.1.2 firmwares from Samsung.
Click to expand...
Click to collapse
My understanding is that it is up to Samsung to produce the firmware, and because it's a carrier-branded device, I have a hard time believing that they'd do that unless instructed to.
Really? You think Samsung is the one making the decision? Its really the carrier.
Can someone pull the modem from this update? Pm or post a download link once extracted please.
Sent from my Transformer Prime TF201 using Tapatalk 2
I've been having this issue since I first flashed a LiquidSmooth ROM a couple months back, but as I've installed official CM10.1 and AOKP roms, the issue has persisted across them. Currently I have Avatar 2.13b on slot 1, AOSP r6 on slot 2 and LiquidSmooth 2.4 in slot 3 and the problem exists on all 3. Bluetooth will work fine on an initial flash, but a some point later on, it disables itself, and the only way to get it back is to wipe dalvik and reboot. Is this simply an instability of the kexec kernel, or something more. I've seen a few posts related to this, but not enough that it seems like a common issue. Any one else having this problem or any thoughts on why its happening to my RAZR MAXX xt912? Wiping dalvik isn't a huge inconvenience, as I typically only use BT to and from work, but after a long day in the office, not being able to connect my headphones can just add to my frustrations. Any thoughts or help is greatly appreciated, thanks in advance!
Did you ever make any progress on this problem? I'm having a similar, tho not identical, BT problem . . . posted it, hoping to get some idea how to approach it. Thanks
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
psudeke said:
Sorry, no luck yet. Happened today while sitting idle at my desk, no reboot, not even being used. If I run into a solution on another site, I'll update this post
Posted from along the edge of a straight Razr
Click to expand...
Click to collapse
Too bad. I was hoping to piggyback, or at least get some insight.
I like to think I'm not an idiot, but short of changing hardware I can't think of anything new to even try.
Hi, I'm new to these forums, and I'll be glad if someone could help me.
I have a Nexus 4, which has served me well for a long time. I'm not in a financial position to upgrade and I feel that the phone is still fast enough for my needs. However, I have been experiencing a very annoying issue ever since I upgraded to Lollipop back last year. The phone is currently up to date and was running a custom rom before i reverted to stock to upgrade to lollipop.
The issue is that after a while, the phone will just stop loading videos (on YouTube/Vine/Twitter). This wont be fixed until I reboot the phone. This happens almost every day and is extremely annoying. Changing from AwesomePlayer instead of NuPlayer in dev options also doesn't help. I've performed a factory reset, to no avail. Clearing cache also didn't help.
I don't know what to do any more. Any help would be appreciated.
Has anyone else noticed frequent GPS issues with the new 5.1.1 update? My D6708 either sees GPS satellites and can't triangulate, or it can't see any. I've reset the agps settings and tried all of the GPS fix apps on the play store, but nothing has worked. Any suggestions?
Yes, have noticed it since the update, both of our phones do it, only thing we have done to get it to work is restart the phone, will work for a while then stop again.
1linuxfreak said:
Yes, have noticed it since the update, both of our phones do it, only thing we have done to get it to work is restart the phone, will work for a while then stop again.
Click to expand...
Click to collapse
I've noticed it happen even after I restart the phone several times. I just downgraded back to kitkat, so hopefully that fixes the problem until Sony or the community releases a patch.
randomjoh said:
I've noticed it happen even after I restart the phone several times. I just downgraded back to kitkat, so hopefully that fixes the problem until Sony or the community releases a patch.
Click to expand...
Click to collapse
I don't think reverting back to KitKat will be with the trouble. 5.1.1 is the possibly the latest and only thing the Z3v will ever get.
randomjoh said:
I've noticed it happen even after I restart the phone several times. I just downgraded back to kitkat, so hopefully that fixes the problem until Sony or the community releases a patch.
Click to expand...
Click to collapse
Yeah don't see MM coming or any other patches from VZW or Sony.
I am just killing time with this phone (Z3v) until all the accessories get here so I can start using my BB Priv.
I also noticed this recently. It was the first time I had really used GPS since the latest update. I thought it might be related to having to reattach the back cover due to separation but now it appears it's a more general issue.
up
GigaSPX said:
I don't think reverting back to KitKat will be with the trouble. 5.1.1 is the possibly the latest and only thing the Z3v will ever get.
Click to expand...
Click to collapse
I reverted back to kitkat, and I'm still having issues with the GPS. I'm pretty sure that the problem is hardware related, so I'm going to have to just wait until my Verizon contract is up. I've read a few articles online with the GPS issues of the Z3 models in general. I'm thinking that it might have just been one of the areas they cut corners on. If anyone has a fix in mind, I'm open to try anything at this point.