yashsingh1/xdaforums huggingface dataset:
[Moto 360] xt_gonzalo:
Why is... *not saying* OK Google a solution to this tragedy XD

[Actual question]
[Moto 360] deadgiveaway:
Wish i could turn this off also .... Always does random searches while im talking
[Moto 360] thebobmannh:
The words "OK Google" come up in conversation that often?
[Moto 360] aperry:
No, probably not for most people. So I guess you bring up a good point. Since we don't say "ok google" very much and the watch thinks we do, this is proof that its voice detection reliability should be improved. This is one of the reasons why I turned off "tilt to wake".
[Moto 360] deadgiveaway:
Not even lol , thats the problem ...way to sensitive ...opens when i say anything ...or from tv shows .....

Ive never even said okay google ...

I prefer okay noodle
[Moto 360] Errant33:
This watch CAN make it through a full day with the screen on no problem. Im running ambient mode.

Ways voice activation activates:

- touch the watch face(Happens more then you think when your not trying to)

- Ok Google hot word

- Any slight alteration such as OK lets go(my bane word)

I don't even want the app launcher that comes with it. LOVE android watches HATE voice control always have. I am always listening to music/podcast and it just messes with that. I put in replacements for touch actions for everything so that is never more then 1 swipe and a key press away. My watch face i designed has hot spot key presses on it to go where I want with out ever swiping off the home-screen. I am not rooted yet since I didn't want to void warranty but I really hate this mic so I may have to.

To those triggering mic to much my solution to limit it was a invisible image 3 layer deep over the whole watch face. it takes 2-3 repeated taps on my watch face to cause the voice control to activate stops a lot of my accidental taps. I believe it isn't OK Google sensitivity that is the problem its that any time you touch the watch face while its on it doesn't mater if you said OK Google.

I use Watchmaker to make my faces, Id be more then willing to share the current watch later when I get home from work, let me know if anyone is interested.
[Moto 360] Errant33:
Any update on a method to mute/disable mic or just OK google? I am still fishing around for a way to do this with out rooting if possible.

Mute wear mic on the play store sort of half does this currently in 5.1.1 it still responds to Ok Google but after that it will not pick up anything.

Thanks,

Things i currently have had to limit the always listening capabilities.

- My phone

- My watch

- My gaming consoles

- My TV

- My computers

Am I the only one who really doesn't like voice control, and especially "always listening" devices?

Honest off topic question:

Why is everyone so ok with letting these devices literally pick up everything and send it to some unknown server to verify the recording doesn't contain "the keyword to trigger"?

My mindset is if they can search for a keyword they can search for anything and they have everything. From the joke you said that sounds so wrong out of context to anything else this is stuff that could ruin anyone's life with PC Police and media the way it is today!
[Moto 360] oposiasty:
Maybe freezing specific app via titanium backup could help.
[Moto 360] sambartle:
You could fill the mic hole with epoxy or some kind of glue perhaps?

potentially a permanent solution.. but it'd probably work.
[Moto 360] Errant33:
I am still under warranty so I am trying to limit it to software changes that can be reversed easily or wont flag a void of warranty.

I was thinking epoxy route or similar. What I would really like to do once my warranty is a combo of that and a mute/disable via hardware to assure.
[Moto 360] sambartle:
You could probably gently drip nail varnish across the mic hole.. with a hole that small, surface tension will normally make it seal the hole without running into it, and therefore not stick to the mic as it doesn't get that far in.. you'd almost certainly be able to pick it out/off with a toothpick/pin if you ever needed too.

Probably not as good as the epoxy at stopping the mic working, but its likely to mute it enough that it wont pick up any words and therefore not invoke OK google.

Cant see how they would ever know if you picked it off if you ever needed to return it.
[Moto 360] thebobmannh:
Mostly because that's not the way they work. If always-listening devices were sending all sounds to some external server you'd have a constant stream of audio being sent out, and that's juts not the case. Keyword verification is done on-device, while other voice stuff is done externally (typically) after the keyword is triggered.
[Moto 360] Errant33:
I am aware how they are supposed to work, as a software developer that doesn't mean they WILL work that way. Its been proven that this data does end up getting transferred to servers at times(See Samsung smart TV issue a few months back), and that at any point a proper update can enable it so all of it gets sent up or similar.

