Hi all,
I have a problem and maybe more experienced users might offer help:
I have successfully paired my Galaxy S2 with Audi's Bluetooth Car Phone via the rSAP (remote SIM Access Profile). I am not using the "hands-free" profile, but the full Car Phone which logs into the service provider network and disables the mobile.
When I turn on the ignition one of the following happens:
a) in 70% of all cases everything's fine
b) in 20% of all cases the connection seems to be rejected at the very start
c) in 10% of all cases the connection is terminated while the phone book is synchronized from Galaxy S2 to Audi Car Phone
b) and c) might even be manifestations of the same problem.
Using a log tool I was able to capture an error message in the phone's log: it seems that the Galaxy tries to send a data package which is not acknowledged by the Audi Car Phone. After 3 retries (ret = 3) the phone gives up frustrated and terminates the rSAP connection -> Game Over!
I have the (general) feeling that Audi's MMI Car Phone is not very responsive when just started and that due to that it might sometimes not be able to acknowledge on time. My former HTC Diamond 2 did not seem to have such a low frustration level.
Questions:
1. does anybody know a solution to this issue?
2. does anybody know how to set the number of retries to a higher value to make the Galaxy more error tolerant?
3. ...?
Help highly appreciated. One thing added: I am a newcomer to Android...
Best,
Beschinel
I thought, I'd bump this up.
Help greatly appreciated.
Cheers, Chris
Hi there! Actually I have a bigger problem than you! I have a Passat CC with btooth rsap and after requesting tge 16 digit code for the pairing, the car mfp says "Could not connect". I am really confused. galasy s 1 worked fine although sometimes it would lose the connection.
O.K. I have an update to your problem.
I tried using S G 1 again and the percentages you describe are true indeed.
However in S G 2 it would not connect at all even after a ROM change and an upgrade to 2.3.4
My second guess was the data connection. I have a data connection in my phone for 5 GB per moth.
When I disabled the data (holding the power button and selecting the appropriate option) the phone got connected immediatelly and after using it for over 1 hour with starting - stopping the car it would work perfectly with no drop connection at all!
I will observe it in the next few days and let you know how it goes.
p.s. My S G 1 worked with data connection enabled however it got all the disconnects you describe. I never tried to use it with data disabled. Not sure why data affects the btooth rsap like that. Which audio system od you have installed in your car (RNS or RCD? mine is RCD510)
OK after using S G 2 for several hours with data disabled on the phone everything works perfect and no disconnects occur whatsoever. Try disablining your mobile data mate and hopefully u will notice difference.
Dont know if it helps but I use SensatioN ROM by Crysis21 (fantastic ROM).
I have the SAME issue. I recently bought the i727R model (Samsung Galaxy S2 - LTE) and have the same problems with the phone keeping a connection to my '07 A4 RNS-e radio.
The disconnections are very random. Maybe 50% of the time the phone will reconnect...only to disconnect again. The rest of the time, the phone disconnects and will not reconnect until I power-cycle the phone.
I suspected it's a data problem right away - it seems to loose the connection when an incoming message or IM or app sends data on the network.
Unfortunately, because of this flaky connection, I've gone back to using my iPhone and given up on the SGS2-LTE. There's all sorts of issues posted on forums about the Bluetooth dropping, but ZERO solutions (or help from Samsung). I haven't tried turning the DATA connection off - and probably won't because I completely reset the phone and put it up for sale on Craigslist.
chrall said:
I have the SAME issue. I recently bought the i727R model (Samsung Galaxy S2 - LTE) and have the same problems with the phone keeping a connection to my '07 A4 RNS-e radio.
The disconnections are very random. Maybe 50% of the time the phone will reconnect...only to disconnect again. The rest of the time, the phone disconnects and will not reconnect until I power-cycle the phone.
I suspected it's a data problem right away - it seems to loose the connection when an incoming message or IM or app sends data on the network.
Unfortunately, because of this flaky connection, I've gone back to using my iPhone and given up on the SGS2-LTE. There's all sorts of issues posted on forums about the Bluetooth dropping, but ZERO solutions (or help from Samsung). I haven't tried turning the DATA connection off - and probably won't because I completely reset the phone and put it up for sale on Craigslist.
Click to expand...
Click to collapse
necrobump and a big +1 here for an Audi RS4 owner using Samsung S2 LTE on Rogers.
I started a thread here in case anyone has an updated solution
http://forum.xda-developers.com/showthread.php?t=1651867
FWIW, I use my SGS2 (GB 2.3.5, KI3 rom) with my A3's Bluetooth pretty frequently and have never had any problems. However, it's not MMI -- it uses HFP and rSAP.
Related
I've had two Galaxy S II phones now, and I've had the same problem with both devices. The phone's wifi is great -- when it works. Although I noticed that the death grip lowers the wifi signal bar, I can still browse the internet and download apps just fine.
The problem is that, at times, the phone will show wifi connectivity and yet, I can't browse the internet or access the App Store. I'll have to shut off the wifi multiple times and even this doesn't work 100% of the time. Shutting off the phone and turning it back on works 100% of the time.
Since this has happened to two phones, I'm beginning to question whether I have an issue with the wireless router because I have not come across this as a prevalent issue. At the same time, my laptop and a family member's iphone doesn't have the same issue.
Anyone else having this problem? Or have suggestion for fixing the problem?
Thanks
Here is me showing the problem on video:
My roommate and I both have the Galaxy SII and he constantly has problems connecting to our wifi. The only difference in our phones is his is rooted and mine is not. I plan on rooting my one of these days but would like to fix the other issues I am having first.
Mine isn't rooted, but it still has the connectivity problem.
EDIT:
I may have found the the solution. Probably unique to my situation, but what I did was disable WPS on my router. It's a medialink router and I thought I had disabled it (per instruction) but it was on. Perhaps that was the issue. So far, no problem.
EDIT:
Nope, the wifi has dropped again. By dropped, I don't mean it drops in the middle of browsing. It seems to drop after I've stopped using the phone for a while. I've already checked to see that the phone is to never turn off the wifi when the display is off/sleep.
Arghhh
same exact problem.
wifi on moto surfboard sbg6580
did the static ip fix continue to work?
Any phone is the same.
Sent from my SAMSUNG-SGH-I777 using xda premium
Don't have any issue with wi-fi , mine is rooted on stock rom
i have no issues with wifi on my sgs2, i have wifi on 24/7, and on wifi proabably 50% of the time. it connects and disconnects when supposed to, picks up on cell data and drops when its supposed to..
fwiw, my GF has an iphone 4, she had problems connecting to the HOME wifi, but no where else, i updated the firmware on the router, same problem, i swapped out the router for a spare a friend had, and setup a second access point on the same network, just called it the same SSID but put a "2" after it.
her connectivity problems went away, immediatly she noticed a difference and has never complained of a drop since...
try different encryption methods, if you're using wep, try wpa, try a few different things.
also try a firmware update, you might lose your settings during a firmware update, but there is usually a backup/restore option you can use. backup your settings before flash, then restore after. if you have access, for at least testing purposes, hook up another router and use it to connect to and see if the same problems persist.
No problems at all connecting to a WHR-G54S running Tomato.
The Moto Surfboards are known to be flaky.
I had the same problem. after getting another one I found out that if I didn't download so many apps at one time the problem mostly stopped and after running a couple weeks, I haven't had the problem with connection since. I'm not sure it will help, but I did a factory data reset and reinstalled the apps one our two at a time (it's frustrating, I know).
Sent from my SAMSUNG-SGH-I777 using XDA App
Update, I've had my phone replaced by Samsung tech in Plano TX, that doesn't help, but updating my router to the Apr 2012 eko dd-wrt did make some differences. Also the ota update from att has a new modem apk and that also chg'd the phone functionality. One thing that I have seen is that the phone reports the wifi network signal as being lower than before, and the output signal is slightly higher. I find that I have to occasionally turn the wifi on and off to reset it.
Short list of fixes and things to try:
1 update routers firmware
2 no dual encryption
3 some routers with 300 or greater Mbps settings need to be toned down to 150 or less
4 phone likes mixed protocol network over N only.
5 turn off phone power save
6 un check the carrier hot spot notify.
7 un check open wifi notify
8 pick a single band 2.4 or 5ghz. Note that updates with this can temporarily lock in to that frequency and not allow changes.
9. Dial *#0011# menu button, wifi and turn off the power save setting. This has to be done on every boot, and may cancel the display timeout.
10 On 5Ghz don't use DFS channels
Incorrect since people who have installed some roms and cm 10 are saying that they don't have any problems: I am almost certain now, that the wifi disconnect/connect issue is hardware incompatibility.
I have Linksys wrt-610 v2 -- which has problems
I have Netgear WHR3500L which has problems
I have Linksys wrt-54GL v1.1 which has NO problems (had to dig this out of storage)
If YOURS works or YOURS doesn't work pls visit this thread and post your info so we can find out what routers do and don't: http://forum.xda-developers.com/show....php?t=1752356
-------
I've posted this and then the mod's moved the thread http://forum.xda-developers.com/showthread.php?t=1722363&goto=newpost to the Sprint version of the forum.
Here's a recap since the guy has a sprint phone and won't recognize my issue there.
Here's the issue I've been having. I'm in a very active 2.4 wifi neighborhood. Even though I had the advanced wifi set to 'Always on' it kept disconnecting (and instantly reconnecting) to my network. The phone is scanning the neighborhood almost every 15 seconds. It's simply WPA-2 with just AES (and I'm not changing to TKIP)
This is a problem for me as I use "Unlock wtih WiFi" to keep from having to enter my PIN when I'm at work/home and "Home Sweet Home" which uploads any photos I have taken to my server when it detects the home wifi network (and deletes them from my phone after 3 months).
Anyway, I was just on the chat with Samsung and in the end we did this,
1. disable the ATT WIFI auto login function (seems there's something similar on the Sprint phones that's a issue).
2. soft reboot the phone (turn off, pull battery, count to 30, boot up)
However this suggested solution doesn't work.
The wifi isn't staying connected though the breaks are very very temporary, but long enough for those apps to kick in.
Update additional things tried:
3. Turned off WiFi power save in the *#0011# service menu
4. Turned off Open WiFi notifications, ATT Autologon.
5. Selected a single wifi band (5Ghz) where there is ONLY one network, mine
FWIW, I like that it connects to my 5Ghz wifi at 150 mbps, the speed is great.
6. I've disabled the Unlock with WiFi and it still occurred.
Here's a video of the issue showing the phone:
http://youtu.be/FBo3NFdcMhs
Here's a videoe of the issue showing the router: http://youtu.be/rRALDc8LZOk
and for those technically inclined here's a dump of the logs which clearly shows the drop and reconnect: https://dl.dropbox.com/u/38266113/SendLog.txt
FWIW. I just got off a 45 minute call with Samsung Help Support, went to level 3 support in Texas. This is newly documented, I've referenced this forum for additional reports of the dual encryption and the wifi connnect/reconnect issue I'm having. My ticket # 2113584507 (just for disconnect/reconnect) which you can mention at level 1 as having the same disconnect/connect issue. I specifically asked if I could post the ticket # so anyone could reference it at Level 1, but they will still take your own experience down.
Level 3 said they expect that they will be getting calls today since it's the first full day after the release. So if you want it fixed, CALL SAMSUNG, they're collecting bug reports.
I was having this same problem yesterday afternoon at work. Last night I set my radio to 5GHz only and today it hasn't happened once.
I am so glad I found this as it was driving me nuts on my new Sprint SIII. I think it's bouncing back and forth when both are available as at work, it stayed solid where we only have 2.4.
Thanks!!!!!!
I had that problem the entire time I had my Captivate. Very short disconnects. Only reason I knew was because of a task I was using in Tasker having problems, and I set a method to track connection.
I fixed the problem with setting a static IP address. I used WiFi Static.
I'm using it on the S3 just to be sure.
Had the same problem. However I set it to connect to 2.4ghz and it stopped doing that. If I put it on auto it will do it. If I leave at 5 it won't connect.
I do however think I might have a wifi dead spot. I notice if I hold it a certain way I lose a signal or two on wifi. Or the speed of wifi decreases. Anyone else having the same issue? It might just be me
sent from my GALAXY SIII
I've experienced the same wifi drop issues so glad it is being investigated. Thanks to OP for diligence in tracking this down!
ewingr said:
I had that problem the entire time I had my Captivate. Very short disconnects. Only reason I knew was because of a task I was using in Tasker having problems, and I set a method to track connection.
I fixed the problem with setting a static IP address. I used WiFi Static.
I'm using it on the S3 just to be sure.
Click to expand...
Click to collapse
Have any of you tried this ^ ? Mine is set up like that, and no issues at all. I did have those issues on my Captivate until I did above.
I'm having a rash of the issue tonight--dropping wifi and now says unable to connect due to poor reception (I'm sitting beside my router)...
Liferules said:
I've experienced the same wifi drop issues so glad it is being investigated. Thanks to OP for diligence in tracking this down!
Click to expand...
Click to collapse
although I've gone to level 3, I need you and everyone else experiencing this to report it so that its corrected. Granted they are certainly going to visit the wifi code for the dual encryption issue and stability with Auto frequency, but fixing this could be done at the same time.
FWIW, since I have two routers and 3 networks, one of them is simply a pure G up to 54mbps default firmware setup (since it's the FCC's) and connecting to that greatly reduces but not entirely eliminates the problem (even in the same room). It's much worse on my "N" only networks. And I have tried static IP that also doesn't fix the problem. This is some sort of software issue in the renegotiable speed setting or timing settings or power savings. Off course it certainly could be some badly (or purposely) behaved app software too.
stan.s said:
... And I have tried static IP that also doesn't fix the problem...
Click to expand...
Click to collapse
Interesting. Given that I don't seem to be having any issues, it seems it is not a problem for everyone.
Had the same problem. Net gear router wrnd3400. Wifi kept dropping so then I connected to Verizon router and no problems. Seems to be a problem with some after market routers.
Sent from my SAMSUNG-SGH-I747 using xda premium
topgun303 said:
Had the same problem. Net gear router wrnd3400. Wifi kept dropping so then I connected to Verizon router and no problems. Seems to be a problem with some after market routers.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
More likely to be a timing issue or protocol issues as the phone scans and tests various networks on different bands and protocols. Many people have n routers that do mixed networks, b, g and n, and they just may not know what they are doing all the time as the phone renegotiates with the router. I have a wrt 610v2 doing only n on 2.4/5ghz and on the the Netgear N300 it drops less doing 2.4 g and at my friends who have a wrt54g and it dropped even less often. The app that I use to enable my lock screen pin makes this more noticeable.
Sent from my SAMSUNG-SGH-I747
FWIW, I decided to followup on the ticket. Samsung level 1 (not that it matters) says they have never heard of this problem. Level 2 was better, and we in essence setup a new ticket with the videos already linked to it. I offered a sendlog, I offered to install a test app if they have one. I already beta test for a number of app developers as well as some major hardware OEMs.
PLEASE, everyone, call samsung support directly and register a ticket that this is a problem so that they have the information first hand and not via ATT or Sprint, etc which they might ignore.
stan.s said:
FWIW, I decided to followup on the ticket. Samsung level 1 (not that it matters) says they have never heard of this problem. Level 2 was better, and we in essence setup a new ticket with the videos already linked to it. I offered a sendlog, I offered to install a test app if they have one. I already beta test for a number of app developers as well as some major hardware OEMs.
PLEASE, everyone, call samsung support directly and register a ticket that this is a problem so that they have the information first hand and not via ATT or Sprint, etc which they might ignore.
Click to expand...
Click to collapse
I just called. They said they would note it 'on my account'. They indicated it would be a Google issue, not Samsung. They only do the hardware (and of course, it can't be a hardware issue, can it? )
I was thumbing through the phone logs from a boot to connection and reconnect. I have to say Chrome has a lot of errors thrown particularly in the bookmark sync. Also it appears that every time the wifi is initially started it checks for authentication for tethering on both the wifi and BT. It almost looks like the phone thinks that the wifi ap is off and restarts wifi scanning.
Sent from my SAMSUNG-SGH-I747 using xda premium
Which phone number did you call for Samsung support, please?
I have experienced the slow network and disconnect/reconnect issue on this phone since it arrived, but all is normal on our 5 or so other mobile devices with this Netgear WNDR3700 router on the 2.4GHz and 5GHz bands.
Oh, and there's this.
- ooofest
Hi all,
I'm having a data connectivity issue on my phone when moving from 2G to 3G. If I'm connected to 2G, then move into an area of 3G coverage the phone will successfully migrate to the 3G network, however the data connection will often not start up for between 30 minutes and severanl hours. Flipping airplane mode will *sometimes* fix it, but more frequently, even rebooting the phone won't work. However, if I lock the phone to 3G from the settings, I do not encounter this issue at all. It only happens on my home provider (Jersey Telecom - they're small). In the UK, on Three, it didn't happen.
So, given that the problem can persist over reboots, and doesn't happen in the UK, it makes me think it's more likely a network issue, so I called them up. The network engineer managed to reproduce the issue on his colleagues Samsung Galaxy Note, but they are adamant that it's a phone issue and not a network issue, and is a matter of Samsung not sticking to the specs. The phone isn't currently rooted, but I can root it if it will help me debug the problem. From the sounds of it, it may be problem consistent to all Samsung radio phones on our network.. and I really don't want to switch to another phone.
They say that from their logs, the phone is not always trying to create (or presumably, migrate?) a PDP when moving to a 3G network. It's hard to say whether it's a problem with the phone or their logs.. has anyone else experienced a similar issue? Does anyone know how to access logs about the phone trying to create a PDP etc. so that I have something to compare with theirs?
Thanks
check out the modems thread and try a better modem
Sent from my checkrom jellybean powered sgs 3
I have searched all over and I don't find an answer, if I'm missing a thread please just point me in the right direction.
My home wifi has been working with my Note just fine since I got the phone (cue ominous music) up until yesterday. Last night, it started asking me for a password (which was weird, because it hadn't since I first got the phone and set the connection up), and I put the password in, but it kept saying "authorization error." I am really frustrated, I rebooted the phone, the router, removed the home wifi connection (the "forget" button) and reinput it -- I even booted into "safe" mode to make sure it wasn't some app -- no joy. It's a very simple linksys router, WPA/WPA2 security, all the other tablets/computers/phones in the house work just fine (tablets/other phone Android, laptops Windows.) And my Note was working just fine until last night -- no recent software install or update, it was seemingly just random. It's a stock Verizon Note, I haven't even bothered to root since it does everything I want.
Here's the kicker: I connect to OTHER public networks just fine. I connected to my work and McDonald's wifi this morning, no problems.
What could be wrong? I really need to be able to use my wifi at home, I don't see anything in Google or on the boards about this. I am hoping my search-fu is weak and someone knows what is up with this.
restore defaults on your router, then setup a new password.
Hope this Helps....
MaureenMun said:
I have searched all over and I don't find an answer, if I'm missing a thread please just point me in the right direction.
My home wifi has been working with my Note just fine since I got the phone (cue ominous music) up until yesterday. Last night, it started asking me for a password (which was weird, because it hadn't since I first got the phone and set the connection up), and I put the password in, but it kept saying "authorization error." I am really frustrated, I rebooted the phone, the router, removed the home wifi connection (the "forget" button) and reinput it -- I even booted into "safe" mode to make sure it wasn't some app -- no joy. It's a very simple linksys router, WPA/WPA2 security, all the other tablets/computers/phones in the house work just fine (tablets/other phone Android, laptops Windows.) And my Note was working just fine until last night -- no recent software install or update, it was seemingly just random. It's a stock Verizon Note, I haven't even bothered to root since it does everything I want.
Here's the kicker: I connect to OTHER public networks just fine. I connected to my work and McDonald's wifi this morning, no problems.
What could be wrong? I really need to be able to use my wifi at home, I don't see anything in Google or on the boards about this. I am hoping my search-fu is weak and someone knows what is up with this.
Click to expand...
Click to collapse
I have been experiencing this problem for the past 4 days. I have owned my Note II since December 25, 2012 and it has been working on any WIFI AP ive tried. 4 days ago in the middle of the day, my phone started giving out "authorization error" and would not let me log in to my home WIFI. I have 4 computers, 3 smartphones and other devices all working perfectly in my home WIFI. My problem even occurred when connecting to open, unsecured WIFI AP also. Nothing seemed to work. I called Verizon and did all the steps leading up to factory reset. With no luck on any tricks or tips from them I called Samsung. They walked me through the same processes and everything, so I decided to do a factory reset. This did not fix anything. I still get "authorization error" and "wrong password" on any WIFI i try to connect to.
I found out yesterday if I stand within 5 feet of my WIFI router I can connect and browse the internet for a few minutes until it kicks me off and does the same old "authorization error". If I sign in to my WIFI within the 5 feet and walk away, it disconnects and again, gives me the error messages.
I called Verizon back and they are sending me a replacement phone.
TL;DR:
Try accessing your WIFI when you are right next to it.
If problems still persist, call your carrier.
I hope your phone isnt as busted as mine.
Argh, that's bad. At least my phone connected to open networks so I knew the hardware was ok -- I wiped the router and set it up again (per the suggestion in this thread) and I'm good for now. (Embarrassed I didn't think of that myself) Hope you have better luck with your replacement phone!
soaptylerdurden said:
I have been experiencing this problem for the past 4 days. I have owned my Note II since December 25, 2012 and it has been working on any WIFI AP ive tried. 4 days ago in the middle of the day, my phone started giving out "authorization error" and would not let me log in to my home WIFI. I have 4 computers, 3 smartphones and other devices all working perfectly in my home WIFI. My problem even occurred when connecting to open, unsecured WIFI AP also. Nothing seemed to work. I called Verizon and did all the steps leading up to factory reset. With no luck on any tricks or tips from them I called Samsung. They walked me through the same processes and everything, so I decided to do a factory reset. This did not fix anything. I still get "authorization error" and "wrong password" on any WIFI i try to connect to.
I found out yesterday if I stand within 5 feet of my WIFI router I can connect and browse the internet for a few minutes until it kicks me off and does the same old "authorization error". If I sign in to my WIFI within the 5 feet and walk away, it disconnects and again, gives me the error messages.
I called Verizon back and they are sending me a replacement phone.
TL;DR:
Try accessing your WIFI when you are right next to it.
If problems still persist, call your carrier.
I hope your phone isnt as busted as mine.
Click to expand...
Click to collapse
Ok............ wow you have me 100% nervous now. I've been experiencing this issue ever since I unlocked, rooted and ROM'd my Note 2 back in the middle of December, and I experience the problem with only my Wireless-N SSID on my router. I can connect to the Wireless-G band just fine but the N one gives me this error no matter whether it's open or not. I seriously hope this isn't an issue of broken hardware..............
I figured this was worth mentioning. I have 3 Note 2's in my household, 2 of them are running Beans Build 5 and Perseus kernel overclocked and the other phone is totally stock.
All 3 phones have the exact same issue of connecting to the 802.11 N band on my router. They connect to the G band just fine. I think this rules out any worries about it being a lemon issue. Most definitely is a Samsung software issue that's been happening to multiple models going back a few years. Here's a google search of this issue using non-phone specific parameters. Notice how ALL phone specific forums point to a Samsung device.
I have a bad feeling that this is not something that will be getting resolved any time soon.
Edit:
The plot thickens. I have performed some tests on my router to see if I could get my phone to connect. Well here's my results:
5Ghz band = Wireless-N Only = Authentication error occurred
5Ghz band = Wireless-A/N Mixed = Connects instantly
2.4Ghz band = Wireless-N Only = Authentication error occurred
2.4Ghz band = Wireless-G Only = Connects instantly
The problem is clear. It's Wireless-N. I can connect just fine at Wireless-A speeds (54mbps max signal) and everything up to Wireless-G, independent of frequency, but as soon as I try to force Wireless-N onto my phone, it craps out and fails to authenticate. This happens regardless of whether I have the network encrypted or not.
And based upon my google search I have linked to in this post, I doubt this is something we can expect to be fixed anytime soon. Oh yeah and for the record, when I have my router set to Wireless-N only mode, I was able to connect instantly without error on my crappy old HTC Thunderbolt running a hacked together AOSP 4.0.3 ROM.
Yep............... GG Samsung
wireless n has been a unreliable joke since it was released...my favorite routers are the linksys wrt-54gl running linux dd-wrt firmware. one of the most affordable rock solid routers built. its only g band but most people do not need anything faster for home use. heck most of us cant afford the t1 type connection speed to utilize n band anyway.
Exact same problem as well...I'll have to try the Wireless N-only vs. Auto to see if that fixes it...
EDIT: Both wireless mode settings of 'N-only' and 'Auto' caused the problem. I had to set it to 'Legacy' in order to get the connection to stick without authentification errors. Have an ASUS RT-N66U router...
EDIT 2: Did the same thing on my Cisco E3000 and it worked as well.
Really looks like a Sansung wifi bug on the Note 2....
vortmax said:
Really looks like a Sansung wifi bug on the Note 2....
Click to expand...
Click to collapse
It's not Samsung. There have been issues with myriad devices and wireless N pretty much the whole time it's been around. Android OS or the the N standard-- I personally know people with other manufacturers hardware and the exact same issues. If it's an OS problem, you would think it would be fixed by now, but who knows, like was mentioned above, very few people need the bandwidth that wireless n can theoreticly provide.
Good Luck,
Jason
jacampb2 said:
It's not Samsung. There have been issues with myriad devices and wireless N pretty much the whole time it's been around. Android OS or the the N standard-- I personally know people with other manufacturers hardware and the exact same issues. If it's an OS problem, you would think it would be fixed by now, but who knows, like was mentioned above, very few people need the bandwidth that wireless n can theoreticly provide.
Good Luck,
Jason
Click to expand...
Click to collapse
It's definitely something specific with Samsung and the N2 since my cousin's G3 connects to the same router on 5GHz WirelessN/Auto with no issues at all. I think they have a bug to fix...
Can someone else perform a check with their Note 2 on a Wireless N only setting? It seems this is a bug that really need to be fixed.
vortmax said:
Can someone else perform a check with their Note 2 on a Wireless N only setting? It seems this is a bug that really need to be fixed.
Click to expand...
Click to collapse
Mines been working on N only since I got it. Rooted and running about 6 different ROMs.
Sent from my SCH-I605 using xda premium
I just had this issue come up when moving to an AOSP ROM this morning. I even nandroided to a previous ROM that had working WiFi and still not working. I restore defaults on my router and reset all my security settings. Still getting the same authentication error.
Sent from my SCH-I605 using xda app-developers app
For the people experiencing this issue, are you on 4.1.1 or 4.1.2?
vortmax said:
For the people experiencing this issue, are you on 4.1.1 or 4.1.2?
Click to expand...
Click to collapse
I have tried roms that were 4.1.1 and 4.1.2 with no luck.
Sent from my SCH-I605 using xda app-developers app
I am pretty much to the point of using Odin to go back to stock and see if that fixes it. I went back to stock rooted rom that was my first backup and the problem still carries over.
Sent from my SCH-I605 using xda app-developers app
So I am quite sure that I've got a weird issue with my Redmi Note 2. To make it fast I will just list the issues.
Phone logs out of all networks (Wifi and mobile data at least every five minutes).
Sometimes it just 'decides' not to receive or send data, wheter it is connected to the internet or not.
Mobile data is never faster than E, even within my monthly data limit and in areas with high speed mobile data.
Is very slow at times (and crashes approx. once a day).
Does not react for some few seconds every now and then (makes typing impossible/remixes music...)
The main issue is the connection problem. My provider combines two mobile data networks, so that the phone thinks it is in roaming sometimes. Yet all of this was not a problem at the beginning. The connection issue just suddenly appeared (after I was on vacation and used roaming). Not sure, if there is a connection to that, though. I already asked a more tech savvy friend of mine, but got no solution out of that. So far I have tried:
Installing a new operating system (nothing changed eventhough that exact OS worked perfectly on the same phone my buddy had).
Googling the issue and try to play with the settings to get it working properly again (again nothing changed).
What I don't get is why such an issue would suddenly just arrive and that apparently nobody else had that same issue. I would be more than happy about any help I can get. Besides the issues I like the phone (and don't want to have to buy a new one).
http://en.miui.com/thread-508431-1-1.html..flash baseband.maybe can help for poor signal
Hi,
The same problem is on my phone. Due to this problem, I couldn't use the phone at all, I bought another phone. Now my device is in the drawer, no different from zero. I have tried various roms, including lineage, I changed wifi antenna as hardware. The problem continues. Is there a solution to the problem.