yashsingh1/xdaforums huggingface dataset:
[Nexus 6  General] clninja:
Have fun with choppy lag anywhere below 30% battery, poor battery life, inconsistent performance, inconsistent battery life, proximity sensor that only works half the time, crackling speakers, halo effect on screen protectors, horrible discoloration at low brightness screen setting. Poor low light pictures,

These are things that don't show up on spec analysis or sheets somewhere

Yall rely too heavily on benchmarks and numbers in a sheet. Gotta look at real world use and results and optimisation of hardware+software. The reason an iPhone runs so fluid on lower specs is because of that optimisation

I love my Nexus 6. These are all things I've learned to live with. But in hoping for better results from the new Nexus.
[Nexus 6  General] istperson:
I don't know what people are saying about battery life, but I could go two days on 5.1.1 and I'm on my fourth day with only a 15% charging yesterday morning on my M preview. It's not a lot of SOT, only while I check my mail (company and private), read/send texts, and check the Wikipedia, or a site here and there. It's better than my Note 3 was with Play Services unable to wake up the phone or keep it awake.
[Nexus 6  General] Smallsmx3:
Still not a deal breaker, if the phone didn't have a battery and always needed to be plugged in or something along those lines then it would be
[Nexus 6  General] clninja:
You admit that you rarely use your phone. I don't see how that is an accurate representation of battery life for an average user or a heavy user.

The average user will

Check/send email

Check/send texts

Phone calls

Browse web

Use navigation

Play a game here and there

Stream music

Take pictures

Use a Bluetooth device of some sort

That's just the average user.. Heavy users will do all of that.. They will do it more frequently and they will do alot more on top of it.

BTW of your the kind of person who turns off your location and Bluetooth and syncing and data and whatever else to conserve battery life than don't even bother commenting. Nobody should have to turn their smartphone into a flipphone to conserve battery. If you do, that's an issue with the phone
[Nexus 6  General] droidstyle:
I have no lag below 30%, battery life is fine(5-6hrs sot with WiFi, Data, Bluetooth, and GPS on), do not notice any halo effect with my revision 2 Jelly Comb screen protector, camera is fine for what I need, I do notice some crackling in speakers on phone calls, I have not noticed any issue with the proximity sensor. Maybe you have a Lemon?
[Nexus 6  General] istperson:
BTW I'm not. I have both wifi and data on except for nights when I use my phone for alarm clock. And I'm sure I said I use it for mail and texts, also for Tapatalk and Skype, and take occasional photos. Yeah and I usually play a game here or there, but that doesn't count, because there's no phone that can run Tomb Raider Go for a day. So yes if I play games then I plug it in after to charge it.

OTOH I only use GPS when I use it for navigation, because Battery Saving location mode is accurate enough to 10 meters.

What I'm not using is Google Now cards
[Nexus 6  General] Onknight:
JUst getting here Retiring Nexus 4 shorty for the Nexus 6

Reason I got a Nexus 6 was I don't have USB C on any computer in my Home.

Plus 3 Gigs of Ram is better then Two if 5X I was looking into Buying .

Wireless charging

2 maybe 3 more years of Updates on The nexus 6 .

It was better choise for me
[Nexus 6  General] xTmDarren:
I've had my nexus 6 since launch and the only problem I ever had was the Sprint LTE/3g problem ( which seem to of fixed itself after i went to project fi and back to sprint ), and the battery barely lasting a day. But after I installed 6.0 that was fixed and now I can go a full day with heavy usage, two days easy with average usage.. All the other problems you listed I haven't had.

Either way.. I wouldn't expect the 5X/6P to be worth upgrading from a nexus 6. Unless you just have to have the better camera..

I personally can't wait til project ara comes out..:cool:
[Nexus 6  General] sage_viper:
Granted, the 6p looks less horrible in someone's hand compared to the renders and leaks we had before, I still think I'll keep the N6. I think someone would be wise to upgrade to either from a N5 if they're ready for a new phone, but 808/810 over the 805 isn't that big of a leap.

The only thing I wish I had going forward is the fingerprint reader; but I can wait another year with the N6 without it.
[Nexus 6  General] Bl4ckX:
In my opinion the both of the new Nexus phones aren't worth the upgrade when coming from the N6. The only benefits of the N6P is the most likely better camera and the newer processor. The 100mAh boost in battery capacity is probably not going to make a huge difference and if the smaller screen is better or worse is just a thing of personal preferences.