I just don't like having ANY mics/camera enabled unless they are needed. Even my phone mic is muted unless it needs to be on.

I am that guy that since 15yrs old I have had all my ID cards and CC in what amounts to a faraday case to give you a idea. Nothing to hide I just like my rights!
[Moto 360] thebobmannh:
I always think it's funny when people in the technology field are afraid of technology. I worked with a guy who was absolutely insane about privacy rights and people spying on him, and yet one of our customers was legit the NSA.

I mean, I get being a paranoid dude, but taunting fate by buying a device whose main focus is voice-based communication doesn't make me think you take it as seriously as you want people to believe.
[Moto 360] Errant33:
Locks are for honest people, and any barrier has a way for it to be removed. I do not actively block my behavior online its very easy to see what and who I am if you even give minimal effort. Security and being smart are not synonymous. I just don't want to be part of the funnel of data if they want to monitor me directly there is literally NO blockades. Honestly most of the stuff I am looking to limit there are already many other ways to obtain the same data.

I am sure you can understand that mentality of thinking.
[Moto 360] zerosum0:
If you say ok Google and swype it off the screen when it comes up as d do it five times in a row that should stop it for a while

---------- Post added at 07:58 PM ---------- Previous post was at 07:54 PM ----------

Poke a pin in it
[General Topics] hitmanid:
I am using Samsung Grand quattro and when ever i use it in my car(Hyundai Xcent) to play songs via Bluetooth songs wont play smoothly, songs play but suddenly they stop for few seconds and play again and this repeat for all songs but no problems when attending calls through Bluetooth. Any when i play over usb or Bluetooth of windows phone of my brother in my car music player it plays just fine . What could be the problem. How can i fix this???
[Nexus 5 Q&A, Help & Troubleshooting] pibetuerca:
Ever since installing Lollipop my phone hasn't been the same. I've used cyanogen, slimkat, etc and they all start to present problems within a week from installation.

And forget about lollipop 5 or 5.0.1 , it begins to crash from the first moment.

Is there a way to do a hard erase and manually install things? *when I install things android images, I use ADB and the flash-all command.
[Nexus 5 Q&A, Help & Troubleshooting] dicecuber:
Revert back to kitkat for now until the bugs are fixed?
[Nexus 5 Q&A, Help & Troubleshooting] pibetuerca:
It does not work. All kit kat images start to "degenerate" after a week from installation. It's really strange.
[Nexus 5 Q&A, Help & Troubleshooting] :
Then it must have to do something with your configuration (maybe an app that goes rogue or something). Don't forget that factory images completely restore your device and that this state has been well tested for several weeks / months :)
[Nexus 5 Q&A, Help & Troubleshooting] chrisgtl:
Just experienced a similar problem.

My Nexus 5 32GB was clean flashed with various ROM's and every now and again the phone would just freeze, maybe for 2-3 seconds at a time and then all of a sudden catch up with itself and carry on working fine until the next freeze. Usually the freezes would occur when using Chrome but it did freeze using other apps I had.

Anyhow, on Sunday night I went to bed as usual and put the Nexus 5 on charge (it had about 27% left) - woke up Monday morning to a dead Nexus 5.

Battery still gets warm to touch when charging it but the phone is dead. No red light, nothing. No charging screen animation.

Google are sending me another Nexus 5 out - which will probably go bad too as I tried to remove the battery cover after reading about unplugging the battery to kick the phone back to life. No doubt Google will now say I have no warranty as I've attempted to remove the back cover (unsuccessfully as it looked like it was going to snap the tabs off) - however the phone now has marks around the cover where I tried to open it up.

Oh the fun!

My previous phone, the Nexus 5 16GB died a couple times with the red flashing LED problem, but I managed to get it working twice by unplugging the battery. My newer Nexus 5 32GB is only 3 months old and it is dead.

