yashsingh1/xdaforums huggingface dataset:
[Nexus 6  General] compuw22c:
In my quest to resolve my Bluetooth issues (mainly interference issues between my moto 360 which is BT le and my car not being able to connect when the watch is on and in range). I've found many people complaining that many bluetooth issues popped up after Google switched to using BlueDroid for the Bluetooth stack around android 4.4. I came across this project https://code.google.com/p/aosp-bluez/https://code.google.com/p/aosp-bluez/ which attempts to build Bluez (the previous default Bluetooth stack) back in to android 4.4 & 5.0 (and above possibly).

Any ROM devs care to chime in on whether they'd be willing to try this in their build? I'm not against trying to build it myself but it sounds as though I'll need some drivers that may or may not be available for the N6 as it is for the N5. Any help, advice or a point in the right direction would be greatly appreciated. Thanks!
[Nexus 6  General] Arthur4ik:
bump
[Nexus 6 Q&A, Help & Troubleshooting] already_taken:
Hi, I have a Nexus 6 (Stock, Rooted, v5.0.1) and a machine with Mac OS X v10.10.3

I'm trying to make USB Tethering working (Using the N6's internet on the OS X machine) but I don't see it in OS X 'Network Preferences')

I tried this HoRNDIS: USB tethering driver for Mac OS X [0] but even that doesn't help.

Google's support page on this topic [1] says Note: USB tethering isn’t available on computers running Mac OS.

Has anyone found a solution or sees this config working?

(PS: I like USB Tethering over WiFi because it consumes less battery on my Nexus and OS X machine. Also, my Nexus charges while sharing)

0. joshuawise.com/horndis

1. support.google.com/nexus/answer/2812516?hl=en
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] ostriches3064:
Since we still don't have lollipop, a real root, or boot loader unlock, I was thinking about getting a lg g3 from Swappa. Thoughts? Thanks in advance.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] adrynalyne:
Two words:

Underpowered GPU.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Harry44:
Wait for the G4 if you do anything.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] SchmidtA99:
I 2nd the thought on waiting for the g4.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] ostriches3064:
They seem like pretty much the same phone except for the g3 is way cheaper. So if I get a new phone, it'll be the g3.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] adrynalyne:
Its not, but either of them is a step down from the Turbo in several areas.

The Turbo has some difficulty with frame rate and the resolution, how do you think a GPU that is 40% slower fares?
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] wadamean:
Both surely aren't the same phone. Why would you think that? Internals have been significantly improved, camera, display, buttons on back, cpu and gpu, software.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Galaxo60:
If you are going to drop the Turbo, you should do it for a Maxx in first place because of your complaints.

If there is no way to get a Maxx, you should get a Nexus 6.

If you don't feel comfortable with the size or you don't like it, I still wait for the LG G4 instead of buying the G3, it has several improvements and the first impressions says that the phone is well built and really fast despite the 808 processor.

:cool:
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Im Saint:
I think if you really look at them closely and note the way the LG Extravert 2's keyboard slides out, you'll find it's a dynamic change from the casual flip open approach of LG's Revere 3. However, both are still going to give you the stunning 2 inch display that you crave. It's a tossup, but I think you should definitely go with the the LG E2. It's where the true design is.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Slartibartfast_:
The G3 is a great phone, especially after you debloat it. Yes, the hardware is not as good as the G4 and the Turbo and it's not super snappy - performance feels like on the Samsung S5 for example, at least to me.

I would wait a bit until the G4 is out and the G3 drops in price significantly. Of course, if you can afford the G4, go for it.

BTW if you do get the G3, make sure you get the 32GB/3GB variants and not the 16GB/2GB type
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] maxpower7:
I actually switched from the G3 to the Turbo despite the lack of Lollipop. The G3 just isn't a particularly snappy phone. It's not *slow*, per se, but it's also not particularly *fast* either. It's also not especially smooth. This is of course because the Adreno 330 GPU just isn't quite up to the task of driving a 1440p display, as well as LG's inexcusable lack of software optimization. The Turbo is so much better than the G3 even without Lollipop. It's your life, but I wouldn't recommend making the switch.
[T-Mobile LG G3] zero061099:
OK so my phone screen got smashed up prertty good...so i got a new screen and replaced it and checked thoroughly to be sure it was installed properly which i did ..BUT device will not power on at all nor will it show led when plugged into charger...i should also add that it did not power on or show charger led after screen broke. would anyone know what part may be damaged to cause this? I did disassemble whole phone and didnt notice any physical damage..circuitry etc...tried a a couple different batteries and chargers also..any help would be appreciated thx
[Nexus 6 Q&A, Help & Troubleshooting] *Tar*:
If I flash the 2.46 zip after reboot the app want to update again?!

