yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Q&A, Help & Troubleshooting] dmw_4814:
There is definitely a problem both with the GPS AND the data connection on the Note 3 vs. the Note 2!

I drive a tractor-trailer for a living and use Google Navigation constantly to find my destinations (I know it's routed for automobiles and not trucks; I'm intelligent enough to NOT drive my tractor-trailer down a road it's telling me to go down that I shouldn't!) - the Note 3 is CONSTANTLY losing it's GPS lock, and displays "Searching for GPS" on the screen. The only way I can get it back is to turn off GPS and then turn it back on. Then it'll sometimes work for just a couple of minutes, or a couple of hours before it happens again. Most of the time it's just 5-10 minutes before it loses GPS lock again. My Note 2 NEVER, not even once, did this!

I live in Phoenix, AZ and drive to Las Vegas several times a week to make deliveries. There are large areas where there's no data connection at all, and in some areas where my Note 2 had a 4G connection, the Note 3 has NO data connection whatsoever! And, I'm not talking a couple of miles here; I'm talking at least a 30 or 40 mile stretch of US 93.

Yesterday, I was driving across I-40 west in New Mexico, on my way back from Wichita, KS, and Google Navigation, when it was working, looked terrible on the screen - the roads were all fuzzy and "bloated" because, apparently, it wasn't downloading all the map data.