If my refurb Nexus 5 dies I am moving away from the Nexus line as my faith in this brand is depleting very quickly.

The only Nexus I've not had any problems with was the Nexus S. My Nexus 4 earpiece was very distorted and crackly, plus the screen always looked yellow.

Really bugs me to say it too - as the Nexus is a perfect solution to the pure experience enthusiast. But from my recent experience with a dead Nexus 5 for no reason my overall experience of the whole experience is an experience and half.
[Nexus 5 Q&A, Help & Troubleshooting] CalculatedRisk:
Sounds like it might be a hardware memory chip issue. Starts off good and slowly deteriorates into a bootloop.
[Nexus 5 Q&A, Help & Troubleshooting] pibetuerca:
That would suck but yes I suspect my problem is hardware related.

Every thing worked great before lollipop though.
[Nexus 5 Q&A, Help & Troubleshooting] JOEzone:
Try safe mode, also go stock whatever and a different kernel. I've been lucky with mine but noticing battery drain with lollipop.
[One (M8) Q&A, Help & Troubleshooting] HeadKandy:
Hello all,

I'm having a bit of a time rectifying this problem, and my usual Google/XDA searches haven't unfortunately bore any fruit.

The problem in a nutshell:

I unlocked my phone via HTC Dev, it was S-Off, and bootloader was unlocked.

I was using Viper Rom, last one before their 4.0/4.1 Lollipop release - no prroblems.

I was using an older 3.X firmware (I forget which - probably inconsequential in any case).

I wiped my phone in preparation for installing the 4.1 Rom with TWRP.

I installed the new Rom via TWRP, I wiped again with the Rom's wiper.

I rebooted my phone after a successful wipe.

I booted into the rom, but a whole bunch of processes failed (com.android ones), however I was able to, at this point, get into my wifi and set up my accounts etc.

After this, I had a black screen, though my notification bar etc. were there.

I thought it might be a firmware issue, and so I used fastboot RUU to install the firmware version 4.16.401.10. Everything was fine, and it has flashed successfully.

Unfortunately, the bootloader is now once again locked (relocked, to be exact), and I can't boot back into the Rom OS to run adb commands to unlock it once again.

Fastboot commands such as flash unlocktoken are met with fails.

I have no idea how to proceed from this point forwards.

So, I'd appreciate any and all help at this point to get me back up and running again! Maybe I'll learn something along the way too :D

Thanks in advance!

edit: Ah yes, here is my getvar information:

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 1.25.214500021.06G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.16.401.10

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: *************

(bootloader) imei: *************

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B10000

(bootloader) cidnum: HTC__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 3aa067db

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
Can you post the error you get when trying to unlock the phone?

You don't actually need to be unlocked to flash a custom recovery, you just flash a ZIP via RUU mode (it's what I do on the rare occasion I want to root my phone to try something)
[One (M8) Q&A, Help & Troubleshooting] HeadKandy:
Sure, which error are you talking about?

When trying to use my unlock token, I get the following:

I thought there was a fastboot oem unlock, but as it turns out, there isn't.

When trying to flash TWRP 2.8.5.0 (mine is an international UK/EU version, not sprint or verizon or tmobile, carrier SIM unlocked) - I get:

Do you require any additional information?

Thank you for the quick response to my plight!

Edit: Oh, do I have to be in RUU mode to install TWRP? If so, that might be my noobish mistake!

Edit2: nope, RUU mode won't let me do it either :(
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
For example, you could flash this ZIP file in RUU mode for the latest TWRP and keep the bootloader locked:

https://www.hightail.com/download/UlRTcXlpOC9iV3hMWE1UQw

You shouldn't have to be in RUU mode, I just made this ZIP to flash TWRP with a locked bootloader
[One (M8) Q&A, Help & Troubleshooting] HeadKandy:
Thank you for this, however I'm getting the same error.

Am I doing this correctly?

(Using Ubuntu)

Terminal command: sudo fastboot oem rebootRUU

Wait for silver HTC logo on phone screen.

(After unzipping the recovery.img file) sudo fastboot flash recovery recovery.img