And from the outside... Full metal is nice but I'm no fan of the black camera bar of the 6P
[Nexus 6  General] Master05:
I will keep my N6 now that we know everything about the latest devices. I was planning to switch because the N6 still feels too big even though I can handle it without a problem but it's just not confy at some occasion.

That being said, a switch to the Nexus 6P was out of the question as it's a downgrade for the price premium you have to pay. The screen is only a bit smaller, you lose wireless charging, get a weird design and the infamous SD810 rev 2.1. Then again you would gain a fingerprint sensor, a better AMOLED display and some smaller features. But that is not worth the money as I previously said.

The 5X on the other side looks appealing from the due to it's 5,2'' screen but their choice on going with a mere 2GB of RAM is a bummer. The SD808 should only be a rather small update to the 805 and the rest of the specs look mediocre but make sense when you take the price into consideration. At least the U.S. price. Since I'm from Europe I get majorly screwed and ripped of when it comes to pricing which is why the 5X is off the table too. I won't pay 500€ for a device that overall doesn't beat my one year old N6 in many aspects. No matter the better cam, fingerprint sensor and so on...

On top of that you gotta consider that I once bought my N6 for 650€ and now you can get it for like 400,- which means selling it right now would give me 50% of my investment back, tops.

So see you next year, Google.

