Related
So just being real brief, gederom on my Kindle Fire. Works great, no issues but for a WiFi issue. When wandering away from one access point and towards another it won't hop unless it completely loses the signal to the first. This means that usually I'll be standing on top of one at the end of my house while it's still talking to another that's barely hanging on without even a single bar. I'm not sure if this is an issue with the rom or if there was something the stock Kindle Fire rom was doing to automate the process.
Is this occurring due to a bad install or is this just a current issue, and is there an app I can get that would solve this problem for me?
Any help is much appreciated.
Toxeia said:
So just being real brief, gederom on my Kindle Fire. Works great, no issues but for a WiFi issue. When wandering away from one access point and towards another it won't hop unless it completely loses the signal to the first. This means that usually I'll be standing on top of one at the end of my house while it's still talking to another that's barely hanging on without even a single bar. I'm not sure if this is an issue with the rom or if there was something the stock Kindle Fire rom was doing to automate the process.
Is this occurring due to a bad install or is this just a current issue, and is there an app I can get that would solve this problem for me?
Any help is much appreciated.
Click to expand...
Click to collapse
I'm pretty sure that's just how Android was built. I cannot think of any devices at the current time that can connect to more than one wifi at a time. Also, if this feature was implemented, it would probably create a pause in internet connection which could be very annoying if you were on a Skype call or were downloading a file.
jji7skyline said:
I'm pretty sure that's just how Android was built. I cannot think of any devices at the current time that can connect to more than one wifi at a time. Also, if this feature was implemented, it would probably create a pause in internet connection which could be very annoying if you were on a Skype call or were downloading a file.
Click to expand...
Click to collapse
I don't mean connecting to multiple access points, but disconnecting from the one that has the very poor signal, and hopping to the nearest one with a full signal. The stock Fire OS did it. It really seems like it should be something that every wireless device is capable of. I guess I'll look at wireless configurations and see if there's anything about how aggressive the card is when finding better signals to attach to.
I've not had that problem with my GedeROM installation, but then again, I don't have multiple access points. Try a different ROM. If this feature is very important to you, you might even consider switching back to the original ROM, or the MoDaCo ROM which is stock with Play Store.
New user, first post, if I am missing info then I apologize.
I have the tmobile galaxy s 3 SGH-t999.
Started looking around at different roms, etc, ended up with trying the cyanogenmod 10 first.
Did the required steps, used oden to load the clockworkmod recovery.
Wiped/factory reset, then loaded up the rom. Seemed to work pretty well other than some issues with the cam crashing (seperate issue which I researched and believe I have the answer to). But overall the problem was that intermittently the inbound audio on calls sounded robotic, and reverberating. Also dealt with 4 hour battery life. Tons of info to address later when this issue is corrected however.
Have been digging around on forums, and see this issue, but no articles yet (that i have found) addressed for the SGH-t999.
Ended up re-wiping the phone and put on the liquid smooth rc9 (d2tmo).
So far it appears i am having basically the same exact issues that occurred in cyanogenmod. If I reboot the phone, it will continue. Then for whatever reason the next few calls or so later that are sent or received it sounds fine. Then back to robotic.
End user can hear me fine. The audio issue is just for inbound voice.
Tried to factory reset again, still the same issue.
I have installed the google pack to be able to use play store, etc. Perhaps this is causing the issue?
I did try to get the log cat, but could not replicate the issue while running it, so I am not sure if it would be of any use or not.
Also, this issue does not make a difference whether bluetooth is enabled or not. Am not doing wifi calling, have not tested that yet.
Again very sorry if this article is incomplete.
Thanks in advance for the help!
Resolved
tsm233 said:
New user, first post, if I am missing info then I apologize.
I have the tmobile galaxy s 3 SGH-t999.
Started looking around at different roms, etc, ended up with trying the cyanogenmod 10 first.
Did the required steps, used oden to load the clockworkmod recovery.
Wiped/factory reset, then loaded up the rom. Seemed to work pretty well other than some issues with the cam crashing (seperate issue which I researched and believe I have the answer to). But overall the problem was that intermittently the inbound audio on calls sounded robotic, and reverberating. Also dealt with 4 hour battery life. Tons of info to address later when this issue is corrected however.
Have been digging around on forums, and see this issue, but no articles yet (that i have found) addressed for the SGH-t999.
Ended up re-wiping the phone and put on the liquid smooth rc9 (d2tmo).
So far it appears i am having basically the same exact issues that occurred in cyanogenmod. If I reboot the phone, it will continue. Then for whatever reason the next few calls or so later that are sent or received it sounds fine. Then back to robotic.
End user can hear me fine. The audio issue is just for inbound voice.
Tried to factory reset again, still the same issue.
I have installed the google pack to be able to use play store, etc. Perhaps this is causing the issue?
I did try to get the log cat, but could not replicate the issue while running it, so I am not sure if it would be of any use or not.
Also, this issue does not make a difference whether bluetooth is enabled or not. Am not doing wifi calling, have not tested that yet.
Again very sorry if this article is incomplete.
Thanks in advance for the help!
Click to expand...
Click to collapse
Ok, after 4 different roms, and lots of testing, I finally figure it out.
Using Voxer caused the issue. As soon as a voice message is sent using voxer, the problem starts immediately, and is correct by a reboot. Issue immediately returns once Voxer is used.
Any idea of how to work around this, besides the obvious? =)
Since I upgraded my AT&T Galaxy S3 with the official Jelly Bean update last week, my bluetooth pairing with my car has not worked.
At first, I was continuing to use the existing pairing which was set up and perfectly working in ICS. Whenever I made a call from my car ('09 BMW 3-series, bluetooth phone via built in nav system), there would be a loud pitch sound when the call was answered and then connection lost.
So I unpaired, and re-paired.
But now it does not work at all. Connection keeps dropping every few seconds. I have not even managed to get the data sync (transferring of contact data from phone to car) to complete.
This is beyond me. Jelly Bean is great, but it is not worth the price of not having properly functioning bluetooth.
Any suggestions? Anyone with similar issue? Is it possible to somehow roll back to ICS?
I know this is a typical response for any issues after an upgrade, but have you tried a factory reset?
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.
nsmith4 said:
I know this is a typical response for any issues after an upgrade, but have you tried a factory reset?
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.
Click to expand...
Click to collapse
Thanks for your response.
I have not (yet) tried a factory reset, was sort of hoping to avoid the hassle of having to restore my data and apps. But I will eventually resort to it, if nothing else can fix it.
Good suggestion with regards to erasing from car memory. I am not sure if or how that can be done, but I will try and look through the settings to see if I can. (what I have done so far is just "remove" the device from the list of paired devices...
nsmith4 said:
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.
Click to expand...
Click to collapse
Pretty sure this is the actual cause of your problem.
HiKsFiles said:
Pretty sure this is the actual cause of your problem.
Click to expand...
Click to collapse
I went through all possible options in my car's nav system (xDrive) and I do not see any options to delete the car's memory.
So the only option as far as I know is to remove the device from the list of paired devices before pairing it again. And I tried that already...
Look through All Applications in Application Manager for BT share. Wipe data for that. Be warned this should wipe all your bt pairings.
Ok. So I resorted to restoring to factory settings.
With it clean, before restoring backup (made with Titanium), I went to my car and paired.
It worked - it synced the (very few, AT&T default) contacts, and no dropping (as far as I waited, a few minutes).
This was good news.
So I went back up and restored all app data, signed into Google account to sync all contacts etc.
Then back down in car and connected.
Problem is back It won't sync the contacts and continously drops and reconnects.
Well at least I have a reference point to go back to now and perhaps take one step at the time.
I was thinking next step is to restore to factory settings again, then ~only~ add google account to sync up contacts, then try. If that works, restore one app at a time to see if I can isolate the issue.
I will do this tomorrow.
mrhaley30705 said:
Look through All Applications in Application Manager for BT share. Wipe data for that. Be warned this should wipe all your bt pairings.
Click to expand...
Click to collapse
I just did this. I am however too tired for the day and will check first thing in the morning, if this resolved it (as I am back in the problem state) - before resetting and starting all over (ref. my above mentioned thoughts of how to do a gradual restore)...
Thanks all for your input so far - I cannot tell you how much I appreciate it. This forum rocks so far.
/Lars
Progress this morning:
First of all, I tried as suggested clearing data for Bluetooth Share. Didn't fix the problem.
I know now that if I pair the phone and connect after factory reset, with the contacts list on the phone at default/almost empty (11 pre-defined AT&T numbers), it works.
So what I did this morning:
I factory reset the phone again. Then I added my Google account to sync up contacts list from my GMail account.
I ~only~ did this. No apps installed or restored.
Paired and connected. And I have the problem.
So this seem to somehow be caused by my contacts list after it has synced up with Google.
Any suggestions?
I am thinking that if I cannot get this resolved, I want to roll back to ICS. Having no functional bluetooth pairing with my car is not an acceptable tradeoff, no matter how great JB is. Is there a way to roll back? Can I get the official ICS ROM from AT&T, if needed?
But of course - this will be my final solution; I much prefer to get this resolved. I am open to any suggestions re. my contacts/google account.
You have an old problem. There are stock roms and instructions to do it stickied on the original development forum. I suggest you download the jb version of your carrier and flash that through Odin first.
If that doesn't work, then go back to ics
Sent from my SGH-I747M using xda app-developers app
Deoxlar said:
You have an old problem. There are stock roms and instructions to do it stickied on the original development forum. I suggest you download the jb version of your carrier and flash that through Odin first.
If that doesn't work, then go back to ics
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Thanks for your feedback.
Can I ask, if you know where this problem is perhaps discussed?
I looked in the developer forum, but must admit I am confused which thread/which ROM you are referring to. Are you talking about a modified stock ROM? I would greatly appreciate a link if it is...
Today's update:
At work we have a Galaxy S3 AT&T device (identical to my own) for testing purposes.
I just upgraded it to Jelly Bean today and then added my gmail account to it, paired to my car - and the same problem.
So at least that rules out an issue with my specific hardware/phone.
I also tried using a Galaxy Nexus (Verizon version) from work. Issue did NOT happen.
I then flashed my own phone with the stock Jelly Bean ROM downloaded from here:
http://forum.xda-developers.com/showthread.php?t=1739426
Same issue happens
So my final solution (at least for now):
I flashed to the stock Ice Cream Sandwich ROM (downloaded from same place as listed above).
It works now.
Funny how one can be so happy with a downgrade, but I am
Thanks all for all your input.
I am still open to any suggestions (as I would love to be on Jelly Bean in the future), and I have an easy way to test possible solutions on my work test device...
Thanks again!
Lars
Hey, I am having Bluetooth problems as well. I have the sprint s3 stock jb. My blue tooth will not connect to my moga controller. Everything I have been reading points at it being a software issue on Samsung JB devices. Can anybody else confirm this?
Sent from my SPH-L710 using xda premium
Aren't the bluetooth "drivers" in the kernal? Perhaps using a different, or going back to a stock kernal.
I was having a similar issue with my phone not automatically connecting with my car. It would connect if I cycled BT off then on. All this on Tasks 4.1 rom & KT's kernal.
Flashed with the new 4.2 rom & kernal and it seems to be fixed.
Just curious, did the OP ever try a factory reset? I'm on Blackjelly, which is a ROM heavily based on AT&T stock JB and I have no issues with my Bluetooth whatsoever. However, I do have the KT747 kernel installed, which has its own set of bluetooth drivers.
crazililazn said:
Just curious, did the OP ever try a factory reset? I'm on Blackjelly, which is a ROM heavily based on AT&T stock JB and I have no issues with my Bluetooth whatsoever. However, I do have the KT747 kernel installed, which has its own set of bluetooth drivers.
Click to expand...
Click to collapse
I have a Verizon S3 (running stock) and the same problem is happening. I've even tried a factory reset but that doesn't seem to have helped although I'm still testing it (need to go drive for a while). My car is a 2010 Audi A4. I've spoken to both Samsung and Audi and both tell me it's not their problem. I'm hoping Samsung updates the phone with a backwards compatible BT driver or Audi upgrades their driver. I am not happy.
EDIT: I drove some more today and bluetooth only dropped once. The strange thing is that while I am driving I only see 2 bars on my dashboard screen when the phone shows 5 bars. I would "assume" that the phone is the most accurate signal meter. In any case, everything "seems" to be working better although not as well as before.
Bluetooth in car only has voice audio, no ability to control the phone
Ansextra said:
I have a Verizon S3 (running stock) and the same problem is happening. I've even tried a factory reset but that doesn't seem to have helped although I'm still testing it (need to go drive for a while). My car is a 2010 Audi A4. I've spoken to both Samsung and Audi and both tell me it's not their problem. I'm hoping Samsung updates the phone with a backwards compatible BT driver or Audi upgrades their driver. I am not happy.
EDIT: I drove some more today and bluetooth only dropped once. The strange thing is that while I am driving I only see 2 bars on my dashboard screen when the phone shows 5 bars. I would "assume" that the phone is the most accurate signal meter. In any case, everything "seems" to be working better although not as well as before.
Click to expand...
Click to collapse
Hi guys,
I have the same problem.
Details:
Phone: GALAXY S3 I747M
Carrier: Rogers
What happened?
Let me start by saying Bluetooth was flawless before moving to Jellybean (flawless means it would work consistently EVERY time on all featureS). Data and Voice between my Car (2010 Audi A4). I consider data the phonebook information back and fourth to the car, the ability for the car to control my device (make calls, end calls, switch calls) and the number of bars for reception.
I upgraded to Jellybean, then stuff wouldn't work (Bluetooth, GPS, 3G, wifi, etc.), so I tried a few roms (I would factory reset, wipe cache, wipe delvik cache, format /system EACH time I swapped ROM's). Unable to get anything to work consistently with everything. I downgraded to 4.0.4 (Using the WanamLite ICS SGH-I747 V1.3 Android 4.0.4 ROM).
Everything started working again! EXCEPT Bluetooth. It connects with no problems, but it seems like it's only the voice part, the data part (as decribed above) doesn't...I can tell by not seeing any information go back and fourth between call logs and the wrong number of bars for reception, it's like the connection is jumbled.
Unfortunately, it's inconsistent to around 50% of the time, sometimes it DOES work.
Voice/audio through phone calls work ALL the time. IF someone calls, the car recognizes it and the audio mic and through speakers work...but the car doesn't realize it's happening enough to give me options (like ending the call from the car).
This only happened once I went from Jellybean and then went back....not sure what's happened...
Appreciate your help and thanks in advance!
rohanverma said:
Hi guys,
I have the same problem.
Details:
Phone: GALAXY S3 I747M
Carrier: Rogers
What happened?
Let me start by saying Bluetooth was flawless before moving to Jellybean (flawless means it would work consistently EVERY time on all featureS). Data and Voice between my Car (2010 Audi A4). I consider data the phonebook information back and fourth to the car, the ability for the car to control my device (make calls, end calls, switch calls) and the number of bars for reception.
I upgraded to Jellybean, then stuff wouldn't work (Bluetooth, GPS, 3G, wifi, etc.), so I tried a few roms (I would factory reset, wipe cache, wipe delvik cache, format /system EACH time I swapped ROM's). Unable to get anything to work consistently with everything. I downgraded to 4.0.4 (Using the WanamLite ICS SGH-I747 V1.3 Android 4.0.4 ROM).
Everything started working again! EXCEPT Bluetooth. It connects with no problems, but it seems like it's only the voice part, the data part (as decribed above) doesn't...I can tell by not seeing any information go back and fourth between call logs and the wrong number of bars for reception, it's like the connection is jumbled.
Unfortunately, it's inconsistent to around 50% of the time, sometimes it DOES work.
Voice/audio through phone calls work ALL the time. IF someone calls, the car recognizes it and the audio mic and through speakers work...but the car doesn't realize it's happening enough to give me options (like ending the call from the car).
This only happened once I went from Jellybean and then went back....not sure what's happened...
Appreciate your help and thanks in advance!
Click to expand...
Click to collapse
It's a know JB problem. No solution right now
Ironically, I had the same exact bluetooth problem the OP describes, but it happened with my stock ICS ROM. Made trying to call someone extremely frustrating since I have a stickshift!
The problem disappeared with my upgrade to the 4.1.1 stock ROM. I have also had no issues at all with any 4.1.2 JB custom ROM.
I believe it is a generalized issue with Android, because the problem I had with ICS was not reproducible when using a different bluetooth headset. Only my own would cause the problem. As soon as I realized that the problem no longer existed in 4.1, I began using my own headset again, and have done so without a single dropped call.
BWolf56 said:
It's a know JB problem. No solution right now
Click to expand...
Click to collapse
Thanks, but just for clarification. It was working on JB perfectly. I upgraded to ICS, thats when bluetooth with my car stopped working (with a number of other things). So i downgraded BACK to JB (stock rom) and I still have the same problem.
It's almost like the data side of the connection is all jumbled up....did ICS leave something on my phone (I did a factory reset, wipe cache, wipe delvik cache, format /system when switching back).
So I feel like it wasn't a JB problem it was an ICS problem, but reverting back to JB didn't fix the problem, so I feel like ICS left something on there that the old rom didn't overwrite. Any files I should be checking to ensure that isn't the case?
Thanks a lot!
rohanverma said:
Thanks, but just for clarification. It was working on JB perfectly. I upgraded to ICS, thats when bluetooth with my car stopped working (with a number of other things). So i downgraded BACK to JB (stock rom) and I still have the same problem.
It's almost like the data side of the connection is all jumbled up....did ICS leave something on my phone (I did a factory reset, wipe cache, wipe delvik cache, format /system when switching back).
So I feel like it wasn't a JB problem it was an ICS problem, but reverting back to JB didn't fix the problem, so I feel like ICS left something on there that the old rom didn't overwrite. Any files I should be checking to ensure that isn't the case?
Thanks a lot!
Click to expand...
Click to collapse
Umm just to clarify, firmware goes like this (in order): Eclair, Froyo, GB, ICS, JB. So JB is the latest.
Here's a JB fix for BT: https://dl.dropbox.com/u/28275651/REVERT-MY-ALSA.zip
Flash it in recovery, clear cache and dalvik and hopefully it will work.
Just wondering if these are problems everyone is facing, or just me, and if there is maybe a fix for some of them. They have been broke for MONTHS, and I can't figure out why I don't see more people talking about them, or why they haven't fixed them yet.
1. Bluetooth A2DP streaming is broke - Okay, this one I know is common knowledge, so we can skip this one. Supposed to be fixed officially by Google in 4.2.2. I can live with this.
2. The native WiFi hot-spot only works without encryption. All WiFi hot-spot apps from the Play Store are broken as well. Either you can't connect to the phone from your laptop/device, or the SSID isn't broadcasted at all, and you can't see it from anything.
3. When using a Google app that requires the microphone, whatever app you are using will crash. I have noticed this with Google Now, and most annoyingly the keyboard. The worst thing about this is that if you accidentally hit the mic key on the keyboard, the keyboard crashes, and it doesn't work again until you wipe the phone and re-install the Rom. Rebooting doesn't even solve it.
All three of these problems persist for me through out all the roms I have tried. This means CyanogenMod10.1, Kangdroid, PAC, Paranoid, Slimbean, etc. I know most of those are based on CM10.1, so that explains why they are all broke, but why have they been broke for so long, or is it just me?
Never seen #3 happen (I use it quit a bit). Wifi hotspot issue is known.
Aerowinder said:
Never seen #3 happen (I use it quit a bit). Wifi hotspot issue is known.
Click to expand...
Click to collapse
Yeah, that bug alone didn't happen when I first started using 10.1. Not sure when it started to be honest.
Update google search for the keyboard I think
mt3g said:
Update google search for the keyboard I think
Click to expand...
Click to collapse
That's very possible. It's one of the first things I try when I get the latest nightlies, so I probably try it each time before I have updated anything.
Is there any reason to think that the hot-spot issue will be resolved in 4.2.2?
Ya, and I don't know, it might be coding that is needed within AOSP, does wifi tether encrypted not work on the Nexus 4 or GNEX?
Just an update for anyone who is searching and finds this thread by some chance...
It looks like 4.2.2 did not fix the HotSpot issue, but it did fix the Bluetooth streaming. I tried the SmoothRom 4.2.2 release, to test these things.
PAC-man rom 4.2.1 is my current favorite rom, and they did somehow fix both of those issues recently. Probably had something to do with 4.2.2's release this week. So if someone is looking for a 4.2 rom with working Bluetooth, and WiFi tether encryption, you might want to give that rom a try.
It is right here:
http://forum.xda-developers.com/showthread.php?t=2015525
4.2.2 has working everything. On Liquid Illusion you need to flash a custom kernel that is updated to have encrypted hotspot.
Sent from my SGH-T999 using xda premium
ArkAngel06 said:
Just wondering if these are problems everyone is facing, or just me, and if there is maybe a fix for some of them. They have been broke for MONTHS, and I can't figure out why I don't see more people talking about them, or why they haven't fixed them yet.
1. Bluetooth A2DP streaming is broke - Okay, this one I know is common knowledge, so we can skip this one. Supposed to be fixed officially by Google in 4.2.2. I can live with this.
2. The native WiFi hot-spot only works without encryption. All WiFi hot-spot apps from the Play Store are broken as well. Either you can't connect to the phone from your laptop/device, or the SSID isn't broadcasted at all, and you can't see it from anything.
3. When using a Google app that requires the microphone, whatever app you are using will crash. I have noticed this with Google Now, and most annoyingly the keyboard. The worst thing about this is that if you accidentally hit the mic key on the keyboard, the keyboard crashes, and it doesn't work again until you wipe the phone and re-install the Rom. Rebooting doesn't even solve it.
All three of these problems persist for me through out all the roms I have tried. This means CyanogenMod10.1, Kangdroid, PAC, Paranoid, Slimbean, etc. I know most of those are based on CM10.1, so that explains why they are all broke, but why have they been broke for so long, or is it just me?
Click to expand...
Click to collapse
I've had #3 happen, and it can be fixed by clearing the data for the keyboard and the voice search (I don't remember if the voice search part was an app, but I remember looking for it). Just go to apps and wipe the data.
milesmarrero said:
I've had #3 happen, and it can be fixed by clearing the data for the keyboard and the voice search (I don't remember if the voice search part was an app, but I remember looking for it). Just go to apps and wipe the data.
Click to expand...
Click to collapse
Thanks for the info, but updating to the newest Google App from the PlayStore fixed it for me.
Your solution would probably fix the need to reflash.
Has anyone else experience their WIFI connection almost completely stop working? For the last few days either I get no connectivity at all or very slow, but every now and then for a few minutes it will run at normal speeds.
I'm stock, rooted, no custom recovery or 2nd bootloader. I've rebooted the kindle and my router multiple times. I've done a full factory reset on the Kindle. None of that helped. There's 3 laptops, 2 other tablets, and 2 phone all running fine on the WIFI so I don't think it's the router.
If anyone has any suggestions. I'd appreciate it.
Have you done any other modifications other than rooting?
soupmagnet said:
Have you done any other modifications other than rooting?
Click to expand...
Click to collapse
I've got the google services installed to get the Play Store working, and installed NOVA launcher. I think that's all.
Well, I thought it may be something with the drivers gone funny, so I finally got around to getting 2nd bootloader and recovery going. I tried CM10, I tried Hashcode's stock ROM, and I tried the full restore from the KFHD First Aide tool. All the same results. I'll get intermittent bursts of full speed, but for the most part every web page, market request or attempt to stream something times out.
When I look at the WIFI settings in the kindle, it pretty consistently says 39Mb link speed. My phone is connecting at 26Mps, but everything works no problem as do all the other devices.
I know I'm heading into O/T territory, but does anyone know what Router Settings to check for that may be limiting just one device? Failing that I'm going to have to return to stock and see if I can get some help from Amazon.
Thanks in advance!
I'm also having some wifi issues like you. Mine's 8.4.3, rooted, with google play store and a few other things. Like you, all my wireless settings seem to be ok, several other devices use the wifi without any problems. And like you, I've had CM 10.1 installed in the past and I'm back on the stock Amazon rom.
One hunch that I had yesterday was the following: I bought a cover for my Kindle that can cover the back and front of the kindle. When I use it normally, I fold the front cover around to the back of the device, meaning there's a double cover on the back when in use. I thought to myself, maybe the cover is blocking the wifi signal or something... I then tried changing the cover to "kickstand" mode, so that it wasn't against the back of the device. It seemed to help, but I still need to do more testing.
If you have a cover then maybe try taking it off and testing the wifi. If not then I'm out of ideas, but I'm not sure how it could be a software problem, since you've tried different ROMs with the same results.
Apparently, after a quick google search, it looks like a lot of people are having wifi problems with the kindle fire HD. Perhaps the following thread will help: http://www.mobileread.com/forums/showthread.php?t=210002. It mentions changing some router settings. I'll try it on mine when I get home.
Make sure that QoS is disabled on your router.
Greek2me said:
Make sure that QoS is disabled on your router.
Click to expand...
Click to collapse
Thanks for the suggestions. No help unfortunately.
I need to get somewhere I can try connecting to a different router. If that's still unusable, I think it's time for the service call.