yashsingh1/xdaforums huggingface dataset:
[Galaxy S6 Q&A, Help & Troubleshooting] skg27:
Galaxy S6 (S6 Edge, Edge+) and S7 (S7 Edge) support UHQ-BT codec developed by Samsung (don't mix with Samsung UHQ upscaler used in stock Music application). This codec allows audio transmittion via Bluetooth 4.0 at a pretty high resulution: 24 bit / 96 kHz (2 channels stereo). In order to be able to use this feature you must use Bluetooth audio device, which supports this codec, for example, headphones Samsung Level series. In order to enable UHQ-BT you need to download the application Samsung Level from Google Play Market and make sure that "UHQ" is enabled. 24 / 96 is the TOP possible limit of UHQ-BT codec for a pair S7 (S7E) + Level headphones. Of course it also depends on the audio file (stream) you're trying to play. If the file itself has low audio resolution with high compression then you cannot get high audio quality. The best audio quality will be when listening to audio files in lossless format (such as flac) with resolution 24 bit / 96 kHz. But there's also a question of how such high resolution was created. One thing is it was made from the original studio recording (made in 24, 36 or 48 bit resolution on professional equipment). And the other thing is if the source for lossless 24/96 audio file was a crappy mp3. A special case would be some vinyl-rip made by an enthusiast on some high-end analog - digital pair. You can find them with resolution as high as 24/192. But most of the time you get some background noise and vinyl crackle. So, the point of such high resolution for vinyl rips in the first place is rather doubtful in my opinion... Also, since UHQ-BT top capability is 24/96 audio resolution, there's no point in using 24/192 for our pair (S7 + Level headphones) UHQ-BT will downscale it to its 24/96 anyway... Other high-res BT codecs available: aptX HD, developed by Qualcomm, which supports HD audio with resolution 24/44, which is a little lower than UHQ-BT. Standard aptX supports CD-audio with resolution up to 16/44, which is even lower. Samsung Galaxy S6 (S6E) and S7 (S7E) support aptX, but do not support aptX HD. If you have a BT audio devise, which supports aptX and are unwilling to get Samsung Level series headphones (Level U, Level U Pro, Level U Pro ANC, Level On, etc...) then aptX supported quality with 16/44 resolution is the highest possible that you'll get. And if your headphones do not support aptX then you will get even lower resolution. The bottomline is get Samsung Level series headphones, if you want to get the highest BT wireless audio quality.

Now, as far as Samsung UHQ upscaler, which is built-in in the Samsung stock Music application, this is a feature, which increases audio resolution programmably. This helps to get the audio sound a little "more smooth" compared with original low-res quality. It removes to certain extent the "digitalness" of the sound, "making connection" between sound "dots" smoother. But it cannot make up high frequency sounds between dots, which may be lost due to low resolution and/or high compression. It simply "doesn't know" they existed.
[Galaxy S6 Q&A, Help & Troubleshooting] dat_in:
Hey guys. I swear when I say this that I had a S6 for 2 years and the old samsung music app allowed to enable the UHQ mode even when connected to standard Bluetooth headphones and scrappy speakers started aounding great. In fact I was just surprised at how much of a difference it made. But I updated the app and since then have never gotten it to work over Bluetooth. It still works for wired headphones. But honest to good this feature actually worked and made no difference to which speaker it was connected to.

So I am pretty sure there must be a way to get it to work it is definitely a software matter. I am sure some of you smart folks can figure it out.
[Galaxy S6 Q&A, Help & Troubleshooting] ttlatroo:
What if?

What if I have the S7 and Samsung Level wireless headphones along with the Samsung Level App and the uhq upscaler still is not accessible?
[Galaxy S6 Q&A, Help & Troubleshooting] Attakan:
Hi,

Samsung's own UHQA BT audio codec, such as APTx HD or LDAC, has a link bandwidth of 24/96 (512 kbps), but when I connected my Level u pro to my S7 (Exynos) and check it from the developer's menu, it connect with scalable audio codec 16/44. (256 kbps). And I can not change it. in this case 24/96 flac music quality is reduced to cd. Can someone who knows explain?
[Shield Tablet Q&A, Help & Troubleshooting] the_randomizer85:
Purchased a Shield K1 Tablet

Which will arrive this week, and there are things I would like to know about it, i.e notably on whether or not I should unlock and root it, despite the potential risk of doing so.

What I plan on using this for is primarily emulation (Snes through PSP and maybe Dolphin, no idea how well that works yet) :D That being said, are there things I should do to it?

Do as in, things I can root or flash to give myself the best possible experience, to get the most out of this? I've seen a lot of custom ROMs, Cyanogenmod (which I have on my

Nexus 7 2012, along with a dual boot OS). I have been thinking about having the stock Android 5.1.1, alongside Android 4.1.2 for the sake of Wii remote support since Google