(Btw same goes for my N9 which I won't replace by another android tablet like the pixel or something else. Read the article on the Pixel C on AP. I share the authors opinion and will stay with my N9 for now and think twice about buying another android (premium) tablet in the future. Will depend highly on how Android OS will evolve or not evolve for tablets.
[Nexus 6  General] clninja:
Qualcomm 805

32 bit quad core

Qualcomm 808

64 bit hex core

Pretty big difference if you ask me
[Nexus 6  General] istperson:
In what way they differ that actually matters?
[Nexus 6  General] Smallsmx3:
By offloading all the sensor processes to the new sensor core wouldn't that alleviate stress on the main cpu and prevent some of the issues that the 810 has? I'm guessing that and hopefully whatever heat sink they used for the 6p alleviates any issues
[Nexus 6  General] TiltedAz:
Absolutely. You're destined for that Chinese made product.
[Nexus 6  General] md1008:
I have been a loyal Nexus user for a long while. Had Nexus S, GNex, Nexus 5 and Nexus 6. I just never felt it was that big of a deal, but some people obviously did. All I was saying is that I was surprised. I would rather have a premium all metal build but that is just me. So if wireless charging is a must would you abandon Nexus 6 after it gets outdated and or unsupported and move to a different OEM?
[Nexus 6  General] istperson:
Korean. The LG is Korean. The Chinese is 64 bit octa-core which is even huge- ... -er difference.
[Nexus 6  General] md1008:
I would rather stay wired and be able to use my phone, make calls and even play games while charging. With wireless charging you are still using a wire and are still ironically tethered to the bloody charging pad. I would much rather have an all aluminum body plus USB Type C.

At least the Nexus 6 is a very capable device and will be for some time
[Nexus 6  General] Semseddin:
2.7 ghz all equal quadcores , Up to 55mp camera support, LPDDR3 800MHz Dual-channel 64-bit (25.6GBps), Adreno 420 gpu, Hollywood Quality Video™ technology (in HW) for post-processing.

2 ghz dualcore and 4 weaker A53 quadcores in total 6 cores hybrid package, Up to 21mp camera support, LPDDR3 933MHz Dual-channel 32-bit (12.8GBps), Adreno 418 gpu, No Hollywood nor Bollywood Quality Video™ technology (in HW) for post-processing.

Qualcomm itself couldn't position 808 over 805 but you did it. Congratulations.

https://www.qualcomm.com/products/snapdragon/processors/805

https://www.qualcomm.com/products/snapdragon/processors/808

Pretty big difference if you ask me.
[Nexus 6  General] clninja:
The only thing I see that's better about the 805 is camera support.. Which is good since the Nexus has 55mp

I'll take the better connectivity from the dual band WiFi support and better lte support rather than some Hollywood post processing for video
[Google Chromecast] badm0j0:
volume control via ssh

is it possible to control the volume of the chromecast via ssh? because my sound system is a classic stereo which doesnt have a remote, i am looking into using IR-Toy on my computer to receive IR signals from a standard remote, and in turn send ssh commands to chromecast. the reason i need this is because controlling the volume via the app which is doing the casting is cumbersome. also if there is a ssh command to play/pause i could implement that as well.
[Moto G 2015 Q&A, Help & Troubleshooting] mow4cash:
I'm having issues with the dialer using google voice to make calls. Can you guys let me know if you have this setup and working fine. I'm trying to isolate the problem. Thanks.
[Moto G 2015 Q&A, Help & Troubleshooting] hp420:
You have to use the hangouts dialer for Google voice, not the stock dialer.
[Moto G 2015 Q&A, Help & Troubleshooting] mow4cash:
On my Nexus 5 I use the google voice app and select in the settings make all calls with google voice. When I make a call using the stock dialer it says it's making the call using my google voice number. This uses my cell minutes but the people I call see my google voice number. On the Moto G this only seems to work intermittently. Is this a limitation on the Moto G and I will have to route all calls through data instead of cellular? I usually only use the hangouts dialer on wifi.
[Moto G 2015 Q&A, Help & Troubleshooting] hp420:
google voice hasn't worked like that since like may....try updating your apps. you need hangouts and the hangouts dialer. google voice is a dead app now.
[HTC Vox] shamual:
Hi..

I bought an unlock HTC S710..

it works fine.. kinda sluggish..

but lately I'm having a problem..

when ever i try to restart it...

it doesnt boot...

it shows.. HTC logo..

then Microsoft Mobile Logo..

then buzzes...

and thats it.. its an infinite loop..

it keeps buzzing... and showing these two logo...

but.. when i'm inside the subway train.. it comes to life...

Now i dont get the connection..

is it something to do with searching network or anything?

anyways...

any help or suggestion for this problem is welcome..

thanks a lot...!
[HTC Vox] jockyw2001:
Pull out the sd card and push it back in when it has booted in WM.
[HTC Vox] rodete:
recently i'm having same problem also. Next time i'll try taking out the

memory card....
[HTC Vox] shamual:
yes...

it is the perfect solution..

pulling out the memory card works like magic...

then i tried to chk the memory card...

there wasn't anything wrong with it..

i guess its just a bug with WM6...

but thanks a lot mate...

really appreciate it..
[HTC Vox] kast:
Sometimes applications meant to autostart can cause probs.

If these applications are stored on the memory card, removing it when booting solves the problem.

Ka.
[One (M7) Q&A, Help & Troubleshooting] Aisu64:
So aftter downloading the Android Revolution and wiping the data, I tried installing the ROM.

However it keeps booting into recovery mode. I have no idea how to fix this.

The phone tries to boot up normally, but fails to do so. It restarts and boots into recovery. (TWRP 2.5.0.0)

I have tried deleting installing a few times. Where I cleared both the cache and dalvik cache.

Still nothing. Is there any way to get another ROM onto my phone now? My computer doesn't recognize the device anymore.

After the installation it says complete, but shows an error: "set_metadata_recursive: some changes failed"

after this it says: "installation was succesful!" and tells me to do 1 full system boot before flashing mods.:crying::crying:

"Update, I found out I used a rom designed for M8 and not M7.

If anyone could help me getting ADB to work and a rom I can flash and pretty much a tutorial. I would be super grateful
[One (M7) Q&A, Help & Troubleshooting] Aisu64:
So I found a m7 rom. But when trying to push it using ADB it takes a really long time and ends in protocol error.
[One (M7) Q&A, Help & Troubleshooting] alray:
Here is one problem. You won't be able to flash any recent roms using twrp 2.5.0.0. Update your recovery first: https://dl.twrp.me/m7/

fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader

make sure you have the latest adb version (1.0.32) using the command:

adb version

If not update your android sdk-tools: https://developer.android.com/sdk/index.html#Other

Also make sure you have the latest htc drivers installed on your computer

With the latest twrp and drivers you'll be able to transfer a rom to your phone using MTP protocol when booted in twrp main menu (simply drag and drop your file from your computer to your phone storage).

If using newer roms (android 5.0.2) your phone must have a 7.xx.xxx.x firmware installed on it. Older firmware running new roms cam have issues. To determine your firmware version, use the command "fastboot getvar version-main" or "fastboot getvar all"
[One (M7) Q&A, Help & Troubleshooting] Aisu64:
Finally pushed the files to the phone.

But after installing my phone still keeps entering recovery mode (twrp).
[One (M7) Q&A, Help & Troubleshooting] alray:
Did you updated your twrp recovery?
[One (M7) Q&A, Help & Troubleshooting] alray:
afaik, not with 2.5.0.0. If you can't see the device when in bootloader / fastboot usb mode then you have drivers issues. make sur eyou have latest htc drivers installed. If needed download htc sync. This will install htc sync and the latest drivers. Then uninstall htc sync (but don't uninstall the drivers). You don't want HTC sync on your computer because it will interfere with fastboot / adb connectivity.
[One (M7) Q&A, Help & Troubleshooting] alray:
No problem, go take some rest and I'll help you later :good:
[One (M7) Q&A, Help & Troubleshooting] Aisu64:
So I've been playing around installing and reinstalling and deleting and restarting my computer.