Gesendet von meinem Nexus 6
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
2.46 is "old" now, lol. anyways, the update in the play store is for the app. thats normal. update the app. and sometimes your supersu will get too old, and itll ask you to update your su binaries, through the app.
[Nexus 6 Q&A, Help & Troubleshooting] *Tar*:
Yes there is no way to update through the app if I do so and flash via twrp after reboot there is no effect.... Same as before?

Gesendet von meinem Nexus 6
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
i dont quite know what you are trying to update, but here is supersu 2.49 http://download.chainfire.eu/740/SuperSU/BETA-SuperSU-v2.49.zip :)
[Nexus 6 Q&A, Help & Troubleshooting] *Tar*:
Thank you Sir, this Beta works

Gesendet von meinem Nexus 6
[Nexus 6 Q&A, Help & Troubleshooting] zephiK:
I wouldn't necessarily say 2.46 is old. Yes, 2.49 exists but 2.49 is a beta and 2.46 is the "stable" version while 2.49 is being tested.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
you know what i meant :p

its not old at all, but the apk has been updated since. its odd, old is old. but in android, something relatively new can be considered "old".
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] sangweb:
My phone is rooted and I've accidently click on Install Update and now my phone is rebooting into recovery and trying to install the updates. I've taking the battery out but everytime I put it back it goes to recovery again. How can I cancel this update? I don't want to loose root. Currently running 4.4.3. TIA.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] bulsara:
Samething happened to me and now I'm stuck without root on 4.4.4 1st update got installed and 2nd update failed.
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] sangweb:
Figured it out, take out the battery, hold down home + volume down + power, it goes to custom OS with triangle and exclamatory, press volume down to cancel. Phone reboot with software update unsuccessful.
[Xperia Z3 Q&A, Help & Troubleshooting] kbadone:
I bought Z3 LTE from Sony Store last week but I returned it because it had edge light bleed problem on the left side and I returned it. I ordered a second unit few days ago and I received it and seems it has the same thin light edge bleed as pictured below.

Note this is only visible at an extreme angle and is not visible straight on or looking at the phone at a small angle. Also it's only visible on non-black colored background

Is that normal for and LCD screen? should I return it, or don't worry about it?

Thanks!
[Xperia Z3 Q&A, Help & Troubleshooting] LitoNi:
your chances of finding a perfect panel is basically "zero." if there arent any dead pixels and the backlight bleeding doest affect your viewing experiences then just stick with it. the chances of you getting a more defected one is higher.

you should also go into dial pad and test it with the service menu by inputting

*#*#service#*#*
[Xperia Z3 Q&A, Help & Troubleshooting] abhinav.tella:
I believe that is normal.
[Xperia Z3 Q&A, Help & Troubleshooting] kbadone:
I ran a complete diagnostics when I received the phone. Luckily everything passed and got zero sight of dead pixels, stuck pixels or clouding! Its not the first time I have seen this, I had similar problem with my xperia S, Z and Z1. So its seems like its a normal thing

I'll take your advice and stick with it. :good:
[Upgrading, Modifying and Unlocking] doalvares:
Hello,

Can anyone tell me were to find the instructions and files I need to change my SPV E600 into a HTC S620 (Spanish)?

Thank you very much for your help.
[Verizon Samsung Galaxy S 4] buckeyestargazer:
I'm seeking a bit of advice...