foolishly broke that part of Bluetooth (and the part that never will be fixed again). The problem is, I don't know how hard or cumbersome it would be to do such a thing

without bricking the Shield tablet and ending up with a pricey paperweight. What tutorials, guides, etc should I look into before I consider such an undertaking? I want

to be sure I pick the right files and OS image(s) to install so I can do this right, if that makes sense. :cool:
[Shield Tablet Q&A, Help & Troubleshooting] koichirose:
I just bought it too and was coming from a Nexus 7 2012.

Rooted with the latest CM 12.1 nightly, no issues so far.

Wifi is slowish/buggy and the touchscreen has some issues, but afaik these issues are there on stock, too.

Just get the latest CM12.1 from their site, flash it with TWRP. I had issues with open gapps and ended up using CM's gapps.
[Shield Tablet Q&A, Help & Troubleshooting] the_randomizer85:
Fair enough, and I know that no device is perfect, everything has their own set of issues, so I don't think I'll regret getting a Shield Tablet, that much I know. I was going to get a Samsung Tab E 9.6, but the specs just didn't figure, esp. for someone who wants more power, you know? What about the Android OS ROM you install it with? Should I go with Android 5.1.1 or dual boot it with 4.1.2 instead so I can have Wii remote support? Thanks. :p
[Shield Tablet Q&A, Help & Troubleshooting] koichirose:
I don't know, that's your choice. I don't have that requirement, so I went with CM12 (5.1.1), single OS
[Shield Tablet Q&A, Help & Troubleshooting] the_randomizer85:
Fair enough, I'll keep looking around the forums to gauge what I need to do. I can't help but feel a bit nervous on rooting and voiding the warranty on a device I just spend 200 bucks on, maybe that's just me though :laugh:
[Shield Tablet Q&A, Help & Troubleshooting] Exile1975:
Nvidia has stated that it will still honor the warranty despite it being unlocked or rooted in most cases. I'm just gonna guess that unless you accidentally wipe your bootloader, or use an overclocked kernel that fries it you should be good. What they said is if YOU fubar it that voids the warranty, but if it's anything normally covered by warranty your good.

That said, I rooted, unlocked, and installed an oc kernel as well as recovery within an hour of receiving mine and it runs beautifully. Better than pure stock actually.
[Shield Tablet Q&A, Help & Troubleshooting] the_randomizer85:
Okay, I wasn't 100% sure, only device ever rooted and unlocked was a Nexus 7 2012, never had a problem with it once I got it up and running. I don't feel comfortable with OC at all, as the power is

definitely more than enough for my needs, if that makes any sense. That being said, I don't know what kernel I need since this is my second time ever doing something like this, a little green in the gills so to speak (sad, I know). Anyways, would you guys advise to having dual boot install on this, or just a better 5.1.1 Android ROM than the stock version? I feel a bit overwhelmed at it all, and I don't know what tutorial I should truly follow, that's why I feel overwhelmed, you know?

Reasons for the tablet:

1 - The specs are insanely powerful for emulator apps, my Nexus 7 struggles with even 2D PSP games and some PSX games, lots of stuttering in the audio department, so my primary use is gaming

2 - Multimedia, movies, YT, music and so on

So really, I don't need anything fancy OS wise, just enough to help get the most out of it without having to overclock the hardware. What order would I need to do everything in? Are there good step by step guides for people like me?
[Shield Tablet Q&A, Help & Troubleshooting] wiQbold:
http://xdaforums.com/shield-tablet/development/root-root-nvidia-shield-tablet-lollipop-t2972316

INSTALL DRIVER

-enable Developer Options

-enable Debugging Bridge

-do a 'adb devices' and check the dialog on your mobile and allow it 'every time'

-shutdown

-hold Volume down and Powerbutton at same time

if the bootloader showed up

-do a 'fastboot devices' if it shows your device online then

-do 'fastboot oem unlock'

after that you have flash your recovery

go to the directory where the file is and

-do 'fastboot flash recovery your_file_here'

after that you can reboot to bootloader and go to recovery

copy the SuperSu.zip which you downloaded at chainfires site or on xda and push it to your internal memory (/sdcard)

and flash it over recovery.

reboot enjoy!
[Shield Tablet Q&A, Help & Troubleshooting] the_randomizer85:
So I just follow the guide on the thread, or do I follow the guide you just posted?. The reason I ask is because in the thread's guide, past the parts where it said to install the ADB driver and then the USB drivers for the device, I'm not sure what "debugging bridge" is, unless you meant enable USB debugging, IDK.