My computer can see the device only in recovery. Everytime I'm in the bootloader/fastboot menu it dissapears from the device list in ADB.

Is it possible to flash the phone while in recovery?
[One (M7) Q&A, Help & Troubleshooting] alray:
you won't get any adb connectivity when booted in bootloader / fastboot usb mode. ADB only works from a booted rom with usb debug turned on or from a custom recovery. In bootloader you must use fastboot commands. To see if your phone is detected by your computer when in bootlaoder / fastboot usb mode, use the command "fastboot devices"

If your phone isn't listed with this command, please post a screenshot of your Windows devices manager with the phone connected and booted in bootloader / fastboot usb mode. Also need to know what is your bootloader version? 1.44/1.54/1.55/1.56/1.57 or 1.61 ? You can see this info when booted in bootloader mode

You might want to read what I said again:

You won't be able to flash any recent rom using twrp 2.5.0.0

You can't flash a new recovery using twrp 2.5.0.0, you must use fastboot

:good:
[One (M7) Q&A, Help & Troubleshooting] Aisu64:
[IMG="Fastboot"]http://imgur.com/So88OLm[/IMG]

It says Hboot - 1.44

atm I can't even get it to show up in recovery.

Screenshot: http://imgur.com/So88OLm
[One (M7) Q&A, Help & Troubleshooting] alray:
ok hboot 1.44 is the oldest one and have compatibility issues with windows 8 and 10. Do you have access to a windows 7 computer?
[One (M7) Q&A, Help & Troubleshooting] Aisu64:
Yes I do. A super ancient one.

