yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 General] Sudo77:
Pardon, but I am really getting tired of this efuse debate. If Samsung's Knox technical paper states that there is an OTP fuse there AND the bootloader code shows evidence of an efuse, then there really should be one. But... to be brutally fair, since the exact location of Mr. fuse isn't found, if you can provide some evidence to support otherwise, instead of just stating it, please share it or I will refuse it. It would give me, and other Snapdragon users great relief to know that fuses aren't used in devices anyway. It also just makes sense that different chip manufactures (Exynos & Qualcomm) have different ways of implementing Knox, whether it is hardware-assisted or not.

You better believe IMEI is changeable. There are programs that can write to nvram and therefore change IMEI itself. The point still stands, it is a poor method of server verification. IMEI doesn't have to be lost, simple efs corruption causing unreadable IMEI can falsify the verification depending on how the data is fetched. Again, unlike MAC which is burned onto the NIC and always stays constant as I was taught.

I agree when you say Samsung is cheap when using plastic, but it really doesn't bother me. I don't get why people hate on plastic so much, it has its own benefits. I also don't see why metal phones should last any longer, point be, if you deem the technology underneath the cover to be old, then you are bound to buy a new phone anyhow 1, 2 or 3 years later. However, what really bothers me about Samsung is their CONFOUNDED CRAPPY BLOATWARE. Especially Knox, that has hindered Samsung phones no matter how fast they have become. OT but damn.

---------- Post added at 06:27 AM ---------- Previous post was at 06:04 AM ----------

Very true. I was going to comment on the same, but glad you came first to break it to others...gently. LOL
[Galaxy Note 3 General] harold5249:
I hope in future the "knox cure" will exist. Or else Samsung is killing itself. Just like note 2 users, most of them are not upgrade their note 2 to note 3. I think note 4 sales will not be very high.
[G2 Q&A, Help & Troubleshooting] Noam23:
I came from the Samsung galaxy S2.

With the S2, when I turned ON the BT toggle at the notification bar, I would immediately get a screen where I could choose which BT device I would like to connect to. With the LG G2, I get no such screen. What a bummer, I thought this was part of Android...

In any case, this is the least of my problems, since the LG G2 has a much more severe one - unreliable Bluetooth connection.I think I got to the root of this problem though:

When you connect a device to the LG G2 using BT, you can choose two options for this device: "Phone audio" and/or "Media audio" (A2DP). You can tick both, or just one.

When I tick only one of them, I get perfect stable connection (but then I can only use it for phone, or for music, not both...). The problem is when I tick both of them. What happen is that when a call comes in, or when a call is finished, the G2 has trouble getting back to "Media audio" (A2DP), and usually the BT disconnects. So, the trouble seems to be in the change between "Media audio" and "phone audio", when the G2 is required to make this change, most chances a BT disconnection will result.

I have this exact problem with two totally different devices (both of them worked great with the Galaxy S2), these two devices are:

1. Pioneer DEH-P980BT car CD receiver unit.

2. Sony Ericsson MW600 wireless headset.

I have the LG G2 D802.
[G2 Q&A, Help & Troubleshooting] earlthepearl:
You can long press the Bluetooth icon in the power bar to access this screen. This works better for me since I always have my Bluetooth on for the car, but need quick access for my Creative Bluetooth speaker.
[G2 Q&A, Help & Troubleshooting] Noam23:
Yes I know, but as I said, this is the least of my problems regarding BT function with the G2....
[G2 Q&A, Help & Troubleshooting] djkinetic:
My bt is flawless call comes in it switches to phone audio then switches back to media after call has ended, never had any random disconnects. D800
[G2 Q&A, Help & Troubleshooting] Noam23:
The disconnections are not random, it happens when the phone needs to switch between media audio and phone audio.

Maybe this is a problem with the D802 only?
[G2 Q&A, Help & Troubleshooting] :
havent experienced these issues here so far myself!
[G2 Q&A, Help & Troubleshooting] mimidatabase:
No problem either, transition between audio and calls then back to audio operate smoothly (D802).

No disconection problem either.

