yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] BarryH_GEG:
I don't think this has been asked. Has anyone that's having issues rooted, frozen or removed apps, or disabled apps and services for some of the preloaded apps (the latter even if they haven't rooted)? The opposite of that question is does the issue occur completely stock with just standard issue Play Store apps installed? Also, are magnetic cases being used? Either Samsung's or third party's?
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] GeorgeP:
I'm not rooted. I only have on app disabled: S Voice. I'll try turning it back on for a day or two to see if it makes a difference. Probably a long shot, but My Magazine is required for exchange mail, so who knows?
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] anthropoidape:
Mine was not rooted, and I ran it in an absolutely stock state (as well as with some apps shut down). In either case I had the problem. That was the point where, based also on reading in this forum, I concluded it had to be hardware.

I should say though that "stock" down here is full of bloatware. I also ran Samsung's ML1 firmware and had the bt issue.

No case at all, magnetic or otherwise.

I did read that some people had success with cleanrom 1.1 after rooting. Well, that may be but it is not really satisfactory imho. I would like to run cleanrom of my own free will, not because it happens to patch over a hardware fault!

I wish I'd had a chance to try squeezing the tablet as you suggest though.

Like you, I suspect a build quality problem as opposed to a component failure. We'll probably never know for sure I guess. I just hope I get my replacement soon, and that when I do it's a good 'un.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] Solyomszem:
Hi, I was the one reporting CleanROM 1.1 having this issue fixed. And also have posted that after one day, everything was back to it's original faulty state. So no fix with CleanROM.

Tapatalk-kal küldve az én GT-N7105-el
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] ziggysmalls:
I ended up returning mine. But as I was waiting for 3 hours to do so because of an issue of how I purchased it, I was playing around with my old one. I found that for me, doing a factory reset helps a lot. I did a factory reset and it was working fine while I was at the store, but I went through with the return anyway. The new one worked at the store, but since I did not set it up through wifi in order to be tested, I reset it and did it at home. I encountered problems again, then I reset it a third time and things were fine. Still a mystery.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] anthropoidape:
FWIW factory resets did nothing for my case.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] pcbtmr:
Streaming Audio!

Can't remember who suggested this but to keep the BT radio "alive" stream audio to a BT earpiece/speakers... My K810 now only disconnects when the music stops. To be sure, it eats the earpiece battery but for 7 hrs, the keyboard works excellent with this tablet.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] pozer69:
I gave up on this, however what I have been doing is using a logitech unifying adapter connected to an otg cable with mouse and keyboard. I still think it is unacceptable that this is an issue.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] BarryH_GEG:
I admire the ingenuity and patience that's being applied. But tolerating an issue like this is fine if we were talking about a $99 Coby tablet. We're not, we're talking about a $500+ newly launched Samsung flagship. I don't know what the percentage split is between tablets that are fine vs. screwed up but the fact that there are examples that work perfectly without gymnastics means exchanges or repairs under warranty are in order.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] anthropoidape:
Got my replacement today.

The bluetooth appears rock solid (relatively limited testing, but enough to know it's better than before) with exactly the same keyboard and mouse.

Phew.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] GeorgeP:
That is encouraging. I just picked up replacement number 2 today. So far,so good.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] BarryH_GEG:
George, this is your third device, right? The second worked fine but stopped working later. How much later? Hopefully this is/was an assembly issue that affected early units and that later builds won't be affected.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] GeorgeP:
Yes, this is my third device. The second one stopped working after about a week. I can tell this new one is a later build than the other two were. The other two came with the initial firmware and took a few updates right after I started it. This one came with MK1 out of the box. So I'm hopeful that this one is good.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] anthropoidape:
Interesting point. My replacement is MJ6 which is the newest local firmware. My dodgy one came with (from memory) MJ2. Definitely pre-MJ6 anyway.

This one still seems good. I am pretty keen to root it but I will wait until I am really sure there are no hardware issues. In the meantime the Taiwanese ML1 will do me I guess!

I really love this thing with a working kb and mouse.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] Kspiteri:
so far so good

In light of my previous futile attempts at working around the solution (bluetooth keepalive app etc.) I decided to get a replacement tablet from the online company i bought the tablet from. Took around a month with return shipping processing and actual shipping of a new tablet but I received it last Thursday and have been working with the same bluetooth keyboard I had before with absolutely no problem at all.

The issue must definitely be correlated to Samsung quality control and its an outright shame with the galaxy 10.1 2014 being such a high end tablet, but then again samsung just released a 12.2" version this month I believe which goes to show you how worried they are about this issue...

To all those with a tablet still in time to get a replacement, my advice is to do so and keep bugging customer care until you get a functional tablet.

Its what you paid for after all!!