My Note 3 experience so far has been terrible (I'm experiencing a myriad of other problems, too - TERRIBLE Bluetooth call audio; sounds on the phone, except for my music being played through PowerAmp, just stopped working, even though ALL volumes were at maximum, had to reboot to get them working; screen is "jittery" when typing, it'll sometimes type multiple characters as if I'm rapidly pressing the keys, etc, etc!); I'm returning it today to AT&T for another one. If I have problems with that one, though, I'm returning it for another Note 2!

This makes me VERY sorry I sold my Note 2 on Craigslist! :(

Dennis
[Galaxy Note 3 Q&A, Help & Troubleshooting] maxpeet:
That is essentially what's happening with my ATT Note3.

GPS just drops in the middle of navigating; the notification-bar icon just goes away. I have to toggle GPS off and back on for it to work again. While it's working, it never works well; there's at least a 15sec 'lag' time from when I move to when the screen actually updates my position - but it never truly gets a precise location. I can go to a specific location 5 different times and I'll be 15 yards away in different directions each time.

This is in any of the various mapping/navigation/gps apps, but is most notable infuriating while Ingressing.
[Galaxy Note 3 Q&A, Help & Troubleshooting] McBain_666:
Weird that has never happened to me. Perhaps there is a background app that makes some confusion. I have extensively tested the GPS in the last days and I confirm that the only problem that I have is with the compass, rotating the phone a couple of times makes the GPS works fine. The navigation is very good so far. However this was always in the city where the reception is good and the 4G connection is always present.

Good luck
[Galaxy Note 3 Q&A, Help & Troubleshooting] ilordvader:
Im in Dubai UAE

& I never had a problem finding location till I got the Note 3

Google Maps just doesn't work

S4 worked best in Dubai for me
[Galaxy Note 3 Q&A, Help & Troubleshooting] knightnz:
I find the GPS in my Note 3 to be frequently almost useless. It has good days & bad days, but often it will take a significant length of time to get a lock (several minutes). The GPS in the Note 2 was fantastic, this one is rubbish.

The compass needs to be recalibrated after every reboot. I've used FasterFix and GPS Status to set a better NTP server and force-download AGPS data but it makes little difference.

It makes it a terrible device for trying to play Ingress.

If it can be eventually fixed in software, then great, but it may just be poor antenna design. Given the plethora of issues the Note 3 is having, it's not endearing me towards purchasing another Samsung device.
[Galaxy Note 3 Q&A, Help & Troubleshooting] findoms:
Hi guys,

according to this article:

mobilesyrup.com/2013/09/05/the-samsung-galaxy-note-3-is-the-most-interesting-smartphone-released-this-year-heres-why/

our Note 3 is capable of 1.5 A charging current which should be able to charge it under 2 hours. Mine takes about 2.5 hours with max current of 1.2 A. Is it just me or anyone else having these issues?
[Galaxy Note 3 Q&A, Help & Troubleshooting] STARK !ndustries:
I just received mine today and took almost 2hrs for full charge. Maybe few mins less than 2hrs.
[Galaxy Note 3 Q&A, Help & Troubleshooting] CorruptedSanity:
I've been monitoring my Note 3.

It always charges at 1.2A

Then when it hits 100%, it charges at 1.8A.
[Galaxy Note 3 Q&A, Help & Troubleshooting] hookerpuncher:
1 hr off and 2.5 when it was on to aquire a full charge.
[Galaxy Note 3 Q&A, Help & Troubleshooting] findoms:
Did you mean that your phone charged in 1 hour when switched off, mine took 2 hours and 10 minutes.
[Galaxy Note 3 Q&A, Help & Troubleshooting] hookerpuncher:
Yes. My phone was off and using the supplied Samsung USB Micro 3.0 cable and wall plug.

Will time it again tonight and see how it does.
[Galaxy Note 3 Q&A, Help & Troubleshooting] gorinnosho:
no issue for my note 3
[Nexus 7 Accessories] IDKHow2ShaveWithaRAZR:/:
http://www.minisuit.com/p-1290-mini...stand-slim-rubberized-non-slip-grip-back.aspx

Is it any good?
[Nexus 7 Accessories] thirtyisntdanu20:
I have this and I like it. Connects very easily.
[Nexus 7 Q&A, Help & Troubleshooting] IDKHow2ShaveWithaRAZR:/:
http://www.ebay.com/itm/like/390606676023?lpid=82

From that link, if you open the "components" dropdown menu, it allows you to select between the LCD Display, and the Touch Screen Digitizer.

Because I just cracked the glass, I should be able to get this Touch Screen Digitizer for only $30.

I'm afraid I won't be able to separate the two however.

Thanks in advance
[Verizon HTC One (M7)] beardedYoga:
So I have a couple general questions I wanted to get your guys take on.

Why does Verizon choose to have there phones locked down? The HTC One in particular but generally as well. Is it a method of preserving/increasing profit? Perceived threat to their network? Something else?

A follow up question which depends on how you feel about the first question. Are Verizon's reasons for locking down phones justified? Do you feel they have a right to do this? If you were a strictly moral person, do you have any dilemmas about this?

PS As a side note, I love having my phones unlocked with custom roms, and I am looking forward to getting my sonic S-Off back.
[Verizon HTC One (M7)] idq1i:
People screwing up their phones by crack flashing, and returning them to verizon for warranty when bricked.

Control of tethering.
[Verizon HTC One (M7)] CNexus:
Yeah, they say it's for the reasons above.

But given that, to begin with, the rooting community is a tiny slice of all mobile phone users, and then Verizon users are an even smaller portion of that. So I don't see why they even care. I highly doubt that even if ever single Verizon customer who does rooting messed up their expensive device it would cost Verizon more than .01% of their revenue, if even that.
[Verizon HTC One (M7)] TidusWulf:
It's all about quality control. Even if it is the fact that the vast minority root their phones, it's the minority of users who generate the majority of complaints (and that rule extends FAR beyond cell phone rooting, or cell phones in general). It takes 10 good comments to make up for one bad comment these days, and there just aren't enough good comments to go around.

How likely is it, if your unrooted phone has no physical damage that you'll suddenly find that it isn't booting up? How likely is it that, even if you don't want to do it, factory resetting your unrooted phone will fix whatever problem you're having?

Big Red's reputation, their entire brand, is built on reliability. NOT freedom.
[Verizon HTC One (M7)] mcampos7:
Hey guys feel free to elaborate as much as possible. I'm writing a term paper on unlocking bootloaders/s-off, legalities on our part and Verizon, security risk for us/Carrier, risks taken by us/Verizon, etc.. It's for a Information Security Course. I'll be creating a thread at some point but this is a good start for some sources!
[Verizon HTC One (M7)] sonicxml:
Another point would be that Verizon tries to cater to business/enterprise customers so allowing bootloader unlocking could pose a giant security flaw on devices that have classified data and are meant to be secure
[Verizon HTC One (M7)] Dark Jedi:
I think it's far less about tethering for free. They fixed that with getting rid of unlimited data. They saw they can make more money on teired data plans with coverages. Plus I am amazed at how many people on here has given up on their unlimited data plans just to get a subsidized phone.

Locked down phones is for more like people who roots and doesn't know what they are doing so they brick their phones and Verizon takes a hit having to replace it under warranty. Plus the security reasons companies are looking for. They don't want a phone that could be hacked in to giving away possible secret info. Last but not least is to keep people from taking their phones and flashing it to another carrier as we seen a few people has done on here and other forums. It's money they are not receiving and they want to put a stop to it.
[Verizon HTC One (M7)] 123421342:
I think they do it for tethering. Although you can use foxfi, root tethering is not stoppable unless verizon uses packet sniffing but even so, unlimited data is unlimited data. They also do it for security reasons as unlocking a corporate phone can be bad.
[Verizon HTC One (M7)] santod040:
I will admit, I skimmed all posts and see that most everyone has bought into what they want us to believe.

If it is to prevent unwanted warranty claims, then why would they not allow us to willingly void our warranty via HTCdev when we click the box that says so?

Rather then resort to undocumented or traceable ways of doing so in which case they are stuck with more returns for soft bricks, etc,..and are stuck accepting them because they chose to not take the easy way and let us void our warranty to begin with.

I just think all that warranty replacement crap is a bunch of nonsense and can't be their main incentive.

If it is, then they have their heads buried deeper then I thought and need to realize what I just stated above...
[Verizon HTC One (M7)] steddora:
A really good friend of mine has been a tech with sprint for nearly a decade. From what he has told me, about 27 of 100 phones they can't fix are due to installing non official software. While that's not the highest percentage with damage as the worst, it still is very costly for them to replace. Most of the guys he works with can tell if a phone has been "tampered" with. Even with such things as triangle away with the Samsung lines, they still can find out. Having a locked boot loader on this phone is just one way of attempting to slow the numbers.

As he would put it, most people who do try flashing and other modification methods have very little experience with the phones and their inner workings. A lot of these people end up bricking their phones and try turning them in for insurance claims or warranty which he deals with. He actually saved me some coin by getting me a screen for one of my s2's from a completely fried emmc that he says someone tried a bad flash with.

But yeah, keeping the people like that out of the phones is one of the major reasons as it can become costly to them... I call bs though, considering the amount of profit they actually make on each one of our accounts.

Sent from my One in Blue!
[Verizon HTC One (M7)] Zwitterion:
You are exactly right.

To be honest, there isn't much of a business case for a carrier, when serving as the reseller of a phone, to offer the freedom of an unlocked boot loader. The savvy of the general populace hasn't yet reached the point where the downside is offset by a marketable upside. Hell, most folks still **** around happily with iPhones which lack any freedom whatsoever.
[Verizon HTC One (M7)] josh995:
We can speculate all we want here. Verizon says they lock phones because it's better for the network.

http://bgr.com/2012/03/02/verizon-explains-locked-bootloader-stance-in-letter-to-fcc/

Whether or not anyone chooses to believe that is a matter of opinion, but this is pretty much as close to an answer from Verizon that we'll ever get.

Sent from my HTC One.
[Verizon HTC One (M7)] beardedYoga:
Very enlightening.

To comment on wanting the phones to be secure for corporate security... wouldn't the amazing track record of dev's who contribute here and other places sort of fly right in the face of that.

It seems that every single device that gains enough users has some kind of workaround or vulnerability to allow it to be unlocked. If the corporate world was worried about it, all they are doing is showing just how unable to lock it down the manufactures and carriers are.
[Verizon HTC One (M7)] Anthrax79:
Blah, blah, blah.... the network. that is just their excuse. They used it with the FTC to get by with rate limiting the LTE network. Some lame a$$ excuse about the CDMA legacy junk. Don't get me wrong I am sure that the old CDMA stuff may make the network less predictable, but not less stable. It is all about money, and VZW is the 800 pound gorilla that get to control what we have to deal with. Thank goodness we have talented and dedicated developers that almost always get around the blockades these fools put in place.
[Verizon HTC One (M7)] mobitote:
+1
[Verizon HTC One (M7)] jmotyka:
From what I was told over at elevate, the biggest problem they don't want to expierence again is our phones not being able to dial to the correct 911 dispatch. There apparently was an incident where a rooting user had a modified dialer apk that didn't allow him dial to the correct dispatch. In an emergency for Verizon that is worse case scenario. Then there's a lawsuit that might be filed to both HTC and Verizon.
[Verizon HTC One (M7)] nrfitchett4:
Gotta disagree. When you see people in this forum bragging about getting seven replacements, it does add up.

And it really is a PITA to figure out if it was user error or something wrong with the phone. It's all about risk mgmt
[HTC Wildfire S] devemousa:
hi xda users , can I turn off the security in S-on devices of htc wildfire s or other devices becasue I don't find solve of this proplem , and if I can't change the security from ( s-on ) to ( s-off ) can i install offical ruu or custom roms and can make htc wildfire s support all language like arabic language , thanks
[HTC Wildfire S] csoulr666:
This topic was discussed a lot some time ago, the threads regarding this have gone to older pages.......................Simply put, unlock your bootloader officially via htcdev.com..........It is the minimum needed to root and flash custom roms

It isn't S-OFF, but the next best thing as there aren't any proper software methods for S-OFF
[HTC Wildfire S] AFN:
if you only want Arabic and other langs upgrade your os to latest android 2.3.5 and choose your region from available ruu here
[General Topics] afxal:
Hello

May get some help to change my xda II mini from german to english
[Verizon HTC One (M7)] nscian12:
After the new software update when I'm playing music on my phone, and I want to change the music from my lockscreen it no longer shows up (I can't fastforward or pause) I've tried disabling my pebble, and I've tried turning off everything in accessibility
[Verizon HTC One (M7)] HypostaticOnion:
Did it do it from play music and using the widget lockscreen?

If I've helped, please hit the thanks button
[Verizon HTC One (M7)] nscian12:
No, I mean, there's a setting in security where you can control music from the lockscreen
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Zuggel:
I have a 7" kindle fire HD. When I first got it I rooted it with QemuRoot. I wasn't too worried about doing much, I just added halo launcher and the play store. Everything was good until the launcher quit working. To make a long story short, I had lost root and got it back via Bin4ry. Once again, was lazy and just installed the launcher and went about life.

I lost root again, restored it with Bin4ry and disable updates using KFFA. The launcher works, but I can't get it to be the home button default and there is a lot of junk on there from when I had a freetime membership for my kid.

I would like to reset the device to factory and start over, what do I need to do? Looking at KFFA options 3,4 or 22 look like they would apply, I just wanted to find out what is the preferred method to accomplish this without screwing anything up.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
Either 3 or 4 will work. If you don't remove OTA updates, the Kindle will get an updated pushed onto it and your root will break every time when the Kindle updates. So make sure to remove OTA updates using KFFA as well.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Zuggel:
So I ended up using option 4 and a factory cable, for some reason it would not boot into fast mode via regular usb cable in KFFF. When it got done rebooting, I got a message asking if I wanted to use kindle or holo launcher (which I had previously installed).

That bit confused my, i thought that it would also have been deleted during the restore process?!!? Holo launcher & locker are installed and appears fully functional. Like i said before I would like to get this back to factory and start over. Superuser is on there also, did I forget a step or is there something additional that I need to do? I do not see any other apps other than what it came with.

It did take me to the set up process like on a new kindle.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] stunts513:
Sounds like all it did was wipe the data folder. It has to go into fastboot to restore it to stock, if it doesn't want to do it during the process in kffa you can always use a mobile terminal on the kindle itself and type