- Enable USB developer mode

- Enable USB debugging

- Copy the recovery image and supersu.zip to where the ADB install folder is

- Open the program to open a CMD window to the install location

- Type "adb reboot bootloader"

- Etc

I mean, because the two guides are confusing me more, the forum guide, the thread, how it's worded...now I don't know. Sorry. Is that thread and your guide the same thing, all leading to ultimate unlock and root the device using ADB and the recovery image? And is it not feasible to install Android 4.1.2 as a dual boot OS image so I can test out the Wii Classic Controller since Google broke that part of the Bluetooth code in 4.2+?
[Shield Tablet Q&A, Help & Troubleshooting] wiQbold:
there is another tutorial from SuperPichu I think. this is the best for my understanding but I didn 't find it , up in hurry(?)

http://xdaforums.com/shield-tablet/development/root-root-lollipop-t2945044

and yes. usb-debugging :o
[Shield Tablet Q&A, Help & Troubleshooting] the_randomizer85:
Okay, that thread says flashed to OTA 2.0 already, not entirely sure what that means, to be honest, or of the bootloader is locked on it, haven't gotten it yet. I take it I follow the first thread you posted, then

the one above?
[Shield Tablet Q&A, Help & Troubleshooting] wiQbold:
it is a old thread. It s for kitkat..

I think you go like I said.

be sure. adb drivers are installed

Developer Options

Usb debugging

cmd

'adb devices'

check dialog

'adb reboot-bootloader'

'fastboot devices'

look for output

'fastboot oem unlock`

'fastboot flash recovery /directory/to/your-recovery-file'

'fastboot reboot-bootloader'

go to recovery

flash SuperSU.zip

reboot
[Shield Tablet Q&A, Help & Troubleshooting] the_randomizer85:
And I go into recovery mode by holding vol. down and power, right? And in that mode I flash the SuperSu.zip correct? And I did get the recovery.img from nVidia's source, which I assume is the one I use in Command. Okay. Rebooting I assume is well, heh, also by holding down power. I also noticed both of those threads have the OS name Lollipop in the thread title.
[Galaxy S 4 Q&A, Help & Troubleshooting] stm2015:
My S4 got random reboots

My S4 is running Lollipop (updated few months ago) stock rom w/o root, and recently I experienced random reboot few time a day, usually when I launch the stock browser / facebook app. The strange thing is that when the phone is restarted, battery drops to few % only.

I've tried to replace a spare battery, the same thing still happen.

Factory reset is the last hope I have, but before I doing this, any other tricks that can help? Battery calibration?

Please help me.......:cowboy::cowboy:
[Galaxy S 4 Q&A, Help & Troubleshooting] Lennyz1988:
Battery calibration is a myth and does not exist. Perform a factory reset.
[Galaxy S 4 Q&A, Help & Troubleshooting] lordodin912:
If worried about losing apps, you could root, install titanium backup, backup apps then move/copy titanium backup folder to SD card, factory reset/Odin, root, install titanium backup, copy/move TB folder back to original location then open TB and restore apps, then unroot. Edit: Will void warranty, thanks for correcting me [MENTION=4271351]sutharmukesh88[/MENTION]
[Galaxy S 4 Q&A, Help & Troubleshooting] sutharmukesh88:
Rooting will trip security counter. will void warranry
[Galaxy S 4 Q&A, Help & Troubleshooting] lordodin912:
On 4.4 you could at least, my bad. I thought you could use those one-click apps like kingroot as long as you didn't change recovery or anything, guess not?

http://www.droidviews.com/root-galaxy-s4-on-lollipop-without-tripping-knox/
[LG G4c Questions & Answers] citione:
Hi there,

I'm a newbie here and this is my first post. I bought a chinese LG G4C (sub model H525N) (made for Vodafone, german market) and i'm in Argentina where the LTE frequencies that work (in the whole country) are AWS/Band 4 (1700 / 2100 Mhz) and APT/Band 28 (700 Mhz) but... my cell phone won't work on this! I can use 3G (whichs displays as "H" or "H+" and are good, sometimes... But the main thing to write here is the reason i can access the hidden menu (via 277634#*#) where i can see 15 LTE bands to choose from, but when i select Band 4, Band 28, and many others (as a test mode) i get a "FAIL" message as a response... the ones that i can pick are Band 3, 7, 8 and 20, none of these are good for me, so i was wondering if some cool soul could decrypt the way i can change my settings to get a functional LTE cell phone!

