Hello! I've got the N7105 and I am a fanatic VOIP user I'd say. Unfortunately, i've discovered a strange bug, on Wifi every 10-15 seconds, the ping value gets raised from avg. 10 ms to 80-90, 140-150 for 2-3 seconds and then it returns to normal. This does not happen on CM custom roms. Unfortunately, I have to use stock roms because CM has it's known bluetooth bugs, bluetooth does not work with VOIP apps.
The issue affects both 4.1.1 and 4.1.2 firmwares.
This affects call quality. I don't know why noone discovered this issue.
Related
Hi, I was wondering if anybody has come up with a fix for AOSP roms for Bluetooth yet. Sense roms connect to my bluetooth stereo perfectly, but none of the AOSP roms (Cyanogen, ect.) can connect consistently.
The very odd issue is that yesterday I thought I came up with a solution, so I flashed CM7 on and tested. It worked. However I couldn't connect to the market because I forgot to install the gapps addon, so I did, and didn't think twice until last night when going to work, and bluetooth wouldn't work again. It seemed like the gapps addon broke bluetooth, but it could have been some unknown external factor. I can test this later today to see if the gapps addon does in fact kill it somehow.
Can anybody shine light on the bluetooth issues and maybe enlighten me as to a fix if there is one?
Not one response? That's disappointing. I was doing some testing with CM7 today and I could not reproduce the bluetooth breakage that I have experienced every other time. I was trying to isolate what was causing the issue by lashing the rom, then booting, testing, then flashing the RIL, booting, testing, then flashing the gapps package, booting, testing, then re-installing all apps one at a time from titanium backup (the same as I did before) and nothing broke it. Over a full day now and bluetooth is rock solid.
This poses a problem because I don't know WHY it is working. The only variable I actually changed is booting after each thing I flashed. This still will not change issues with any other AOSP roms even if the solution is to flash each separately, because the rest come with gapps installed, and they are broken both before and after a RIL flash.
Also to further convolute things, I started the day testing LeeDroid. Bluetooth would not connect. This is a rom that should have connected just fine.
Hi mrcandyman,
I too have noticed that a lot of AOSP roms have (imho) severe BT problems, mainly with connection to earpieces in my case (voice dialling). I have tried AOSP roms on both my desire and sgs2 and had the same problems on both. Flashing back to rooted stock roms has always cured my problems with BT. I am not a dev or programmer so have no idea what or where the problem lies only that stock roms I've tried don't have BT problems and AOSP do.
feeling your pain,
Night....
Has anyone figured out the issues with bluetooth on MIUI for E4GT?
In Summary:
Loss of established connection
Can't pair devices
Drops and reconnects
I see the issues spread all over the dev thread, but there is no apparent resolution. It seems that the issue is intermittent (some people experience it, some do not). Some experience certain symptoms and others are experiencing multiple symptoms. I flashed back to Calkulin's ROM after using MIUI for a couple of days because having no bluetooth is a show stopper for me. Otherwise the ROM is fantastic. Calkulin's is always my default. Smooth, stable, and fast.
Of course, all this might be moot for me once ICS comes out.
Odd occurence. Whichever ROM I use on my t800 bar stock alterations like ironman, I end up with terrible Bluetooth audio dropping up to a dozen times song making it unusable. Sadly I hate Samsung's stock ROM which even cleaned up is still painful to use. Any ideas how I can resolve this or is this a cyanogen related issue that will affect all cm based ROMs?
Any way I can debug it?
Thanks
Hi all,
I was wondering if anyone else was experiencing this, and/or had any solutions - as it's slowly driving me mad.
I do love my M8, but it's getting old and slow running Sense 6/7, and I much prefer the 'pureness' of GPe/CM12.
My phone is SuperCID'd and fully unlocked, and currently flashed the latest RUU for GPe (full firmware) then Candy5 ROM v2.5.5 flashed (based on CM12).
I've tried various Sense firmwares, and other hacked/full GPe firmwares... Bluetooth seems the same on all - works fine on Sense, but not as reliable on non-Sense.
The biggest issue I have is that I have a LG G Watch R and it will disconnect after a few hours, sometimes days, and won't reconnect unless I turn off and on Bluetooth on the phone. Even then it's temporary - I find Wiping Data on com.share.bluetooth makes it stable again for a few more hours/days.
And no, it's not the watch, as if I'm in the car at the same time - that will disconnect and not reconnect either. It's definitely the phone...
Now I generally keep Bluetooth and WiFi on at all times. I only use WiFi at home.
I have noticed it seems to become unreliable if WiFi is on, but hasn't been connected to anything for a while. It's almost like it's "scanning" buffer is full and it's affecting both WiFi and BT (as it's the same chip).
If I keep WiFi off, and only on at Home where it stays connected - my Bluetooth seems really reliable and I don't have an issue.
This isn't a fix, though. As I don't want to have to rely on Llama to switch my WiFi on and off based on my location. Surely a potential battery drain versus just keeping it on at all times.
I've tried a Tasker task to wipe com.share.bluetooth every couple of hours, but it didn't fix it. Would still die beforehand.
I've tried various GPe ROMs, and CM12 ROMs - all as Clean Flashes and not restoring Bluetooth data in Titanium Backup (I only restore user aps + data).
Just wondered if anyone had any ideas!!
Thanks for reading.
I'm having the exact same issue.
Gpe and sense work fine, but cm12,1 just won't stay connected to my car or watch. Very frustrating.
I really want to run cm as my daily driver, but it's totally incapable of keeping Bluetooth up.
Is anyone running cm 12.1 and has working Bluetooth? If so, can you let us know which radio firmware you're using?
I took a stab in the dark and applied firmware 4.16.401.10. So far my watch's connection has been solid. Still haven't tested the car, but will test today. Hopefully it'll be stable - if it is then I'll finally be able to use CM as my daily driver!
Full commute without Bluetooth disconnecting from my car, and I've had a solid connection to my watch for over 24 hrs! WOOOOOOOT!!!!
4.16.401.10 is the trick. Anyone having Bluetooth issues on CM12.1 should go download and apply the firmware. (must be s-off, obvs.)
Firmware is here (courtesy of Mike1986 of ARHD fame)
Ah great news - thanks.
I'll give it a go later!
Should know within 15 mins after if the bug is fixed!
Thanks again.
Update - looks like that's the fix!
Strange it doesn't seem to be mentioned anywhere else but at least it's now here for anyone else.
Thanks for the tip!
I recently purchased this device. And Wifi has been, not just abysmal but downright non existent. It was okay in 6.0 but when i upgraded it became worse now with 7.1 Beta it is unusable. I don't even care about having 7.1 Beta or Wifi speed anymore, what version or ROM will give me workable wifi that stays on?
Try dirty unicorns
I've never had an issue with WiFi... is it possible that it is hardware related? The only significant issue I've had is that the sound will turn off after the tablet is on for a long time and the only thing that fixes it is a reboot.
tkoreaper said:
I've never had an issue with WiFi... is it possible that it is hardware related? The only significant issue I've had is that the sound will turn off after the tablet is on for a long time and the only thing that fixes it is a reboot.
Click to expand...
Click to collapse
Hmm, it may be. I've heard of a few people RMAing their device for this, but it was okay with 6.0 (it came with 6.0), i think; So i'm holding up hope.
Try turning off location scanning for WiFi and Bluetooth in Settings under Location, then Scanning. I did that when I first got mine in March and never have had an issue with WiFi. Plus it saves battery as well. Other have mentioned no issues after doing this as well in another thread (http://forum.xda-developers.com/pixel-c/general/anandtech-depth-wifi-testing-t3345129/post69316108).
I have WiFi issues too.
Ver 6 was fine but current version you get full bars all is well.
Several hours later no bars, message attempting to validate.
Solution restart the device.
I complained on Google Boards.