About 6 months ago I bought a Verizon GS4 for my father who is technically illiterate. I rooted the phone and got rid of most of the bloatware that would have just confused him. I did not install a custom rom or recovery etc, just kept the stock OS. He has been using the phone for the past six months. However he recently did something to the phone that may have bricked it (don't ask me what cause I have no idea).

Now when powering up the phone it goes straight to the Android recovery menu. I've tried wiping cache and doing a factory reset, but it still goes straight to the stock recovery. Another strange thing is that with the power completely off when I plug the charger in the phone will vibrate in pulses about 4 seconds apart continuously.

Any ideas what can be done about this? If I have to I can try to get the phone back with ODIN but I wanted to seek advice first. Thanks in advance.
[Verizon Samsung Galaxy S 4] Illogi.xbone:
The most effective way would be to Odin. Now you can just disable the bloatware and if you either get the ota to 5.0.1 or install a custom launcher hide the ones you can't.

---------- Post added at 10:47 AM ---------- Previous post was at 10:42 AM ----------

What build are you on currently? Don't forget to backup the info on your device :)
[Verizon Samsung Galaxy S 4] buckeyestargazer:
So at this point I'm thinking my only option is to restore with ODIN. I believe the phone is NC5. Will the OTA to 5.0.1 mess things up because the phone is rooted? Or perhaps I should root at all and just disable the bloatware...that's probably the best thing at this point.
[Verizon Samsung Galaxy S 4] Illogi.xbone:
The OTA will remove root. However disabling apps is a decent alternative to uninstalling them. Personally, anymore I only root basic phones that have very limited internal memory. The OTA is smooth and it works fairly well from my use for a day.
[Samsung Galaxy Nexus] mb_3000:
I want to get a heart rate monitor but it says it works only with devices that have bluetooth 4.0 (BLE)

I'm running CM 11. does anybody know if whether my bluetooth is 3 or 4? thanks!
[Galaxy Note 8.0 (Tablet) General] TheBigBentley:
Take a look at [MENTION=767379]Samsungmobile[/MENTION]UK's Tweet: https://twitter.com/SamsungMobileUK/status/591908863659618304?s=09

Unless Samsung is just trolling, this is pretty awesome.
[Galaxy Note 8.0 (Tablet) General] Mr.201:
F yeah!
[Galaxy Note 8.0 (Tablet) General] PauloRMag:
Any news?
[Galaxy Note 8.0 (Tablet) General] gooberdude:
well, i had already known that... with too many issue from 4.4.x and their issues with the S6 and other lolly poop issues, i expect august plus or minus a month. i hope it works better than kit kak, so i can replace the updated tablet's 4.4.2 with 5.0 and sell it for a profet.
[Galaxy Note 8.0 (Tablet) General] SecretVN:
I love meterial design. Hope this release will out soon
[Galaxy Note 8.0 (Tablet) General] TheBigBentley:
I had saw the usual sites saying it was coming but that was way back last year and hadn't seen any new info recently so I figured it was squashed. With all Samsung's phones getting updated now, I would assume shortly after summer too.
[Galaxy Note 8.0 (Tablet) General] sputnik767:
Yea, this device came out in April 2013. It is now May 2015, well outside the 18 month support window. Keep dreaming guys, ain't gonna happen.
[Galaxy Note 8.0 (Tablet) General] the Doctor:
Conflicting messages:

Samsung Gulf does it again, says no Lollipop for Samsung Galaxy Note 8.0

A good enough reason to stay on CM 12.2 nightlies.
[Galaxy Note 8.0 (Tablet) General] jazzespresso:
Correct, but official Samsung Denmark said it will get, but depends on region by region. Also heard Note II won't be getting it, but Samsung Korea said it will be getting lollipop (depends which version of Note II).

so it is really hard to say if it is getting it or not, but I still have some hope, it may see lollipop.

Talking about CM 12.2 nightlies, it is buggy and its ugly, but that's personal preference of course.
[Galaxy Note 8.0 (Tablet) General] Mr.201:
Even if some region cant get lollipop, just flash the one that get it lel :p .

dont even talk about cm12.1, so many bug even at application level there's something unresolved yet. not to mention the screen glitch, camera & call. the worst part, sleep animation.
[Galaxy Note 8.0 (Tablet) General] ticktockonthedot:
It would be great if they could get the official Lollipop release to our tablets, however the CM versions are pretty decent at the moment.
[Galaxy Note 8.0 (Tablet) General] cybershawngates:
Except netflix doesn't work on any of them
[Galaxy Note 8.0 (Tablet) General] jazzespresso:
Looks like Galaxy Note 2 will be getting Lollipop, if you think that, this device is released in October 2012, and our Note 8.0 released around April 2013, this may give us a little hope that our device may see lollipop, of course we never be sure for 100%, but at least there's still a little bit hope...

http://www.youmobile.org/blogs/entry/Samsung-Officially-Confirms-Lollipop-update-for-Galaxy-Note-2-and-Note-2-4G-NOT-all-Regions
[Galaxy Note 8.0 (Tablet) General] DarkGuyver:
I hope we will be seeing lolipop for the Note 8.0. I love my Note 8.0 it is a excellent tablet.
[Galaxy Note 8.0 (Tablet) General] JosephRaphael:
it looks like it's canceled http://www.youmobile.org/blogs/entry/Samsung-Galaxy-Note-8-0-official-Android-5-0-Lollipop-update-Canceled-due-to-hardware-limitations
[Omni Features Development] Entropy512:
PLEASE - No generic "This is awesome" or "Thank you!" posts. In fact, unless you're a themer or ROM developer with technical questions about this project, please refrain from cluttering the thread for the time being. This is NOT ready for users yet and needs a lot of work before it will be.

So, it has come up multiple times that users want some way to theme their devices. The problem is that until recently, the only option for that was CyanogenMod's theme engine. Unfortunately, integrating this is problematic for many ROMs - while it's fine for cherry-pickers who don't care about understanding what they're throwing into their project, it's a big issue for someone who does not want to put 13,000 lines of code into their project in a single patch. (CMTE is 13,000 lines of changes in frameworks/base, which is the very core of Android.) Also, it has been known to have resource usage and performance issues.

Over the past year, Sony has worked on getting a runtime resource overlay (RRO) implementation merged into Android. Most of the implementation was in Android 5.0, and a few bugfixes were in AOSP master until Android 5.1 was released.

A few months ago, a few developers figured out how to use RRO for theming. This system was called Layers, and initially appeared to have a huge amount of potential. Unfortunately, for various reasons, the system stagnated. The original set of commits to implement Layers had a whole pile of issues and clearly had not gone through code review, and when attempts were made to fix these issues, the Layers team wanted to make no further changes. For Omni, a core requirement we have for any theme system is that it cannot affect the user experience when no theme is in use/installed. Layers fails this criteria. (For example, in AOSP, the text on the battery history graph is pure black with no transparency. In Layers, it is mapped to "exposed_primary_text_light" which is a shade of black that includes transparency. There is no way for an overlay to change the other graphical elements that reference this resource without also affecting the battery history graph text, and vice versa. There were numerous other cases of "colors redefined" and "multiple different colors mapped to a single resource".)

I've been talking with members of a few project (including Slim and LiquidSmooth) about taking the basic concept behind Layers and fleshing it out into a mature system that addresses the various issues with Layers. Also, there's a desire to try and implement as much compatibility with CyanogenMod themes as possible without making excessive sacrifices (bloat, major mangling of Sony's RRO approach to facilitate compatibility with legacy themes... Despite nearly all themes requiring a rearchitecture for Lollipop...) in order to make it easier for themers to support this new approach.
[Omni Features Development] Entropy512:
Proposed Roadmap and Status

Here's a proposed roadmap I discussed with some guys from Slim and LS in a discussion on G+. None of this is set in stone though.

1) Merge CM's resource exposure commits. While there are many aspects of CMTE I dislike, these are unambiguously superior to the Layers resource exposure commits and I find nothing objectionable to any of them I've looked at so far, although they have yet to go through full review. STATUS: Up on Gerrit, they seem good.

2) Write a Python script that handles translating the overlays of a CMTE theme to one compatible with the new system - STATUS: Semi-working, but requires item 4 and fails for any theme that uses the "common" resource overlay. Themes that don't use "common" (like Mono and FlatshadeUI) can be translated in 3-4 minutes. Well-formed themes that use "common" require typically 20-30 minutes to manually dereference any "common" references. Some themes rely on some hacks CM has to handle incomplete styles in overlays and thus won't be supportable without hacks that may be undesirable.