But I do find the Bluetooth audio volume very low (compared to my previous iPhone 4 on the same car audio system), as reported by other users.
[G2 Q&A, Help & Troubleshooting] lvikel2:
i have sa,e error. no solve
[G2 Q&A, Help & Troubleshooting] s2sera2:
I'm having a similar issue. I have a uconnect 430 system in my Jeep, and every time I end a call, the bluetooth audio streaming playback doesn't quit on me, but continues at a slightly lower pitch, and slightly slower pace. Really bizarre, and I can correct it by disconnecting the phone and powering off the car stereo, then reconnecting everything. Haven't really tried to troubleshoot just yet but saw your post and thought I'd chime in.
[G2 Q&A, Help & Troubleshooting] Slinkynose:
I connect to my 2011 Hyundai Genesis Coupe. I have no connection issues, the phone switches from Wifi to Bluetooth well. If a call comes in I can answer and talk through the car, when I end the call it will switch back.

Some issues I have noticed that are different from my HTC One X:

1. When I switch to the Bluetooth input the audio plays then stops and I have to hit play on the car controls.

2. The audio clips and distorts periodically. I believe this is related to the bitrate of the audio, and may be on the Hyundai side. I mention it because it only occurred now that I use the G2.

3. The car controls will stop working seemingly at random, I have to use my phone to skip or pause. First world problems.

Edit: ATT D800 Rooted, CleanROM XE, had same issues on stock.
[G2 Q&A, Help & Troubleshooting] stevessvt:
TMo D801, 14 Toyota Corolla, no problems at all with it.
[G2 Q&A, Help & Troubleshooting] mgmgb:
BT audio works very well with my car also (D801), one thing that annoys me is that it automatically starts playing music upon BT connection. Is there a way of making it so that I have to do it manually?
[G2 Q&A, Help & Troubleshooting] tiguy99:
This!
[G2 Q&A, Help & Troubleshooting] :
I think a lot off people have old bluetooth equiptment that might not play nice with new. what version bluetooth does the equiptment have you are pairing with and are there any newer versions? Even though bluetooth is standardised if you search you will find often certain equiptment doesnt play nice with it, hence the supperted devices.

tiguy, Knowing not all devices have this is, is important info isnt it? Of course I have different equiptment, so it may not be representative.

Sent from my LG-D802
[G2 Q&A, Help & Troubleshooting] mgmgb:
Anyone?
[G2 Q&A, Help & Troubleshooting] xdafoundingmember:
My Bluetooth is flawless.
[G2 Q&A, Help & Troubleshooting] tiguy99:
At the moment I use my earpiece which is the Platronics Voyager Legend. It works flawless. I haven't done a car Bluetooth sync but from what I've read on the Web with my earpiece and other phones, i was very impressed that i have excellent call quality, sound & range when i listen to music directly on the earpiece
[G2 Q&A, Help & Troubleshooting] cptnmidnight:
I had to install a firmware update to my clarion for the exact same symptoms, I was also having issues with the phone freezing up during the switch between call/music.
[G2 Q&A, Help & Troubleshooting] hyperxguy:
It's just the opposite for me. I would like to have the music to autoplay (without hitting the play button on the Belkin BT... connected to my

2004NissanBoseUnit).

BT is great with my VS980 (with Malladus ROM).
[G2 Q&A, Help & Troubleshooting] mgmgb:
Ha well there's got to be a switch for this somewhere but I've had no luck finding it.
[G2 Q&A, Help & Troubleshooting] cptnmidnight:
Autoplay is a feature of the head unit, not the phone. I got in the habit of hitting the face remove button before I get out of the car. You might check the settings on the head unit for an option to disable it.
[G2 Q&A, Help & Troubleshooting] mgmgb:
Well if the above is correct then I'm completely confused. Now my phone no longer auto-plays and if I take a phone call while listening to music it will stop the music as normal but no longer returns to playing the music after the call is over.