More info you may need from the device:

My cell phone is unlock to use any SIM card, now i'm working with Movistar Arentina.

I have selected as "Net Mode" or whatever (i have my cell phone in spanish language) 2G/3G/4G

According to Movistar Argnetina i have the right APN configuration (Provided by default when i inserted the sim card the first time)

In Hidden Menu: Field Test/Modem Settings/Network Mode i selected "Automatic"

In Hidden Menu: Field Test/Modem Settings/RAT Selection i selected "GSM / WCDMA / LTE auto"

Cheers,

Martín
[AT&T Samsung Galaxy S 5] mickeybeats:
Is anyone currently working on a G870A OF2/3 root?

I know this question has been asked a lot around here in the past year, but they all dead end with useless information. So, I'm asking again on the 14th of December 2015; Is there anyone working on a root for the Samsung Galaxy S5 Active (SM-G870A) after the of2/3 ota update. Also, I've seen a lot of answers to the question of weather my device can be downgraded and they've been all over the place. I'm sorry if there is a bit of repetition but there has been too much confusion on this subject and I'm looking for clarification. If I've broken any rules without realizing then please let me know. Thanks.

EDIT: With a little more research I was able to clear up my second question, but my first still stands: Is anyone working on a root for the SM-G870A and can you point me in the direction of a blog so I'm not hanging so far off the edge of my seat waiting for it.
[LG V10 Q&A, Help & Troubleshooting] ajamils:
I'm using unlocked Tmobile V10 on AT&T and everything works fine except for Visual VM. I download the apk from an old link on the forum. It's installed fine but when I try to activate it, it just gets stuck at connecting and nothing happens.

Does anyone has any suggestions for fixing this issue?
[Nexus Player Android Development] npjohnson:
Reserved

Hey Guys! This is PureNexus for the ADT-1 (molly). Hope you enjoy!

Bugs:

*Nexus Remote doesn't pair, henceforth, no Remote Mic yet (this may not even be possible)
*Rear Button doesn't work in Recovery
*LED Control only possible via Kernel Settings, see LED section below
*A few Play Store apps are missing, probably a missing identifier, should be solved soon
*On device mute doesn't function, remains at the lowest volume, muting the TV itself works fine

LED Color Control Instructions

We are working on a GUI App to do this. For now, the default color is Cyan, though the color is controlable via Kernel Settings, these can be manually set using form a root prompt:

echo [I]value[/I] > /sys/devices/platform/molly-led/[I]color[/I]

You will first need to echo 0 to the "pulsing" color to enable customization.

Where /value/ can = 0-255, and color can be "red", "blue", or "green". You can mix and match different values of different colors to get a variety of secondary colors, i.e. 255 > red, 255 > blue = purple, while 255 > red, and 150 > blue = hot pink.

We have also set up a "pulsing" color, which will accept any value from 0 (off) and 1 (on), will give the same LED pulse found on stock, and run through the range of supported colors.

To disable the LED, echo 0 to all the colors.

A script I set up that goes through all the colors can be found here: https://www.androidfilehost.com/?fid=24269982087018750
[Nexus Player Android Development] npjohnson:
Reserved
[Nexus Player Android Development] dcarr622:
Wow, awesome work. Will be trying this shortly. Any known issues that I should be aware of that would impact regular use?
[Nexus Player Android Development] r3pwn:
Well, LED Control is still in the works. I have a bit more to do on it, but it's almost ready. Other than that, I am not aware of any major deal-breaking issues.
[Nexus Player Android Development] dcarr622:
Sweetness. Over on G+ it was mentioned that Cast wasn't fully working - does that mean it doesn't work at all, or that it only works for a restricted set of apps like the ADT-1 does on stock?
[Nexus Player Android Development] r3pwn:
I'm not entirely sure. I haven't installed PureNexus on my ADT-1. I'm more focused on CM13.
[Nexus Player Android Development] npjohnson:
Its broken. Unfortunately that's the hand-off with Marshmallow for now ): We are working on it though!

Check the bugs list in the 2nd post.
[Nexus Player Android Development] bigboolean:
I definitely need to flash this later on! I was one of the lucky winners to receive an ADT-1 last July, and I've been using it for development and as a consumer box (it works well with most Android TV games and emulators).
[Nexus Player Android Development] mastermind278:
I have to admit you guys have done a great job with this ROM. Everything seems to run smoothly. Thank you so much for helping resurrect the ADT-1.