PS. Also still having issues with my sandisk 64GB micro SD blocking up on me but this is likely a card issue and should be addressed in a different thread.

Cheers for all the help guys
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] BarryH_GEG:
Early builds of any device tend to help identify production issues. Early N10.1-14's have suffered from loose/crooked speaker grills, S Pens that fall out of their silo, some pretty nasty screen bleed, and this BT issue. The issue seems to present itself when low powered peripherals like keyboards and mice are connected. Who knows what percentage of people use BT keyboards and mice with their tablets so this could be a huge undetected issue affecting lots of people or a small issue in the single digit percentages. There haven't been new reports so hopefully its been corrected in assembly/production.

Try formatting the card first in another Samsung device or even your N10.1-14 if you formatted it on a PC. That's helped people in the past.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] FSkyman:
BT works when rooted

Hi Folks

I got also some Card and BT issues - the SD Card is a original Samsung 64 GB one.

The Tab surface and some Apps only working some kind of sticky and random unwanted reboots.

The I installed HAL 9000 and TWRP RECOVERY - which sets the Knox Counter to 01.

But now no problems anymore this reply is typed on my Wifes I - MAC BT Keyboard.

The Tab runs now like I was expecting it.

My conclusion is forget about the Knox 01 security thing if you want a very reliable and fast working Tab.

I hope that helped.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] QuantumPSI:
So I'm using the logitech K810 keyboard with my tablet and I have the connection issue as well. It's not nearly as bad as others and is manageable. I've noticed that about 90% of the time when the keyboard reconnects, it's immediately after I press 'shift+i' followed by a space. It doesn't always happen, but when it does, that's typically the last inputs.

I don't know if this information helps at all but I figured I'd at least post. I wonder if I'm inadvertently activating a shortcut of some kind... something to think about.

Edit: Actually, I just confirmed this. If I hold down "shift" and press spacebar, the keyboard will reconnect!!! Every single time! How strange... I wonder why.

Edit: So it's not actually reconnecting... it's trying to switch the language. I just installed Japanese and now "shift+space bar" switches the languages. Wish there was a way to alter this command. Definitely would prefer something more "complex" that can't be easily triggered. With that said, looks like I don't have any keyboard issues that people were saying, so my apologies, just wanted to share my experience.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] dpersuhn:
So, here's an interesting observation for folks that have had BT keyboard issues. I picked up a note pro 12.2 and the keyboards I was having issues with seem to all work fine with it. Not sure if KK is the remedy or what, but if the hardware/chipsets are exactly the same, an upgrade to the 10.1 2014 edition could put us all in a much happier place on this issue.

For reference, I replaced my first 10.1 2014 with a later build and still had issues with several keyboards before settling on the MS wedge, which works OK. The tablet seems to put the connection with it to sleep at times and it can take a moment after the first key press to wake up. The 12.2 exhibits no such issues.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] GeorgeP:
I don't think KK is the remedy. I think the problem was a hardware issue with the earlier builds. I replaced my first and second N10.1 2014 because they both had the problem with bluetooth keyboard connections. The third one has not had a single disconnect in nearly a month of usage on the same keyboard (Logitech K810).
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] dpersuhn:
I guess an update will be the final straw for me. I'm a bit skeptical hardware is the issue on this one with the wedge working well and others failing horribly. If a KK update doesn't fix it, I guess I'll be up for yet another replacement.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] Peter Unger:
OK, an update from my side - debugging etc. was not successful. Samsung told me to wait for the 4.4.x update end of this month or in the beginning of March.

If the error exists, they want to have my tab to install a special debugging firmware.

So let´s see...

Cheers

---------- Post added at 02:57 PM ---------- Previous post was at 02:49 PM ----------

Same here - two early ones do not work, a later one (but with a little bit more display bleeding) works flawless.

I do not give up and exchange them because the tabs with the BT issue have no other issues ;)
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] dpersuhn:
So, I tried a little experiment. I picked up another new 10.1 2014 edition to try. Same results as the last one. I then took my keyboard into best buy to the samsung kiosk. Tab pro 10.1 works great, note pro 12.2 works great. 10.1 2014 edition, garbage with both keyboards. I didn't try the tab 3, but should have just for grins. It's the same result with two separate keyboards. I asked the samsung rep (if you can really call those guys samsung reps) what my options are. His only response was to hope that Samsung would release an update that would correct it. While I agree that there was an apparent hardware issue early on, I think the BT stack is still garbage in the latest 4.3 release.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] BclingergFJ:
It is. I am having lock up issues with mine. Never the 2012.