Also this is how it looks like when I'm in recovery: http://imgur.com/SxW9p66
[One (M7) Q&A, Help & Troubleshooting] alray:
Please setup everything on this computer (HTC drivers + Android sdk tools (adb and fastboot), this will be much easier to work with Win7 because of your 1.44 hboot. Later, once your hboot will be updated, you'll be able to use your Win10 computer without any problem but for now better to work with Win7. Once you got everything installed on your win7 computer, boot the phone in bootloader / fastboot usb mode and use the command "fastboot devices" to see if your phone is detected. If yes then use "fastboot getvar all" command. take a screenshot of this command output and post it here (censor the IMEI number and the SERIALNO number before uploading your picture). Don't update the recovery for now.

Everything is fine here.
[One (M7) Q&A, Help & Troubleshooting] Aisu64:
You might aswell type the next part. Cuz this will be taking a few hours ^^
[One (M7) Q&A, Help & Troubleshooting] alray:
well I need to see your "fastboot getvar all" before i can tell anything more.
[One (M7) Q&A, Help & Troubleshooting] Aisu64:
My windows 7 computer keeps asking for a "android 1.0" driver, even though I installed the HTC one m7 driver package downloaded from HTC. I also tried installing HTC Sync, but it doesn't seem to help. Also it only shows "Android 1.0" while in fastboot so I assume this is the fastboot driver?

one more thing. I can't get it to show it's connected to ADB while in recovery.
[One (M7) Q&A, Help & Troubleshooting] alray:
Strange, it should be easy to make it work on win7. You might want to try this drivers: http://xdaforums.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339
[One (M7) Q&A, Help & Troubleshooting] Aisu64:
I borrowed a friends win7 computer and fastboot works! After installing the drivers you linked me to. Here is a screenshot! http://imgur.com/CN0uLu6
[One (M7) Q&A, Help & Troubleshooting] alray:
:good:

The firmware installed on the phone is very old, one of the first version (1.29.401.16). Recent roms like ARHD 92 and all other recent rom based on Sense UI requires one of the latest 7.xx.xxx.x firmware version to work correctly which mean you'll have to update your firmware first. At this point, you can either leave the firmware like that, update your twrp recovery only and flash a very old rom (Jelly bean, maybe kitkat could work) or you can update your firmware and flash the latest RUU for your phone which will update it to the latest stock version or finally you can update the firmware + recovery so you can flash ARHD 92. Its up to you I can help you whatever you choose.
[One (M7) Q&A, Help & Troubleshooting] Aisu64:
Let's try and update the firmware and recovery, so I can use the latest versions :)
[One (M7) Q&A, Help & Troubleshooting] alray:
Ok so first to flash the firmware, you need to relock the bootloader:

fastboot oem lock

Then reboot in bootloader and make sure the bootloader says ***relocked***

then to update the firmware, download and save this file in the same folder where you have adb and fastboot on your computer.

With the phone in bootloader / fastboot usb mode type these commands:

fastboot oem rebootRUU

The phone will reboo tin RUU mode, you should a see a black screen with a silver HTC logo (don't forget RUU in capital letters, fastboot commands are case sensitive). Then flash the firmware:

fastboot flash zip M7_UL_Firmware_7.19.401.2.zip

The first flash is only a pre-update, you'll get an error message in the command prompt saying something like "pre-update, flush image again immediately" so proceed with the same command again:

fastboot flash zip M7_UL_Firmware_7.19.401.2.zip

Second flash should be ok (confirm with the output of the terminal), if you get a fail again, do not reboot the phone and post back in this thread, if ok proceed with the next command:

fastboot reboot-bootloader

Then you'll have to unlock the bootloader again so you can flash twrp. To unlock the bootloader, folow instructions at htcdev.com/bootloader (submitting your token and then flashing the Unlock_code.bin)

Once your bootloader is unlocked, you can flash twrp recovery:

fastboot flash recovery twrp-2.8.7.0-m7.img
fastboot erase cache
fastboot reboot-bootloader

And finally you can boot in TWRP. Once in twrp main menu, you should be able to see your phone storage from your computer like if it was an external hard drive. Drag and drop your rom.zip to your phone storage and flash the rom using the "install" option of twrp.
[One (M7) Q&A, Help & Troubleshooting] Aisu64:
Everything went very smooth and fast. However I haven't downloaded a rom yet. I just wanted to ask if it matters which version I take? I'm aware it has to be a m7 rom and was thinking of getting android revolution 92. (Lollipop version): http://xdaforums.com/showthread.php?t=2183023 Will this Work?

The rom seems to be working. I have donated 20$ usd to you for helping me out. I really appreciate it, thanks!
[One (M7) Q&A, Help & Troubleshooting] alray:
Yes ARHD 92 will work fine or any other Sense based rom should work fine now that you are running a 7.x firmware. Other type of rom like AOSP / Cyanogenmod based should also work fine. And if you want to go back to stock rom later, you'll only have to flash the 7.19.401.2 ruu :good:

Wow thanks a lot :highfive:
[One (M7) Q&A, Help & Troubleshooting] Aisu64:
I have a last question though. If this should happen Again, would fastboot now Work wih Windows 10 or Windows 8?
[One (M7) Q&A, Help & Troubleshooting] alray:
Yes it should work fine now that your firmware is updated (your phone should now be running hboot 1.61). Plug it your win8/10 computer and restart it in bootloader / fastboot usb mode and use "fastboot devices" and you should see your device listed. :good:
[Moto X Q&A] jy1998:
My wife is quadriplegic due to MS. I bought her a Moto X from Verizon a couple of years ago, (I believe it is Gen 1), for the Voice Commands capability. We did not realize that while you can dial a call with voice commands, you CANNOT answer an incoming call. After some searching on the internet, someone else with similar disabilities suggested the "Answer the Call Free" app from Black Mountain. We installed and what a godsend. Very basic, it just answered any incoming call. Since the phone update last week, this app has not worked. Talked to Motorola, they tried this app and a few others, none worked. We could really use some help.
[Nexus 6P Q&A, Help & Troubleshooting] Powell730:
So I'm not the brightest with the different frequencies etc... What I do know is that Band 12 on T-Mobile has greater building penetration, and that it's currently not supported on the Nexus 6P, despite the phone having the band. My question is, what functionality do I lose? Aside from having more penetrating power, which gives me better signal, do I lose anything else? Honestly, I'm pretty sure Band 12 isn't even in Columbus, Ohio (where I am) yet... but I don't wanna buy this phone and then Band 12 go live here and then I lose LTE, if that's even what happens... or would it just resort to the current band 4?