yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] springer.music:
I'd also like to know this.

Does anyone know how to enable diag mode on the Nexus 6?
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
as far as i know, no nexus ever had a QXDM/QPST mode.
[Nexus 6 Q&A, Help & Troubleshooting] springer.music:
On the Nexus 5 it was possible to enable Diag mode by flashing a custom kernel:

http://xdaforums.com/google-nexus-5/help/dev-enable-diagnostic-mode-t2535478/page10

I was wondering whether a similar thing could be done on the Nexus 6 as well
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
it wasnt a diagnostic mode on the n5, it was a menu for sprint. and it proved to be no use for any other provider. and if you had root, you could always look into /system/app/ and see its apk.
[Nexus 6 Q&A, Help & Troubleshooting] springer.music:
I see.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
it was a way for sprint users to get more info about their network coverage.
[Nexus 6 Q&A, Help & Troubleshooting] springer.music:
I was actually trying to find out whether it was possible to unlock/enable additional LTE bands on the Nexus 6.

For example some of the US bands on the XT1100 (eg. 2, 4, 17) and some additional European bands on the XT1103 (e.g 20).

http://xdaforums.com/crossdevice-dev/sony/thread-progress-please-leave-im-updating-t2871269
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
definitely can try. i know that on the nexus 5 it was only figured out recently if you can add other frequencies..
[Nexus 6 Q&A, Help & Troubleshooting] springer.music:
Would love to try but without diag mode it sounds pretty impossible for the phone to be recognised by QPST...
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
try this method(from the nexus 5, also no diagnostic mode).. http://xdaforums.com/google-nexus-5/general/radio-enable-lte-band-3-nexus-5-d820-t2928561

---------- Post added at 07:10 PM ---------- Previous post was at 07:07 PM ----------

edit.. never mind, he aleady has the nexus 5 files available, so you probably wont get anything new from it. but still..
[Nexus 6 Q&A, Help & Troubleshooting] Larzzzz82:
I used that menu and actually got the n5 to work on att. Had data, no voice or SMS. The cellular network in the settings menu did not give me an option that worked.
[Nexus 6 Q&A, Help & Troubleshooting] simms22:
the nexus 5 already works on att, straight out of the box!
[Nexus 6 Q&A, Help & Troubleshooting] Larzzzz82:
Straight out of the box perhaps. I had already taken sprint and t mobile for test drives before trying att. I was comparing and wanting to get away from big red until I saw my choices. Thankfully the n6 works on vzw.
[Nexus 6 Q&A, Help & Troubleshooting] springer.music:
It looks like they are actually using a special LG driver for Diag mode instead of the standard Google USB driver.

We'd need some sort of Motorola Diag driver that works with the Nexus 6.
[Nexus 6 Q&A, Help & Troubleshooting] springer.music:
Some progress:

http://xdaforums.com/crossdevice-dev/sony/thread-progress-please-leave-im-updating-t2871269/post58434858#post58434858

As I mentioned in that post, I've now left the US and I'm in Europe at the moment, so I can't check whether the added LTE bands actually work.
[Nexus 6 Q&A, Help & Troubleshooting] paychex:
didn't work for me
[Nexus 6 Q&A, Help & Troubleshooting] springer.music:
Thanks for trying.

Just to get a clearer picture, what exactly didn't work for you?

Which model did you try this on? XT1100 or XT1103?

Where you able to put the Nexus 6 in diagnostic mode and connect it to QXDM?

Did the new NV values at lines 6828 and 6829 stick after a reboot?

If the answer to the previous 2 questions was yes, did you pop in a local LTE-enabled sim card? (for "local" I mean a sim card from the region where you want to enable the additional LTE bands, and not a foreign sim card - if you are overseas at the moment - as some network providers have not enabled LTE roaming yet).

Furthermore, did you also try the very same sim card with another (local and LTE capable) phone to see whether it actually gets any LTE connection?

Sorry about all the questions. I just want to get as much info as possible.
[Nexus 6 Q&A, Help & Troubleshooting] paychex:
XT1103. Couldn't even get it into diagnostic mode
[Nexus 6 Q&A, Help & Troubleshooting] springer.music:
Follow these steps to get it into diag mode.

1. Power off the phone