Same error as above -
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
fastboot flash recovery recovery.img <--- wrong

fastboot flash zip recoveryRUU.zip <--- this one
[One (M8) Q&A, Help & Troubleshooting] HeadKandy:
I love you man! Thank you so much!

Worked, TWRP reinstalled, happy days!

For my own knowledge, why did using 'flash recovery' not work? And why did using RUU and flashing the zip work?

Thank you :)
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
Because you can't flash partitions in RUU mode, only ZIP files

Individual partitions are flashed in fastboot but you need the bootloader unlocked to do that
[One (M8) Q&A, Help & Troubleshooting] HeadKandy:
Nicely put, thank you. I'll remember all this for future.

Thanks again both!
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
What you can do now, though, is lock/unlock the bootloader from TWRP...

1. Boot into TWRP

2. Connect phone to your PC (make sure drivers are installed and that your device is recognised when you type adb devices)

3. Get into the shell by typing adb shell

4. Type the following command to unlock the bootloader (probably best to copy/paste this):

echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796

5. Exit shell by typing exit

6. Reboot phone to the bootloader and check you're now 'unlocked'

Parts taken from this thread by [MENTION=3437245]scotty1223[/MENTION] - http://xdaforums.com/showthread.php?t=2708571
[One (M8) Q&A, Help & Troubleshooting] HeadKandy:
Hey, thank you! Sorry, I didn't look back on my topic once I'd managed to solve it. Cheers for the instructions!
[One (M8) Q&A, Help & Troubleshooting] syntropic:
This is new information for me... And I'm stuck too wanting to root..but don't want to use the htcdev token and want to install TWRP.

Q#1: Do I put the recoveryRUU.zip in the platform-tools directory?

Q#2: What is RUU mode? I've done plenty of things in fastboot (flashed recoveries before...I guess I didn't realize I was flashing a partition)... So the whole RUU thing is confusing me. Aren't you just rebooting into fastboot and flashing that zip?

I see the correct commands above, but I just want to confirm what I'm doing exactly.

Thank you very much in advance!
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
1. Yes

2. It's the mode used to flash the RUU - fastboot oem rebootRUU
[One (M8) Q&A, Help & Troubleshooting] syntropic:
Ok... I guess when I hear RUU I think of the .exe run in Windows to update or restore to factory. Didn't know there was a "mode".

But thanks! I'll put your zip in platform-tools, and then run the above commands.

How is the zip created? Is that something I can do fairly easily?
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
No. It's extracted from the EXE version of the RUU and in encrypted by HTC (unless you have the right tools to hack it)
[One (M8) Q&A, Help & Troubleshooting] syntropic:
What tools do I need? Like a disassembler or Ollydbg?

[deleted earlier self-solved error]

---------- Post added at 01:28 PM ---------- Previous post was at 01:02 PM ----------

This is quite frustrating.... I am not sure why I am finding so many obstacles to what looked like an effortless way to flash a custom recovery...

I ran the fastboot flash zip recoveryRUU.zip

and received the following response from adb.

target reported max download size of 1826418688 bytes

sending 'zip' (12223 KB)...

OKAY [ 1.440s]

writing 'zip'...

(bootloader) zip header checking...

(bootloader) zip info parsing...

(bootloader) checking model ID...

FAILED (remote: 41 model id check fail)

finished. total time: 3.869s

Any idea what "41 model id check fail" could mean?? It doesn't sound good.

I researched this and it looks like it has something to do with the a version mismatch or something. Not sure.

I ran getvar:

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.19.0.0000

(bootloader) version-baseband: 1.23.213311491.05G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.20.531.4

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: FA44VWM00543

(bootloader) imei: ********

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B13000

(bootloader) cidnum: T-MOB010

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 06f11f5b

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

and noticed that my bootloader and HeadKandy's bootloader are different... could that be the problem?

Above you said you created the recoveryRUU.zip from an HTC RUU. So could the variant of the RUU you used to create that zip be the issue??

I appreciate any help as I would love to root this without having to use HTCDEV token to unlock the bootloader.