Just a FYI - the Kodi ZIP does not seem to install via TWRP at least on my ADT-1. It's not a huge deal since you can just move the two files to the proper directory in the /sdcard.
[Nexus Player Android Development] benpage:
I flashed TWRP easily enough, but it doesn't seem to recognize any of my USB keyboards. Does anyone have any ideas?
[Nexus Player Android Development] BRICK0044:
Thank you for keeping the ADT-1 moving forward. I have mine on 5.0.2 and everything I have on it works great. I want to upgrade but I'm wondering if it is fair to say that the apps that don't work with the Nexus Player on 6.0.1 won't work on this either. Or is this a whole different beast? Just don't want to set it all up and not have my Xfinity app work. I will try it after Xmas if no one answers by then. Thanks again.
[Nexus Player Android Development] npjohnson:
Needs to be a mouse.

Yeah. If it doesn't work on the NP on 6.0.1, most likely won't work here.
[Nexus Player Android Development] BRICK0044:
Thank you, I will flash this as soon as Xfinity fixes their app. Thank you for your hard work and Happy Holidays
[Nexus Player Android Development] dhacker29:
Updated build https://www.androidfilehost.com/?fid=24269982087020889 Netflix and Cast functionality fixed. No known issues now that I am aware of.
[Nexus Player Android Development] porschet:
Great work! I've been waiting for someone to create a ROM for this device. I put my ADT-1 away when it lost official Google support and got a Nexus Player which I love. I'll definitely be flashing this during the winter break for my bedroom. Good to know that the powerful hardware of this device isn't going to waste. Much appreciated!
[Nexus Player Android Development] npjohnson:
Added to OP.

Also updated the changelog.
[Nexus Player Android Development] bryantjopplin:
Came over from the Samsung side huh? Well good to see you over here in nexus land.
[Nexus Player Android Development] npjohnson:
Yup. (: I'm on the N6 and N6P too.
[Nexus Player Android Development] bryantjopplin:
Wish I had the 6p but the 6 is still a great phone. Also running the s4 mdk daily as a work phone. You do anything for the n6 yet?
[Nexus Player Android Development] ryaniskira:
Any more updates?
[Nexus Player Android Development] Jhoopes517:
Haven't talked since then.
[Nexus Player Android Development] npjohnson:
Nougat boots. But crashes as setupwizard. Any dev's who want to help can, but I am not the best with userspace issues lol, I specialize in kernel and hardware work.
[Nexus Player Android Development] ryaniskira:
What Gapps package are you using?
[Nexus Player Android Development] npjohnson:
Lol. I should clarify off the bat this is not a GApps problem.

Without GApps we get the same issue, except Launcher3 crashes on loop then. I think it may be related to our hacky GL implementation but I can't prove anything yet.
[Nexus Player Android Development] mannnyh714:
is there someone in orange county california that can help me update the firmware for my adt-1?
[Nexus Player Android Development] rgill420:
is anyone able to cast anything besides youtube anymore. Still on the original version of the cast app but all of sudden nothing casts.
[Nexus Player Android Development] X_Panthers_X:
First i would like to thank all Developers

now i found 3 roms please which one i need to use (stable and best )

1-pure_nexus_molly-6.0.1-20151218

2-pure_nexus_molly-6.0.1-20160202

3-pure_nexus_molly-6.0.1-20160410

can any one help us and make tutorial video from the beginning

how to root and how flash recovery and to end

and can i take backup with any app software or throw PC to original Android ADT-1 with lollipop before start flash to restore if i make any mistake when flashing

thanks in advanced
[Nexus Player Android Development] gil_happy:
Can someone here help me out? I am trying to first install TWRP on my ADT-1, and I have what I think is a dumb question - how do I run the 'fastboot' commands from my PC to the ADT-1? Normally when I have done this in the past on different devices, I just connect a USB cable from my PC to the tablet, etc. However, since the ADT-1 has a USB port (currently a USB dongle is connected for the bluetooth keyboard) and my PC has a USB port, so it would almost be like male-to-male which cannot be correct.

Is this done over IP, do I load TWRP onto a thumb drive and connect to the USB port, etc?

Thanks
[Nexus Player Android Development] meathammer386:
I think you need to side load it with an otg cable have everything you need on the device then do your commands
[Nexus Player Android Development] gil_happy:
Thank you.... I ended up purchasing a developer cable / debug cable from Ebay and was able to install TWRP, etc.
[Nexus Player Android Development] dony71:
[MENTION=5848265]npjohnson[/MENTION] : nougat dev still going on?
[Nexus Player Android Development] npjohnson:
Yes. I was prepared to turn official Lineage 14.1 builds on for Molly (with everything working except for L1), but then a platform change broke boot. Haven't had time to fix it yet.