2. Press and keep pressed both volume up and down and at simultaneously press the power button. This will take you to the bootloader menu.

3. Use the volume buttons to navigate to the "BP Tools" option and press the power button once. This will reboot the phone in diagnostic mode.

4. Connect the phone to a Windows PC with a USB cable. Windows will try and fail to install the drivers. Go to Windows device manager to see the failed drivers. Follow the other steps from link I posted earlier to proceed and update the correct Motorola drivers
[General Topics] Planterz:
Stability depends on device. CM11 is superbly stable on a Nexus 4 or 5, but could be extremely buggy on some random cheap Chinese phone bought from aliexpress because lots of people use and develop for Nexuses, but only a handful of people will be working on that Chinese one. There are also often hardware issues.
[General Topics] XXchrisXX:
Thanks for your reply, i totally agree with you but if you have rightly read my topic you can read that I dont write about device specific features. If I can reproduce a handfull bugs everytime, on every CM11 rom, than that are real bugs on which CM should take care. I will also show some here but I need time to tanslate it here and to write it.

I also totally agree if a device have no maintainer it cant be tested and made fully working - but the problem most of the time is that there are A LOT of people who make their own kernels, own custom roms on base of CM11 and they COULD be maintainer of the device but dont want it or cant do it because of CM itself. If you look how CM is treating the people and not comunicate with them you will understand why there is a lack of maintainer and so many people which COULD be a maintainer because of the knowledge. But that is a other topic. CM need to change his way to talk with the community. If there are bugs, which are easy to reproduce and they will be reported to bugtracker and CM is closing it because the log is not attached, because the reporter CANT BRINGT IT, BUT the bug can be EASILY reproduced WITHOUT A LOG, than it is CMs fault. People want to help and they (CM) close the bugreports. It should be in their interest to test every bugreport to MAYBE find a potential bug. Also look at the bugtracker, there are issues which were reported for years and CM dont care about it. Look for the lack of using the calendar without a google account for example. On the other hand side: They add features which nobody wanted to have and mostly the people dont use. where is ther sense here?
[General Topics] 350Rocket:
Personally, I quit using any cm or cm based ROMs on my nexus because it seemed to lack speed and stability compared to stock or aosp based ROMs.

I had better luck with early custom lollipop ROMs than with cm. Right now I'm using slimkat until black themed lollipop ROMs are stable and bug free.

So basically, I agree that cm should be more stable. But I don't really care cause there are lots of good options out there instead of cm.
[General Topics] karabasan61:
Ow mannnnn .. Thank you so much !!! you are pro !!!
[General Topics] zelendel:
Well first thing is that bugs happen when you use open source drivers and software. This is because it is not coded just for a single device like the OEM drivers and software is.

Second CM is not required to do anything. That includes fixing bugs that they don't care about.

Next. And to be flatly honest they have no reason to talk to the community. Can't blame them as most have nothing more productive to say then "duh this is busted" why talk to those people when you can talk to people that can offer advise and maybe help salve an issue. Nor are they required to post any update at all.

Devs have the right to post a build in the OP and never post support, leaving all support up to the user's.

It doesn't matter if you can produce the error. They have their rules about posting bug reports. If you don't follow them and it gets closed without it even being looked at well then that's your fault.

If you want stable then stay stock. Or learn to fix it yourself. There is no obligation for anyone to even touch aosp based code. Even Google has most stopped updating those apps and files.

Now as for you saying device independent issues. The issue here is that one device could be rebooting every ten min but other devices don't do it.

The only device as a company they need to worry about is the one that sells with their roms. All others are hobby projects and treated as such.
[General Topics] zelendel:
Once again CM has not posted here in years. AOSP will never be completely stable. Deal with it. and a news flash the oneplusone 2 will not have CM. They have already signed a contract exclusive in some places with another company.

Now to end this. Here is a link. Have a good read.

http://xdaforums.com/showpost.php?p=16682226&postcount=2441
[General Topics] Mazda:
Ok so I've read the cluster that is your post [MENTION=6212097]XXchrisXX[/MENTION] and I have to say a few things

First off, I'm probably the last person you would ever see saying anything remotely nice about CM but what's right is right....