This is a very interesting and cool way to get around having to unlock the boot loader with a HTC token, but flashing a zip containing the custom recovery requires that I create that zip...which I have no idea how to do.

Is there any source for any custom recovery that's in a flashable zip format already?? If so, I could use that, then root it/unlock bootloader and then install TWRP.
[One (M8) Q&A, Help & Troubleshooting] EddyOS:
Sorry, I thought you were the OP! That RUU won't work at all as you have to be on x.xx.401.x to flash it (it's the EU RUU, yours looks like T-Mobile)
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
I don't find this surprising at all. You are trying to flash a custom recovery with a locked bootloader. And one of the whole points (arguably

the

main point) of the locked bootloader is to

prevent

installing custom recovery.

A locked bootloader means you can only flash something that is properly signed, meaning it also has to pass the CID, MID checks. Since the zip you are trying to flash is not for your CID, you will get a fail.
[One (M8) Q&A, Help & Troubleshooting] brush2:
Unlocking bootloader a second time did it!

Hi there,

yesterday a friend of mine came around and told me he tried to update from AHRD 3.28.401.9 to 4.16.401.10.

He told me he followed the guides but he end up in a working ARHD Lollipop - but without the ability

to flash anything via fastboot ('ERROR' remote:not allowed) while having bootloader 'RELOCKED'.

He also tried to update to the lastest firmware - FUU as well - but without success.

I tried alot to fix it - but also without success.

The last option and idea I had was to unlock the bootloader at HTCDEVs a second time.

I did it like described in the public tuts around here at XDA.

AND IT WORKED !

This might not work in every case - but it is an option since your bootloader is already unlocked and because this might be you last option :p

As usual -> I am not responsible for bricked devices ... etc, if you try this!

Regards,

brush2

Here is the final result of fastboot getvar all (bootloader is now 'UNLOCKED'):

version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.214500021.06G
version-cpld: None
version-microp: None
version-main: 4.16.401.10
version-misc: PVT SHIP S-OFF
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: HTC__001 (HTC_102 originally)
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
[General Questions and Answers] belamenge:
Hi, I was having huwaei honor 4 play g620s uloo and rooted it before a week.But yesterday after I restarted it, it stopped switching on , there is no response in power button. I bought it month ago and I loved it so anyone who can plzz help me what to do??

It detects the phone on pc but nothing on the phone
[Galaxy S 5 Q&A, Help & Troubleshooting] TheRebel:
Greetings everyone,

I m planning to buy a new phone. Can anyone please tell me which phone i shohld go for, note 3 or galaxy s5, and if possible, reason also, why should i go for some specific phone?

And one more thing, since many here would b already using galaxy s5, so please confirm me, is 2GB ram okay for multi tasking in S5 or is it less? One good thing that i find about note 3 is 3GB ram, tho its a very big phone in size.

But anyway please guide me, i m confused.

Thanks
[Galaxy S 5 Q&A, Help & Troubleshooting] Swimguy14:
Check out this wealth of info on precisely your exact dilemma: http://lmgtfy.com/?q=Galaxy+s5+vs+note+3

sent from my lollipop'd S5
[Galaxy S 5 Q&A, Help & Troubleshooting] rrgrrg:
my mom has a note 3 and i have a s5 duos

... tell you mate my battery is much much much better on s5 it lasts about 5 hours on screen time in 24 hours gaming music wifi all sort of this

while she gets 24% at the end of the day while she uses wifi only and calls

reasons for s5 :

-waterproof (for me its good so i can walk in rain so fine :cool: )

-size is handy u can use one hand for full use

-camera is better on s5

-screen resolution is better (not that better)

reasons for note 3 :

-bigger screen

-more internal storage 32 gigs instead of 16
[Galaxy S 5 Q&A, Help & Troubleshooting] TheRebel:
Thank you my friend for ur reply. And i have noted ur points, but one important thing is RAM of both devices. Note 3 has 3gb and S5 has 2gb. Does this 1gb less in S5 cause any issue with multi taksing? I like specs of both phones, the only thing i dislike about s5 is less ram, and the only thing i dislike about note 3 is its big size.