3) Implement support for loading overlays from somewhere on /data - STATUS: Not started yet. Needs some good security gurus/SELinux guys to do right.

4) Implement support for overlays being able to reference their own resources. CMTE has this, I haven't quite figured out how they implemented it as it's 13,000 lines of code changes to sift through. - STATUS: See the commit list, this is currently working, however it is "proof of concept" quality

5) Implement support for a "common" overlay - many CMTE themes use this and more are using it as time goes on - STATUS: Not started yet. This may not be possible without architectural mangling to a degree that is undesirable

6) Well, this is more in parallel with items 4/5, but implement an app for managing overlays - it has to be after 3 though. Someone who sucks less than I do at UI/UX stuff needs to do this. :) - STATUS: Obviously not started yet. I've had a few people express interest in this stuff.

7) Longterm goal - Implement support for parsing a CMTE theme in the manager app. Gives similar results to CMTE, except the big difference is putting the "heavy lifting" in an app instead of frameworks/base. This keeps the really nasty code separate from the core frameworks and thus more maintainable. - STATUS: Not even close to started. There are some components of CMTE that I really dislike and this may not be possible to do without those components. It's also far more likely to fail in ways that make a themer look bad for something not necessarily their fault.

Ideally it should be able to provide fairly high compatibility with CMTE but without the system bloat and performance impacts that CMTE seems to entail.﻿
[Omni Features Development] Entropy512:
Show me the Code! (Patches)