1. There is no moral commitment or obligation or ANYTHING that CM (the open source side of things) has to follow. You are getting a FREE product. In exchange your feedback may or may not be useful to the developers and device maintainers. You signed no contract. You didn't agree to anything with CyanogenMod or any of it's developers or maintainers. XDA-Developers is and always has been a AT-YOUR-OWN-RISK type of site.

As stated above, you can stick with the stock ROM from the OEM if you want stability and some kind of warranty.

2. There are two different sides of CM. There is the open source side which is what you're griping about and then there's the company, CM Inc.

One is run by volunteers and hundreds of contributors (Open Source side) and the other one is run by employees who are under contract (CM Inc). Don't confuse the two and think that you can hold the open source side to the same things you hold the company to.

Do many employees from CM Inc. contribute to the Open Source side? Yes, but that is a hobby. You want a warranty and someone to yell at for not fixing bugs? Go buy a One Plus One and get you a warranty, simple as that!

3. Who are you to tell them (the Open Source side of CM) what they can and can't do? You should be lucky that your device is even supported by CM or any AOSP based custom ROM.

You talk about Samsung and other OEMs but what you fail to realize is that most OEMs give you a one and done. They give you kitkat and that's it.........they TOO move on to bigger and better things.

Don't be foolish here and think that your device that's 3 years old is going to run KitKat like a champ. You say you "understand" about open source drivers but yet continue to argue your pointless cluster because you think that CM (the open source side) should behave like the company.

YOU DON'T UNDERSTAND! If you did, you would of never made this post and thank your lucky stars that your device even got on CM's radar for support.

Again, I know CM inc has done some messed up things in the past and are arguably run by a circus but what I hate more then them is ungrateful people like yourself.

Stop while you're ahead [MENTION=6212097]XXchrisXX[/MENTION]
[General Topics] Entropy512:
What... the... fk...

Seriously... It's obvious you've violated XDA's "search before posting" rules.

Now, you've given enough information that you're obviously a haxxinos4 user. (You mention N7000 so probably a 4210, but I sort of recall seeing something indicating you might have a 4412 device...)

The only devices that actually have received benefits from Cyngn corporate are their "Cyanogen OS" devices. Oppo N1 and OnePlus One. Those are the two devices where Cyngn corporate staff have NDAs signed with the OEM and Qualcomm (and other suppliers) to fully support every piece of hardware within the device. Now, if your complaint is about those devices (which Cyngn HAS ****ed up too), you have a right to complain. But to be honest, you'll find little sympathy here since the Cyngn corporate guys and XDA don't really get along.

If you're a Haxxinos4 user, and actually PAID ATTENTION, you'd know that Samsung has continually bent the community over and ****ed them time and time again. (Especially in 2012, with the Superbrick fiasco and their broken promises at BABBQ 2012). You'd also know that basically everyone that USED to be a Haxxinos4 maintainer either retired from Android development or left CM after the Focal relicensing disaster. (And even after moving to Omni, Haxxinos4 is pretty much dead to most of us...)

So Mazda is right... While he (nor I) have any love for Cyngn (Kondick has blocked me on G+ for calling him out on various things back during the Focal relicensing fiasco - and I used to be the CM maintainer for multiple Haxxinos4 devices and the Oppo Find5)... Your post just reeks of "typical ungrateful user who can't even search to find the basic backstory of their device"...

Funny thing: Oppo N1 was Cyngn's first official device. Its predecessor, the Find 5, was entirely maintained by people who left CM to found Omni after the Focal relicensing fiasco. All of those people were former Haxxinos4 maintainers who were sick and tired of Samsung's bull**** already.
[General Topics] mazwoz:
[MENTION=6212097]XXchrisXX[/MENTION] wow, you ungrateful twerp. If you don't like it, try another ROM. I'm anti CM after the things the company side did to the community, but they don't deserve this.