su -c "reboot bootloader"
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
Did you use KFFA with a factory cord or a fastboot? When using KFFA, it is best to use a fastboot cord. Booting it into fastboot from USB can be done but I found it did not happen as often using KFFA. You can also use this tool here http://xdaforums.com/showthread.php?t=1951254 and he has a video at the bottom of this page http://androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock/

You can also try your steps again and try number 3.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Zuggel:
It was in fastboot, I used a factory cable to do so before I started KFFA. The screen said "fastboot kindle" or something to that effect.

That was my thought, to try it again, I just like to get other thoughts and opinions from those who are much more knowledgeable about andoid operating systems than myself. I will try another wipe tomorrow (option 3) and see if it has the desired effect.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Zuggel:
I tried option 3 twice with the same results. I am downloading KFHD and will give that a go tomorrow.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
KFHD?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Zuggel:
The link you gave me, that was the file name for the tool.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
Oh gotcha. Yea, that's a System.img Restore Tool. Same idea as KFFA but a different method.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Zuggel:
Correct.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
I tried to run the script myself and see exactly what you are talking about. I left a comment in Chris's thread. I'm sure he will give us the skinny on it.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
OK, so here is how I worked it tonight. KFFA is a great utility but something hiccuped today. So here is the work around I just did.

First thing is root is needed for the restore utility to work. So root using this http://xdaforums.com/showthread.php?t=2351201