Via my Note 3
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] BarryH_GEG:
The fact that the N10.1-14's you tried are having problems with multiple peripherals means it's the N10.1-14(s) you tried. The fact that people who were having problems replaced their N10.14's (sometimes twice) kind of proves it isn't s/w. The formerly problematic peripherals work fine running the same ROM, configuration, apps, and settings they were using when the problems occurred. I'm a heavy productivity user and can use a BT keyboard and mouse for hours at a time and have never had an issue.

Pure guess on my part, but I thinks it's an antenna issue. If you look back a couple of pages you can see how the antenna's run and the actual antenna is on the back of the device while the BT radio is on the front. They are connected with pogo pins which have historically been problematic for wireless signals on the Asus TF201 and HTC One X. BT and 2.4GHz Wi-Fi share the same spectrum and the BT signal is much weaker and more susceptible to interference. So if the antenna's reception is less than perfect the Wi-Fi signal could/would over power the BT signal. BT HID devices are typically used in close proximity to the devices they are connected to and tend to have weaker (cheaper) radios and antennas because of it and therefore output a weaker signal. The fact that some folks have reported their HID issues go away when streaming music sort of confirms that its not just a simple BT stack or s/w issue and that it's somehow signal related; the connection between the HID device and the N10.1-14 isn't being kept alive.

If you're buying and exchanging your device from the same store they could all be from the same production run which, if it's an assembly issue, would explain why they may all behave the same. Did you have to apply an update to the devices you've gone through? The reason I ask is that the report of BT issues seems to have slowed considerably. One or more people who've gotten newer units (latest ROM already installed) haven't reported any BT problems.

Anyway, the fact that some N10.1-14's work flawlessly while others don't means it's not s/w.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] dpersuhn:
The one I tested had MK1 on it right out of the box. This would make 4 tablets, all behaving the same way, purchased from 3 separate stores in 2 states (FL and PA).

---------- Post added at 04:16 PM ---------- Previous post was at 04:07 PM ----------

I'll reiterate from a previous post that the MS wedge works reasonably well with this tablet, as does a Logitech ultra slim mouse. I'll also reiterate that I agree there was likely a hardware issue with some of the early production units. Where I disagree is the notion that just because an apparent hardware issue was found on some units that software issues can't also be present at this point.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] BarryH_GEG:
Not all BT devices work with all devices - it's just the nature of BT. The Logitech K810 is working flawlessly for some people; when it didn't with N10.1-14's they had to exchange.

Here's mine connecting my mouse and keyboard from a cold start. I've had a Wi-Fi G-Tab 10.1, 3G G-Tab 10.1, 3G N10.1-12, and the N10.1-14's BT is the best of the four. Either I'm lucky or you're not.

[YOUTUBE]4F4N9ZLiGxU[/YOUTUBE]

That could also point to an antenna/interference issue which is being overcome by certain peripherals that output stronger signals. A single peripheral, the Logitech K810, working on some N10.1-14's and not others sort of discounts the s/w theory. Especially when the very same and singular K810 was borked on one N10.1-14 and not another. And some of the folks with issues tried their K810's on virgin N10.1-14's as they came out of the box and/or after a hard reset.

The danger of hanging on to the s/w theory is that people have a limited return window. If it's purely h/w and they wait a month for an update and it doesn't do anything to help they're kind of screwed. Or at a minimum inconvenienced having to send their device to Samsung for repair.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] GeorgeP:
It seems you are spending a lot of time on this. If it is for intellectual curiosity, then fine. But if you just want working bluetooth, I'd suggest you exchange it (although I recognize that is a time-consuming PITA) or use one of the work arounds. I think your analysis proceeds from some false premises, like one I quoted.

To the contrary, it is very likely that "three separate tablets from three separate stores in two states, purchased several weeks apart would all have the EXACT same hardware defect" as they were likely produced with the same manufacturing process, in the same facility, and used parts from the same suppliers.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] BarryH_GEG:
For reference, [MENTION=615393]GeorgeP[/MENTION] is one of those that had to go through three N10.1-14's to get one that was 100%. The first was borked out of the box and the second started out fine and became borked. The third seems fine so far, right George?

Your incredibly well written dissertation still doesn't explain how the same singular Logitech K810 can work fine on one N10.1-14 and not on another. If it were s/w that wouldn't seem probable.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] GeorgeP:
Yes. Assuming the bluetooth stack is part of the firmware, i.e., part of MK1, then all three units should have had exactly the same bluetooth software, so only the hardware was what was different. That is why I characterized it as a hardware problem. That said, given the principle of the equivalence of hardware and software, a software update may be a way of fixing the problem.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] Duly.noted:
My Bluetooth keyboard and mouse Work separately but together they are both Crazy no disconnects but repeating key presses and Jumpy mouse. But if I turn wifi Off or connect to a 5GHz network Its all gravy
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] dpersuhn:
Having been in electronics engineering and telecommunications (including wireless) engineering for the last 15 years, this smacks of a low level driver problem to me.