There are other ROMs that are more stable and have more features. Try those. Look at liquid smooth, omni, Dirty Unicorns... Way more options than just CM. But if you go to those Roms with this type of attitude expect zero support.
[General Topics] Saint Isaiah:
Sorry to sound like a moron from left field, but what did CM do to the community? I've been out of the loop.
[General Topics] mazwoz:
They took the work of hundreds, forced people to relicense their work so that CM owned it, and then made millions on some contracts when they became a company. None of that money went to the people who spent years working on cm and helping them be what they are. It went to a few key people, and that's it. This people signed contracts with cm inc. Since then they have poached the lead developers from other ROMs to work with them, eliminating any possible competition.
[General Topics] Saint Isaiah:
Wow that's super ****ty! I'm guessing this is related to the work they did with the OnePlus One phone? Either way, thanks for the info.
[General Topics] mazwoz:
Yes and no, they did all of this before the OnePlus. The first CM phone was the Oppo N1, that contact came about a few months after this went down. Omni ROM was founded because of this.
[General Topics] Entropy512:
I can't dig up a direct link currently, but do a search for "Focal relicensing"

I think there's a link to Guillaume's post on the issue from the CM wikipedia page, but I'm not sure.
[General Topics] mazwoz:
http://xdaforums.com/showthread.php?t=2451752
[General Topics] jerdog:
To the OP [MENTION=6212097]XXchrisXX[/MENTION] or is it [MENTION=6094361]Noteguy[/MENTION]? I am so confused. One of you has 1 post, the other one of you has 4 (all of them in here). Would the real OP PLEASE STAND UP????

That being said, it's quite obvious that you have nothing to offer this community except for whinging - and if you were the only one doing that on XDA then I would say the community should take note and listen to what you have to say. BUT - seeing as you're just another whiny user I think we can all, CM included, just ignore you.
[General Topics] TheBr0ken:
I can't say anything more than what [MENTION=591147]Entropy512[/MENTION] and [MENTION=1289361]Mazda[/MENTION] has already said. You must be very young, because you seriously remind me of my kids sometimes. Get stuff for free, but still complain because its not 100% to your liking. Not sure about Germany, but here we call that ungrateful. Long ago I was not satisfied with the lack of development for my aging device, instead of calling out developers that work, have a family and spend what little free time they have giving me free stuff, I learned to develop myself as to not bother them. Its not plug and play. Most do this for themselves and share. Ranting will only cause them not to share. If you want to kill support for your device faster than the hurdles that are already present with trying to piece together the little bits of open source code we can use, then your on the right track. If you want continued support then sometimes a simple Thank you works wonders. Nobody is making a living off of this (open source side at least). Donations are nice, but I know first hand that both [MENTION=1289361]Mazda[/MENTION] and I have on certain occasions returned donations to users. We don't do it because of the money, we do it because its fun. Don't take the fun out of it is all I'm saying. Be grateful that you aren't stuck on OE jellybean or less software. You owe/need the development community more than the developers do, the sooner you realize that, the better off you'll be.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Morrpheus:
Hi,

I always make a backup in recovery before flashing a new ROM or MOD. I am using CWM Recovery v6.0.4.7

I sometimes have the problem that a restore is "corrupted". Restoring in recovery is successful, but after restoring I have problems with FC's of a lot of apps.

This is not with all backups, but with 2 out of 10.

Is this problem familiar? Anybody a way to solve it? Of course I want to be sure that my backup is 100% successful and that I dont have problems with FC's after restoring.

Before restoring, I always do a full wipe of data/cache and dalvik.

Thanks for reply!

M.
[Galaxy Note 3 Q&A, Help & Troubleshooting] GuestK0079:
I don't know the answer, but i had my problems with cwm too. I now use twrp, no more issues.

Sent from my N9005
[Galaxy Note 3 Q&A, Help & Troubleshooting] Morrpheus:
Thanks, that solved my problem!
[Samsung Gear S] dawgboy1783:
Hey guys and gals I was dabbling around and got curious and used the S4 Dialer Codes from that forum and they also (most of them) work on the Gear S, so maybe we can also try and tweak these little device's from the service menus like our phones, see my screenie for proof, I used *#0011# and also tried *#197328640# and it works too, I don't know a whole lot about the functions within these menus and I know that if you mess around in there you can really screw up your device so TRY AT YOUR OWN RISK I AM NOT RESPONSIBLE IF YOU BRICK OR DAMAGE YOUR DEVICE!..I just wanted to point this out since I didn't see any threads or topic about this yet and maybe a DEV can jump in to provide some guidance as to the functions within these service menus.

S4 Dialer codes forum.