This changed when I updated to kitkat the other day. I haven't made any changes at all to my car audio setup, the only thing that has changed is the phone OS.
[G2 Q&A, Help & Troubleshooting] TheSTiV:
Same problem for me. D802 running 4.4.2 on a Toyota head unit. My experience differs slightly though. Using the stock music app everything is fine but using either PowerAmp or Google Play Music results in some very strange behaviour ranging from my car head unit no longer responding to silent playback, i.e. the phone and car thinks something is playing but I get no audio. The leads me to believe it is app specific rather than the phone itself. Raised a bug with Google but waiting to hear anything back at the moment.
[G2 Q&A, Help & Troubleshooting] poochewer:
My prob is thatin BT settings under my 2013 model hyundai paired device it has "phone audio and Media audio" but the phone audio is greyed out and i cant check it. It is paired with the car but as i said "phone audio" is greyed out!:(
[G2 Q&A, Help & Troubleshooting] mhajii210:
Hardware problem

Hi guys. I just wanted to let you know your BT problems unfortunately might be a hardware issue. I was very surprised when the demo unit at a T-Mobile store did not have any problems connecting to the same wireless speaker my phone was having problems with. I did find an app called Xperia Z1 Bluetooth media fix at the Google Play Store that was an excellent workaround. Be sure to try that app if you're having problems, but ultimately you may have the same hardware issue I had. The only way to know for sure is to test things out with another LG G2. Please see my link at http://xdaforums.com/showthread.php?t=2749891 for more information. Good luck!

mhajii210
[G2 Q&A, Help & Troubleshooting] ak538cn:
I have been reading some people complaining about the Bluetooth button do not launching any application.

In my car stereo (DNX4230BT from Kenwood), music playback, aha radio and Garmin smart link are fine. Hands free calling also works, apart from the voice call button, which is greyed. With my Nexus 4 paired, instead, it launches google now and this allow me place voice commands and place calls hands free. This is a major flaw for me, since I have to stop to dial.
[G2 Q&A, Help & Troubleshooting] ak538cn:
Today I also paired my G2 with my bluetooth intercom Sena SMH5 inside my helmet. Same as above: music playback is fine but I get no action when I press the voice command button; it works on my Nexus 4.

I would like to know if there is anyone with G2 stock rom that has got buetooth voice command button to work on any device.
[G2 Q&A, Help & Troubleshooting] TheSTiV:
For anyone suffering with the BT issues. Flashing this fixed it for me. with the customized stock kernel also on the same page.
[Nexus 7 (2013) Q&A] CCT1:
I cannot get my N7 to accept the 15R update. I have tried OTA, have also tried flashing the zip and sideloading the zip through ADB..always get an error that looks to be a mismatch of the hash. So ultimately I will end up wiping and re-installing...but my question is more than just that. My N7 is rooted with NRT but with no other modifications. The only reason I rooted was so that I could use Titanium backup. I hear people constantly concerned that they will lose root after an OTA update. I don't understand this because re-rooting is so easy and takes only a couple of minutes. I am much more concerned with not being able to update and having to wipe the device. This requires lots more time and effort...even getting my wireless password into the device (63 digits) takes longer than re-rooting. I have to temporarily change the password on my router to something that I can type in, then change it back after cutting and pasting in my real password, which is too long and complicated to type.

What am I missing and also, is there anything else I can do to get 15R into the device? (I have SuperSU 1.65 already.)

Thanks for helping a newbie.
[Nexus 7 (2013) Q&A] sfhub:
Something changed after you rooted. It may not have been explicitly something you changed. It could have been one of the root apps you started using. For example stickmount will often result in the hash for debuggerd to fail.

If you post the exact error someone can probably guess what you installed that caused the hash failure. I assure you it only happens if a file was modified or deleted (unless you are one of the unfortunate with suspect eMMC memory that is corrupting on its own)

The quickest way to get JSS15R is to just use this post in JSS15R discussion thread. Use the nowipe factory option and it will preserve your data.

http://xdaforums.com/showthread.php?p=45671279#post45671279
[Nexus 7 (2013) Q&A] CCT1:
Thanks for the response...I will get into that thread suggested. For the future, if an app screws things up, will uninstalling it fix things or not? You mentioned Stickmount, which I have installed. I went ahead and uninstalled it, but results are the same.

When trying to flash the 15R zip, I get:

skipping MD5 check

no MD5 file found

assert failed-apply patch check [zip name]

error executing updater binary

error installing zip

this is all while booted temporarily into TWRP....I have stock recovery on the unit.

Could freezing useless apps (some system like Google Books and useless keyboards) with Titanium Backup cause the update to fail? I tried unfreezing everything that I had done...still no luck. I'm just trying to get a feel for what to do and not do in the future...

Thanks much!!
[Nexus 7 (2013) Q&A] CCT1:
OK...followed your thread ...read everything and since I saw an error about debuggered somewhere on my N7, I used your debuggered update, flashed it with TWRP and then was successful in flashing the 15R update.zip. So it must have been as you said...Stickmount was the problem and it messed up the debuggered file. I'm still wondering if freezing apps with Titanium backup will mess up an update or if I did not need to defrost everything before trying to flash the zip???

Thanks so much for the help...another success story and noob learning more and more about what the heck is going on in Android.
[Nexus 7 (2013) Q&A] sfhub:
It has nothing to do with freezing apps. Freezing apps won't have any negative effects on your ability to use an OTA successfully.

Stickmount backs up debuggerd, makes some changes to it, then restores the backup, but sometimes it gets out of sync. When it gets out of sync, your original debuggerd is lost even though there is a backup file because the backup is of the wrong file.

Uninstalling stickmount wouldn't have fixed this issue because it already made the modification to debuggerd.

Keep in mind, normally it isn't root that causes the OTA to fail. It is the use of those capabilities root gave you, to modify or remove files, either directly or indirectly through a 3rd-party app that causes the OTA to fail.
[Nexus 7 (2013) Q&A] CCT1:
Gotcha...thanks for the help...your debuggerd script fixed everything...I've put it away for possible future use. Titanium Backup and Stickmount are the only apps I have that require root...I will keep this in mind. To a lesser but similar extent than in Windows, I like to keep a system lean and mean....I think Android can benefit from this also.
[Ubuntu Touch Q&A, Help & Troubleshooting] eagleeyetom:
Try to re-download ~/bin/repo from google.
[Ubuntu Touch Q&A, Help & Troubleshooting] moocow1452:
Manually, or is there an arguement I need for Phablet Dev Bootstrap?
[Ubuntu Touch Q&A, Help & Troubleshooting] internest:
I have the same problem.:confused:
[Ubuntu Touch Q&A, Help & Troubleshooting] mcscruff:
you need to update repo :)

curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
[Off-topic] jab1a:
I am selling my M2000 so i can get a M5000, mine is only 2 months old, in mint condition,i have tomtom 5 software and all PIO's updated with latest speed cams etc, a DVD with all my collected software& some of the latest films shrunk to crystal clear quaulity,well over 1gb, Comes boxed almost as new, everything that came with it i have, its unlocked to any network,i can supply a Pay as you go SIM of your network choice if you would like. For any details or pictures please E-mail me and i will be happy to help. i will sell for £280 ono, it will be on Ebay from the end of this week with a reserve of £300, so nows your chance!!!

E-mail: JAB1A@LYCOS.CO.UK

p.s Even if you use it just for GPS then its still cheaper than buying a sole GPS system, plus you can play full movies etc
[General Questions and Answers] moeburn:
So I have a new Galaxy S3 I747 Bell Canada, and I'm thinking of rooting it, but I still have 11 months of warranty left. Now I know that I can just follow the complicated guides to 'unroot' it, if I need to send it back, but has that ever actually worked for anyone here?

Because think about it. If you need to send your phone back for warranty, it is probably broken, right? If your phone is broken, how can you possibly unroot it first? Sure there are some non-bricked reasons you could send your phone back, such as a broken camera or a small deadzone in the touchscreen, but I'm just worried that my phone will suffer a NAND flash breakdown (after that whole kefuffle in the news) or a malfunctioning CPU while in a rooted state.