TO BarryH_GEG's comment about my position not answering the K810 working after swapping hardware, I can only say that my idea fully supports this. Iagree that there have been hardware issues, but I fail to see why you're stuck on the notion that hardware and software issues must be mutually exclusive. Just because you replaced defective hardware and the K810 started working properly doesn't mean there can't still be a software issue that affects other input devices. Using the same argument, I could conclude that my hardware is good because the first tablet didn't work with the wedge and the second one did when using the same firmware. I continue to hold the same position that both the hardware and software have experienced defects. Hardware defects affecting all input devices, software defects being a bit more selective.

For further clarification about the possibility of the devices all being from the same batch. The first was purchased in Orlando on release day. It was exchanged in Pittsburgh in November, exchanged again in Tampa in early January, exchanged again today in Pittsburgh. I'll keep returning this tablet every 44 days until BB stops me or Samsung fixes this issue.

As to this being academic, it is in a way. I like solving problems like this (it's why I got into engineering in the first place), but more importantly want to lay a smoking gun at Samsung's proverbial feet and help force the issue to be addressed by showing clear cut evidence that Samsung can't refute. If they continue to ignore it, I guess the videos start and they can then beg me to take them down like the flaming chargers for their phones. All in all, I'm becoming less and less tolerant of poor quality technology items as time goes on. Maybe I can help do something about that, maybe not. I intend to give it the old college try...
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] BclingergFJ:
Repeat letters/numbers: try Null Input Method.

Via my Note 3
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] Hahahalalala:
I am experiencing BT keyboard lag when I type. Also English (US) pops up randomly, any way to fix it? When the English (US) pops up it lags even more. Thanks

---------- Post added at 02:54 AM ---------- Previous post was at 02:28 AM ----------

Mines lagging when I try to type a document or basically longer typing. It works fine for short internet comments or seraches.

For example, in LecutreNotes and QuickOffice - the lag is horrid.

Anyway to fix this?
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] BarryH_GEG:
Having had cradle-to-grave product responsibility (including having those of your ilk report to me) at major multinational companies for 30 years, I'd bet you a paycheck that this is h/w-related. I've had to absorb untold cost in various positions due to engineers swearing things are bullet proof only to have to redesign a product post-deployment and blow support cost estimates by factors because of returns/repairs.

As for the BT s/w, it's most likely Samsung's and not Google's anyway. 4.2 (AOSP) had a ton of BT issues that Samsung's devices were immune from. So they either used their own low level BT code or heavily tweaked Google's. If they are using their own or heavily modified BT s/w there's nothing to say that it's different between 4.3 and 4.4 unless there was some compelling reason for them to change it.

You and I can argue pedigrees and theories until we turn purple and not correctly identify the problem going off of such anecdotal evidence as presented here. Not knowing how many people use HID BT devices on their N10.1-14 we don't even know if this issue affects a small number of devices or is a pandemic. No one's reported any widespread or common BT problems with anything but HID devices; and even that's been random. If the BT s/w was indeed borked you'd think the issues being reported would be broader than HID devices and a lot more frequent. My only issue and reason for responding to you is that by you espousing a s/w theory people could buy-in to it and not return their devices when they have the opportunity. Then, if it is h/w, they'd be screwed.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] dpersuhn:
In nearly every post, I've reiterated the point that people should return and keep returning devices that don't work properly regardless of whether the issue is hardware or software related. The high return rate hopefully will get the attention of the retailers, who have a way bigger stick to shake at Samsung than we do.

As for arguing pedigree, I couldn't care less where you're from or what you purport to have been responsible for managing. I didn't post that background info to get into a pi$$ing match or even for your benefit, I did it so people would understand the angle I'm looking at this from and any bias that may result. I may be completely wrong. I have no stake in anything other than wanting the problem completely resolved and three hardware swaps later, it still isn't. I'll swap again in another 43 days if the problem hasn't been solved just so I reset the timer. Hell, I'd love nothing more than for this to be a hardware issue that a simple swap would resolve, but that just doesn't seem to be fixing the entire problem in my case, so I'm digging deeper.

Anyone who reads these threads has seen the "last word" behavior from you before, so I don't really need to say more about that. That said, I'm not going to waste any more of my time addressing your posts. Instead, I'm going to keep digging at technical aspects of this issue to whatever end I can.

Thanks for your input, I agree that hardware issues have been found and may still persist, and I'll say once again that folks should return these these tablets UNTIL they have one that works exactly as they need it to, regardless of what the underlying cause may be. I don't need to be right, but I do think this problem hasn't been completely solved, even with hardware replacements. For all I know, Murphy could be riding my shoulder and I could have the worst possible luck in the world. The probability of that just decreases with every iteration of hardware swapout.