THESE PATCHES ARE A PROOF-OF-CONCEPT/WORK IN PROGRESS. DO NOT MERGE THESE INTO ANY PROJECT. I will NOT work with anyone who merges these before they are ready!

You can submit them to your own Gerrit for review, but DON'T merge them.

Resource exposure patches

These are similar to the patches that make up "Type 2 Layers" - but to maximize compatibility with CM themes, we're using CM's resource naming. In fact, all of these patches are cherry-picks from CM

https://gerrit.omnirom.org/#/c/13292/

https://gerrit.omnirom.org/#/c/13293/

https://gerrit.omnirom.org/#/c/13294/

https://gerrit.omnirom.org/#/c/13295/

Allowing overlays to reference their own resources

A major limitation of the vanilla RRO implementation is that an overlay cannot reference its own resources. Sometimes this is annoying, in other cases (such as windowBackground attributes - see http://developer.android.com/guide/topics/ui/themes.html ), it makes doing certain things impossible. One of my main goals has been to find the minimum amount of change to allow this. Currently, the patches below are also all extracted from CMTE's frameworks/base megacommit. If this architecture is preserved I'm going to fix authorship of these commits, but right now I'm hoping to use these to gain ideas for a better way to do this and in the process rewrite them. These commits in their current implementation have some serious architectural limitations.

https://gerrit.omnirom.org/#/c/13346/ - The core implementation. This allows overlays to use their own resources. I'm in the process of analyzing this to determine if there's a way to do this without the current limitations it has. Specifically, if you attempt to use a "standard" overlay with package ID 0x7f, the overlay will completely fail and cause severe issues.

https://gerrit.omnirom.org/13347/ - Treat a few other PackageIDs as being "static" packages. I'm still in the process of reading through Android's code to figure out the differences between static and dynamic references. Overlays must be one of these packageIDs or they will fail.

https://gerrit.omnirom.org/13350/ - Allow aapt to override the packageID by specifying it as an argument to -x - this is needed to produce overlays that don't bork the system

Overlay best-fit hacks

https://gerrit.omnirom.org/#/c/13324/ - With standard RRO, if an overlay only has one resolution of resource, and the overlaid package has a resource that is a better fit (for example, overlay only has xxhdpi and device is xhdpi), the overlaid package's resource would get used. The end result in Layers is that some overlays would behave inconsistently on some devices. (For example, I've never seen a Layers overlay for Hangouts properly theme chat bubbles on any of my devices...)

Misc other fixes

https://gerrit.omnirom.org/#/c/13356/ - Quick settings tiles have a hardcoded AnimatedVectorDrawable class. This doesn't need to be hardcoded and can be a generic Drawable - for example, some themers want to use a RippleDrawable here. This commit is from Steve Kondik
[Omni Features Development] Entropy512:
Porting CMTE Themes

*Documentation on how to port a CMTE theme to the new system goes here*
[Omni Features Development] Entropy512:
More leftovers

Original leftovers is going to be the porting guide
[Omni Features Development] skynet11:
Why not just call it Overlays Theme Engine?
[Omni Features Development] Entropy512:
Hmm, maybe... It's more likely to get confused with Layers though. It's already bad enough that so many users confuse Layers with vanilla RRO.