Now you can restore to 7.2.3 and root (all one process) using KFHD System.img Restore. Choose the "KFHD_SRT_v1.3.0- 7.2.3 (separate option for restoring factory recovery)" download here http://xdaforums.com/showthread.php?t=1951254 This will root your tablet and give you a couple Gapps and Play Store.

Then use KFFA to "Disable Amazon OTA updates." Make sure to look for a Super User request right after you click to proceed so the process suceeds.

Now you can proceed with using the installed Play Store or installing a 2nd bootloadr/custom rom

This is the process that worked for me. Make sure you give the restore tool plenty of time to work. It can be done by booting your KFHD into fastboot by using fastboot commands or a factory cable. Here is a video concerning the restore tool listed https://www.youtube.com/watch?v=k-8lTMLCGfE
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Zuggel:
I didn't need to root, I have a factory cable (assuming that was why I needed root to get into fastboot?!?). I tried KFHD_SRT_v1.3.5- 7.3.0 and it worked fine, except for some reason I could not turn on wireless. I am trying it again to see if it works out better for me. If not, I will try version 1.3.0
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
You need root to use the restore tool, not get into fastboot, like I stated. If you are not rooted, you can not use the restore tool listed. Use the USB cord to root and the fastboot cord to restore. The fastboot cord to restore to 7.2.3 so you have a matching boot.IMG. Then when flashing a 2nd bootloader and custom rom, you will most likely not bootloop or get a red screen.