http://xdaforums.com/showthread.php?p=48222157
[Samsung Gear S] dawgboy1783:
Ok just browsing through the menus and if you select [4] Reserved just look what's in there! and although this is the only setting that would not enable does this mean it is possible to enable it via software? Could LTE be built in awaiting another software enabling update like other sammy devices? that would be pretty slick! an LTE Smart Watch!
[Samsung Gear S] wase4711:
doesnt the t mobile version already have LTE? Thats how they are advertising it..
[Samsung Gear S] foxbat121:
No, none of the Gear S has LTE. Don't confuse '(fake)4G' with LTE.
[Samsung Gear S] wase4711:
wow, shocked that a mobile company would engage in deceptive advertising! :cyclops::confused:

actually, its a non issue, considering how little actual data use most will be using with a smart watch at this point..
[Samsung Gear S] dawgboy1783:
From what I can see the only symbol that pops up on my t-mobile Gear S is 4G, but my question is why would LTE band selection be inactive within the service menus, none of the previous gear watches had LTE so why would it be in there? And its funny how selection 4 says reserved where the LTE selection is.
[Samsung Gear S] sbrownla:
The LTE is likely showing because it has a Qualcomm Snapdragon 400 chip in it. That chipset supports LTE as well as dual mode GSM/CDMA (e.g., the same watch would work on Verizon as well as AT&T), as well as quad-band GSM (850/900/1800/1900), but that doesn't mean the radios are actually in it.

That menu is very likely a holdover from the S400 operator menus in other devices. Manufacturers tend to be lazy when it comes to modding things like that.

Of course, until there is a teardown we don't really know what all is inside this watch. Also, the previous Gears didn't have the same service menus because they don't have chipsets that support independent cellular radios.
[Samsung Gear S] dawgboy1783:
I can agree with you and for sure a tear down would be a good source of information.
[Samsung Gear S] sbrownla:
I asked iFixIt and they say they are too busy ... which is shocking to me given what's inside of this watch ... Somehow the Kindle Voyage is more important to them ... HAH.

I don't know what the deal is but the media is REALLY resistant to the Gear S. And I don't like that at all. :mad:
[Samsung Gear S] joytest:
Surprisingly the user manual from the UK site HAS disassembly instructions in the last few pages.

Ostensibly this was for replacement of the battery......

Doesn't seem very difficult. Remove the screen, and everything else is right underneath.
[Samsung Gear S] sweets55:
Try it and let's us know. Hehe
[Samsung Galaxy Alpha] Redsandro:
I got this phone last week. It's beautiful and very fast. But as expected, the battery is terrible.

The normal energy saver doesn't do much for me. And the extreme energy saver is not something I'd like to use on a daily basis. What does the normal energy saver do?

Normal energy saving mode

Stop background data, unless connected to WIFI

Dim screen, unless brightness is set to manual

I even noticed that the S Health services (constantly checking for motion pedometer) is still on in power saving mode.

There are a lot of options on this phone that are convenient, but I'm not sure which ones are having a non-negligible impact on the battery. Maybe we can combine our knowledge and come up with a list. We can each personally choose which ones we can live without, and which ones we want/need. I'll start with the ones I am thinking of:

Possible energy consuming functions

Touch Sensitivity: For when wearing gloves. Is this just the way software interpretes data, or does this in fact require more power?

Air View[link]: Is this just the way software interpretes data, or does this in fact require more power?

Smart stay: Uses front camera, which requires power. Is the camera always on, or only in browser?

Smart pause: Uses front camera, which requires power. Is this always active? Every video? Only Samsung video player? Youtube?

Smart scroll [link]: Uses front camera, which requires power. Only in stock browser? Or all apps?

S Health: I personally like the pedometer. Makes me walk a bit extra. Those pedometers you get for free with your groceries work forever on a penlite battery. But the one on the phone, does it have dedicated hardware? Or does it prevent the phone from sleeping, monitoring gyro sensors permanently?

Multi-window: Probably uses multiple cores. Can you just keep this mode active even if you use a single screen? Or does this mode permanently require more power?

3G: Switching to 2G always requires less power. Is this setting gone in the ALPHA?

Quick setting switches (toggles)

Half those options have a quick setting on the backside of the notification screen. But the other half does not. Which is annoying. Do the "hidden" features not matter as much for power? Is there a way to add these "hidden" features to the quick setting screen?

Discuss. :)