But then I think, well if the NAND flash or CPU completely dies, will THEY even be able to tell if the phone is rooted? I mean sure they have tools where they can rip the flash out of the mobo and read it and see if it's rooted, but to do all that would cost them labour hours. I would imagine if I sent back a rooted phone with just a broken camera, they would turn on the phone and see the big "THIS PHONE IS ROOTED!!!" message and refuse my warranty, but if I can turn my phone on, I will unroot it before I send it in for a broken camera. But if the phone CANT turn on, would they really bother with all those low-level hardware tools to try and fix my phone and see if its rooted? Wouldn't they just send me a new phone, and possibly try and refurbish my broken one to resell, without ever noticing that its rooted?
[General Questions and Answers] MissionImprobable:
Depends on what your issue. Most of the buttons on my D2 stopped working and I had to send it in for warranty. Had to sbf and wipe and then it was fine. VZ has additional "root counter" features, but as you aren't using their device the standard unroot procedures should be fine. I think they take care of the on-board root counter.

If your phone is completely unusable then you're just out back. Obviously you can't take care of what you need to do if the phone isn't functioning at all. That said, depending on the damage they might not even be able to check for root anyway, and they just might not care. Also depends on your carrier's policies.
[General Questions and Answers] claudi82:
Honestly i don't recomend rooting ur phone on the the warranty period
[General Topics] Sig0431:
If this needs to be moved to a new location, please feel free to do so.

This all started when I noticed that my images with hash tags posted on Instagram (IG) were no longer receiving a short influx of "likes" after posted. It seemed that my hash tags were no longer working. After testing many images, uninstalling and reinstalling IG, creating a new account, using only 1 hash tag, etc my tags seemed to no longer be working. I even searched for the tags I used in images and found that my pictures did not show up on the search results.

Soon I stumbled upon what I believe is the issue that most are having when their hash tags do not seem to work anymore. I have sent many trouble tickets to IG, from within the app, via email, facebook, twitter etc. and have not even received an acknowledgement that they reviewed my email. I am hoping that posting here may:

1. Confirm that what I am seeing is also happening to others.

2. Find it's way to IG for them to investigate and fix.

OK enough background, lets get to it. If you are having the same issue of hash tags not working, I would like for you to do the following and let me know if you have the same results.

1. Upload a image to IG

2. Add 1 hash tag to the image (you can add more than one to continue to test this issue)

3. Post the image with the hash tag

4. click on the explore button and do a search for the hash tag you posted with your image.

5. If you are having the "hash tags are not working issue" more than likely you will not see your image at the top of the results

6. Start clicking on the search results images in order (top right to left) but I want you to take note of how long ago each picture was posted when you click on it (this is located in the top right when you click on the image. If you are having the same issue as I am, you will see that the images within the search results are no longer in order from new to old.

So in reality our hash tags are still working, but because there is no order to the search results, you could be a thousand images down even if you posted 2 seconds ago.

Please confirm if anyone realizes they found to have the same issue that I do. Also if there is anyone that has a way of bringing this to the attention of Instagram I would greatly appreciate it. I have offered to send IG screen shots and anything else they need but have not heard back from them. I have also tested this on the Galaxy S2 and my new Galaxy Note 3, as well as on three different accounts with the same results.

Thank you all for your time.
[Samsung Galaxy Nexus] mkhang:
Hey everyone! I recently (yes, just recently :/ ) updated the Verizon Galaxy Nexus from 4.1.2 to 4.2.2 this past weekend and I used the app "Voodoo OTA Rootkeeper" to keep root access while downloading the OTA. I didn't want to update to 4.2.2 but long story short, I did. I was unwilling to update since many people have had troubles getting wifi tether to work and I wanted to avoid that and keep running on 4.1.2 to keep wifi tether with no problems (Don't fix what's broken, right?). Well, I used another app "Root Checker" to validate my root access, and it says "Sorry! This device does not have proper root access." and I was wondering how I lost my root access in the process? Would anyone know by chance? I'm not too familiar with root anymore since I've had my phone rooted for over a year now using the 1-click toolkit that many people dislike. I was wondering what I should do next, in order to have root access once again. I don't want to run the risk of bricking my phone and having to pay big bucks for a new phone. Anything helps!!
[Samsung Galaxy Nexus] samersh72:
flash latest cwm with fastboot for your variant, and install supersu zip