I don't mind helping but you should read the help I offer before disregarding. I never BS anyone one here. I really suggest you read some topics on this or you might end up with a paper weight.

---------- Post added at 01:49 AM ---------- Previous post was at 01:46 AM ----------
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Zuggel:
When I restored using KFHD, the image was already rooted, or so the title stated. When I replied I had already done what i replied about before I read your suggested route. It's still not right, so I am following your route and hoping the kids sleep long enough for me to finish it in one sitting!!
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Zuggel:
When I used Bin4ry, it added a second version of superuser to it (not sure if that is important or not), then I chose option 1 (Restore factory rooted with SuperSU) in KFHD. I now have a red triangle asking me to reboot or reset..
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Zuggel:
I ran option 1 with KFHD 1.3.5, back to working at least, only one version of superuser and the wireless is working. So far so good, and almost out of time right now.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] LinearEquation:
You did something wrong. Your lucky you only got a red triangle and not a red screen. You need to restore again. When you are done, before exiting, clear the CASHE and data (think this is option 3 but confirm). You should already have root so use KFHD_SRT_v1.3.0- 7.2.3 (separate option for restoring factory recovery.)

Always make sure ADB and allowing apps from unknown sources is turned on on your tablet. I always turn my tablet to never sleep or an hour so it stays away and turn the brightness up on the screen when modding. Every tool you use, reconfirm the settings are the same.