yashsingh1/xdaforums huggingface dataset:
[Moto 360 2015] jarbi:
Hi,

Just for the record, I figured it out in the meantime. Apparently my watch "forgot" the Wifi password, so I dropped and reconnected to the Wifi router- now I have connection via Wifi !
[General Questions and Answers] jasonwood1985:
Please Help!.

I know the basics of tasker but this one i cant seem to figure out, i am trying to create a profile whereby when my bluetooth disconnects in my car (because i have parked up and turned of the ignition) and my home wifi is connected i want my Philips hue lights to come on to great me. I need both to work at same time as i then dont want my lights to come on for example when i get to work and turn the ignition off and therefore the Bluetooth disconnects.

I have it at the moment where they are both on the profile then as a exit rule it turns on the lights however this also seems to work if i exit the wifi as in when i get up the road the lights come on?

please can you help

thanks
[Nexus 6P Q&A, Help & Troubleshooting] TheReverend210:
Something I've just noticed, wondering if anyone else suffers from the same.

I have a loose-ish headphone jack, it makes a connection, but only on about the last 2mm of the connection, might be relevant.

Anyway, I've just noticed, the last 5 steps on the upper end of the volume control make no perceivable difference in actual volume.

I'm thinking its more of a software issue, but I was wondering if anyone else has thus issue?

Apologies for the disjointed nature of this post, but I'm rather drunk. I'll try and flesh it out if needs be.
[Nexus 6P Q&A, Help & Troubleshooting] RED ZMAN:
Nope, I've got the same issue all across with the volumes.
[iPAQ rw6828, XDA Atom General] tacobell:
Hi...

Ive had my xda atom for almost 8 months now, I have encountered two strange problems while using the phone,

Today I was not able to make any call, whenever I dialed a number it starts dialing and then says call ended 0:00. I did a soft reset but the result was the same. I am no using my old nokia phone because I dont want to miss any calls now.

The second problem happened once till now, I left my o2 beside me while I was surfing the net for about 45 min. bluetooth was on the whole time and it was paired to a bt headet.

When I finished surfing I checked the o2 and it was simply hanged. It worked after restarting, but the bad part was that people who called me or send sms while the phone was stalled were able to ring me normally and it seemed to them as if I did not answer them back, because i didnt receive any missed calls after the reset...

All help is appreciated...
[iPAQ rw6828, XDA Atom General] ckaidi:
Soft reset only reset the RAM and system loads. If you surf net offen with your Atom then you shld use either SKtool or Memmaid to clear your phone cache and history stuffs. As ATOM is already very low on resouces the net surfing will leave even more loads on the system causing it to lag and ATom is known to hang when memory run low. Do also try our dear Jiggs latest ATOM ROM which will stablise and speed up our ATOM!! :)

Cheer,

kaidi
[Nexus 6P Q&A, Help & Troubleshooting] abraxo:
Anyone else think this? Everyone sounds muffled
[Nexus 6P Q&A, Help & Troubleshooting] Codename13:
IIRC, this is a common issue with some Nexus devices. I saw somewhere that a 6P owner fixed the issue on their device by changing a line in the build.prop, as done here on the Nexus 5. Apparently you have to change the value of "persist.audio.influence.voicecall" from "true" to "false". Of course, you have to be rooted to modify the build.prop, and I think modifying the build.prop breaks OTA updates because of system block verifications.

Edit - apparently the muffled sound issue is a result of the noise cancellation microphone picking up your voice as background noise, meaning it attempts to reduce the volume of your voice. It's probably some sort of design flaw, but I don't think it's worth RMAing when it can be fixed with a simple software modification to the build.prop. Alternatively, you should be able to fix the issue by covering whichever microphone is the noise-cancelling microphone on the Nexus 6P (for the Nexus 5, I read that it was the top microphone)
[Nexus 6P Q&A, Help & Troubleshooting] abraxo:
Thanks, I'll definitely check those fixes out. I don't think losing ota updates are too big a deal since you can't use otas when you're rooted anyway
[Nexus 6P Q&A, Help & Troubleshooting] ohlin5:
Here you go: I'd go ahead and post here to add to the "pile" of people confirming this as a legitimate issue. Someone from Google confirmed earlier they were looking into it. https://productforums.google.com/forum/m/#!topic/nexus/g70qCHkqLA4

(Also, the desktop view looks WAY better)
[Nexus 6P Q&A, Help & Troubleshooting] anglerstock:
Yes it's weird. Also I am surprised other party cannot hear if you place the phone on the table. What is up with that...
[Nexus 6P Q&A, Help & Troubleshooting] coolguy949:
Google can't seem to get noise cancellation right. I remember the issue with my N5. I left myself a voicemail back then and was surprised how muffled I sounded. After that, I understood fully why people would keep asking me to repeat things while on a call. I'm still subscribed to the threads on Google Product Forums and it seems they never actually fixed it.

I suggest calling your Google Voice number or something and leaving a message to test.
[Nexus 6P Q&A, Help & Troubleshooting] mlin:
Yeah, noise cancellation is kinda funk though I've actually been pretty pleased with it on the 6p. I do notice times with both the 6p and the 6s+ that sound gets muffled and I assumed noise cancellation was the cause.
[Nexus 6P Q&A, Help & Troubleshooting] cb474:
Ironically, Google once had the best noise cancellation there ever was and was possibly the first to put it in a smartphone. The Nexus One used the Audience chip (now called Earsmart). It was amazing. People regularly thought I was at home when i was in a noisy cafe or out on the street. Subsequently Apple put the Audience chip in the iPhone 4 and it also got rave reviews for noise cancellation.

But it's been downhill since the Nexus One. The Nexus S had no (!) noise cancellation. The Galaxy Nexus had something crappy that I have never figured out what it was. Then the Nexus 4 turned to what is now the default in most phones, Qualcomm's Fluence--it's built into their chipsets; Fluence is pretty medicore and tends to have a lot of issues, compared to the Audience chip. The Nexus 5 also uses Fluence and has had a lot of issues cutting off the beginning and end of people's statements. The Nexus 6 uses Motorola's Crystal Talk and has four microphones (instead of two) for noise cancellation; it seems to be a step up from Fluence, but nothing like the Audience chip. And now I assume with the Snapdragon 810 chipset in the Nexus 6P Google has gone back to Fluence; however the 6P has three microphones, which is interesting; I read at least one person saying it's better than the Nexus 6.

Anyway, probably people should blame Qualcomm, rather than Google. As their chipsets have become more and more common, Fluence has become the default noise cancellation on many phones and it's never been that great.

Strangely, Apple dropped the great Audience chip in the iPhone 5, and people noticed that was a real step backwards. And Samsung, which used to put in in all the Galaxy S and Note phones has now dropped it with the S6. So for whatever reason (probably companies not wanting to pay licensing fees) the Audience chip seems to almost be unused these days, even though it is the best and was a pioneer in the field. Noise cancellation started out great and has only gone down hill ever since.

*

For those experiencing muffled voices, it's possible that the way you're holding the 6P is blocking one of the noise cancelling mics. There is a whole under the camera hump on the back that is one of the mics. I'm assuming the main mic is in the speaker at the bottom of the front of the phone. I'm not sure where the third mic is.

If you block one of the mics that can create issues with call quality. So you might try moving your hand around to see if that improves call quality.

If you take the advice above to disable noise cancellation in the build.prop, your voice will be more clear in quiet places, but you will have no noise cancellation at all and in noisy places it could really suck--every tiny little background sound will probably be picked up and overamplified, for your caller.
[Nexus 6P Q&A, Help & Troubleshooting] anglerstock:
I bet the main microphone is the one in the back and that is ****ed up choice by whoever made this phone. You cannot have a vonference call and lay the phone on the table while speaking because microphones get muted.
[Nexus 6P Q&A, Help & Troubleshooting] cb474:
The main microphone is absolutely not the one on the back. The main microphone is always the one positioned closet to the mouth, when you hold the phone to your head. There is no other way noise cancellation could work. The back of the phone is a very typical place for a secondary, noise cancellation, microphone. There is nothing wrong with that position. It needs to be faced away from the source of your voice (your mouth) and towards an other external sound surrounding you (the rest of the room, space around you, etc.). Otherwise, there would be no way to distinguish what's background noise, from what's your voice, and filter the background noise out. What matters is the hardware chip that does the signal processing. Some (e.g. the Audience chip) are much better than others (e.g. Fluence).
[Nexus 6P Q&A, Help & Troubleshooting] anglerstock:
Main microphone is on the back. Put your phone on a desk and make a call. Good luck having other party hear you ;)
[Nexus 6P Q&A, Help & Troubleshooting] cb474:
You are just completely wrong about this and do not understand how noise cancellation and microphones on cell phones work. The reason placing the phone on the desk may interfere with call quality, is because it may block the secondary noise cancellation microphone on the back and cause the noise cancellation to improperly filter out your voice (as if it were background noise), because it can't tell what is background noise when this secondary mic is blocked.
[Nexus 6P Q&A, Help & Troubleshooting] omnius1:
Thank you for clearing that up, I've seen the same ignorance on different forums besides XDA from people who made a big deal out of this and blew it way out of proportion. This is as ridiculous as one post I saw that demanded there be an LED notification on the back so he can place his phone face down. :rolleyes:
[Nexus 6P Q&A, Help & Troubleshooting] subhani:
In any case, some basic uses like putting phone on table and holding between ear and shoulder results in no mic/voice capture. This is a serious issue. I have experienced at least the latter on more than one occasion and it was extremely frustrating.
[Nexus 6P Q&A, Help & Troubleshooting] anglerstock:
If you use your phone for phone calls maybe you would understand ;)
[Nexus 6P Q&A, Help & Troubleshooting] cb474:
I didn't say it wasn't an issue. I was just clarifying what and where the different microphones are, since some people have complete misunderstandings about this.

Given that one of the two noise cancellation microphones is on the back of the phone, just below the camera visor, and given that covering a noise cancellation microphone will always disrupt call quality, obviously holding the phone between your ear and shoulder (which blocks this microphone) is going to be a problem. Complaining about it isn't going to change it, because the only solution would be for Huawei to redesign the phone. I wouldn't hold your breath for that to happen. If holding the phone that way is a crucial functionality for you, then obviously the 6P is not the right phone for you (though frankly, really? this is important to people?).

On the other hand, it is reasonable to expect the phone to work properly when placed on a table in speakerphone mode. So if that is a problem with the 6P (no everyone is reporting this), then that is a true design flaw. But still, I wouldn't hold my breath for a fix, because there may be no software solution for this (other than disabling the noise cancellation, as some have done--but then of course, you have no noise cancellation, which isn't great either).
[Nexus 6P Q&A, Help & Troubleshooting] omnius1:
I do, the NC mic is located way at the top back of a quite tall phone. It's nearly impossible to grip a phone to your head and have your hand be anywhere near that mic unless your hands are literally half a foot or more wide. So that leaves sitting it on a table in speakerphone or shouldering it. I don't shoulder phones, but I have used it on a table in speaker without any issues. And it's not happening to that many people anyway.
[Nexus 6P Q&A, Help & Troubleshooting] obsanity:
I think everyone in this thread misunderstood your question. From your question I take it you are the one using the Nexus 6p and you are the one who hears everyone else muffled. Which would not have anything to do with your mic but everything to do with the top speaker.

I don't know about you but I personally think this phone is the best sounding phone for calls I've ever owned when it comes to hearing people on the other end. Whether they can hear me OK or not, I don't know. I haven't heard complaints.
[Nexus 6P Q&A, Help & Troubleshooting] subhani:
That was an answer straight out of Steve Jobs' mouth :D. Jokes aside. If there are faults, one shouldn't dismiss them simply out of the view that it may need a HW revision, when the solution may be simpler. One certainly mustn't assume that a phone with one stated defect is simply not for me, since really that is for me to decide and at no point have I given the impression that this is a deal breaker for me.

TLDR; it IS an issue for some. Is there any solution? How widespread is the problem? Nothing too complicated guys. This IS the 'Help' section of the forum.
[Nexus 6P Q&A, Help & Troubleshooting] cb474:
Yes, I thought of making a steve Jobs joke when I wrote that. But if ever there was a case of don't hold it that way, this is it. With the iPhone 4, the problem was you couldn't hold the phone in the most normal way, during calls, that almost anyone would do. Whereas shouldering the phone to your head, especially with cell phones that are so thin and not conducive to this, is a pretty limited use case.

Sure, it could be a deal breaker for some people, but I don't really see this as a design flaw. That noise cancelling mic needs to be on the back of the phone and as far away from the mouth as possible, for noise cancellation to work. The position it is in makes a lot of sense. There aren't a lot of other good places for it, where it wouldn't be more likely to be covered by a finger (like on the side of the phone). If the trade off for functional noise cancellation is you can't shoulder the phone, that's a pretty sensible trade off, I think. You can't please everybody and catering to a very small use case scenario doesn't make sense.

On the other hand, if the phone doesn't work properly in speakerphone mode when sitting non a table, an incrediby common and normal use case scenario, then that to me seems more like a legitimate design flaw.

That aside, part of my point is also, whatever people think of the design and whether it works for them. If they are hoping that mic on the back is going to be repositioned in a revision of the phone, so people can shoulder it, they are deluding themselves. This is not an issue that's going to be addressed. But other noise cancellation issues, that might have to do with the algorithm might get addressed, although it would require more than an update to Android, since the noise cancellation is built into Qualcomm's chipset. I don't even know if it can be updated. So again, whatever one thinks, you probably should take it as a point for deciding whether you want the phone, because I think it's pretty unlikey there will be a "fix" for these "issues."

The most likely thing that might get fixed is just if there are quality control issues, having to do with the position of the microphone inside the phone and the gaskets between them and the holes in the body of the phone. Tiny misalignments can be surprisingly detrimental to the performance of both mics and speakers. That's something Huawei could correct, without having to physically redesign the phone.

So it's prefectly okay to hate the 6P for having these issues and not want the phone. But I think people should set there expectations pretty low if they think they will be fixed. It's much more complicated than as simple update to Android.

TLDR: Don't hold it that way. And now may be the time to lose all hope. (But by the way, some people report the call quality on the 6P is great and it would be nice to hear more from those people.)
[Redmi Note 2 General] kg3:
Found on a Spanish forum: www.movilesdualsim.com/tema/rom-aosp-xiaomi-note-2-massopa-rom-v5.115981/

It says it is multilingual.

There are two versions v5 and v5.1. If the camera does not work in v5 then they say to use v5.1. There is also a deep sleep and auto brightness patch.

AOSP based

CM moded

Bootanimation CM12.1

Wallpapers CM12

Terminal

Dolby Atmos + Fx Audio

File Manager CM12

CM12 Gallery

E-Mail BOX +

Recorder CM12

Two spectacular Webcams

Improved camera

My Remote

Alarm CM12

Screencast

Sony Walkman

Video Sony

Root Explorer

MobileUncletools

functional Framework Gravity +

New icon in settings

Reset MDS

TrueCaller

3C CPU Manager

Brightness corrected

Fixed charge battery with off mobile.

Vibration corrected

Save to SD corrected

and more and more and more ........
[Redmi Note 2 General] chris5932:
Maybe ask him to post the rom here.. I dont understand spanish
[Redmi Note 2 General] JakobiE:
So there's no "Standby"-Showing off in the battery consumption?
[Redmi Note 2 General] martyan:
i tested this too...

but i not liked this... This has several similar apps. For me not make sense has several apps that make samething.
[Redmi Note 2 General] MexiDroid:
i will try it!
[Redmi Note 2 General] darko150:
Hi,

I use this Rom for two months and works very well!

I seem to be experiencing the opposite problem to what everyone else on this forum is experiencing.

Whenever I make or receive a call, the ear volume is always set to the highest which is too loud especially when in quiet environments as everyone around me can hear what the other person on the end of the line is saying, plus it almost deafens me.

Even when I turn the volume down during a call, it always defaults back to maximum volume during the next call.

I looked under the "volumes" section in the settings but can't seem to see an option for this.

I tried to solve with GravityBox - Expandable volume panel, but again volume after call by itself is setting to max

Can anyone help me on this please.
[Redmi Note 2 General] ps000000:
I also found many Chinese custom ROMs, but I am not sure I can post it without DEVs permission.
[Huawei MediaPad X2] Rudolpht:
I have never had this issue on any other device with 5.0+ and wonder if it is unique to the X2

I can do any app that says start at boot up, e.g., Smart Unlock, and any autostart app, and oftentimes the service will not start at boot up

I have downloaded and tried a number of apps and utilities (about 4 init.d utilities and bootcomnand) and unfortunately no dice. "Autostart and Stay" is the latest.

Not only will the service not startup at boot, even manually started (which like Pavlov's dog I have trained myself to do), it does not "stay" ie keep the apps persistent or working in the background. Padlocking the apps (pulling down vs zooshing up in the multifinder/square box background tasks doesn't keep things executing.

This is a big hassle. I'm rooted and would do a single command line type command in boot shell pro, but don't have a command I can toss in to start the process or app and/or keep the process persistent.

Any help appreciated.
[Huawei MediaPad X2] ajsmsg78:
Go into phone manager then settings then shortcuts and add the Dropzone shortcut to your home screen. Then open the shortcut and enable everything in dropzone.
[Huawei MediaPad X2] Rudolpht:
That is great advice. There are still nuances about this phone I need to explore. The nuanced nuance was I needed to have the dropzone shortcut (the service was already turned). I also had to protect it so it would run in the background during sleep (?!?) and after that third reboot it booted the service correctly. It seems like a combo of science and mysticism. But it works & thank you!
[Huawei MediaPad X2] trurl3:
Let's check your energy saving level. Any level higher than lowest one makes problems with prematurely switching off apps.

Energy saving mechanizms are pretty nasty in X2. I have great issues with notifications from WhatsApp and other communicators till I switched energy saving level to the lowest.
[Huawei MediaPad X2] Rudolpht:
Thank you. I have the energy savings set to "Normal" as the next level seemed to save only 5%. I'm learning something new every day. Thank you.
[Huawei MediaPad X2] Rudolpht:
I'm trying to research the wonders of dropzone. The best I can find is that it allows a small set of apps to allowing floating notifications. Doesn't really explain the ability to get autoboot things to work or other magic. I'm grateful that this and some of the protected app changes are making this androud work like it should (or like other phones) . A slight more battery drain but a worthy tradeoff for tearing my hair out.
[Huawei MediaPad X2] ajsmsg78:
If you don't mind losing the No Disturb mode, you can delete the whole system manager app from system/app if you're rooted and you won't ever have to deal with the permission problems again.
[Huawei MediaPad X2] Rudolpht:
I'm up for that. Would that kill the app lock also? Would a Titanium freeze do the same? Guess I can give it a shot.
[Huawei MediaPad X2] Rudolpht:
And… it works. App Lock just as if it didn't exist. Will keep Phone Manager frozen for now. Thanks!
[Huawei MediaPad X2] Rudolpht:
And it seems much faster/smoother, which is saying something since it was snappy to begin with.
[Huawei MediaPad X2] ajsmsg78:
Yeah when it's removed it even seems like the battery lasts a little longer. It's something I wish wasn't even included as just a task manager app would have sufficed. You can always delete the PhoneDiagnose and PowerGenieEngine as well. I can also remove them from the Super Slim KangVIP ROM as well if the majority would like that. My goal is a flashable ROM with no bloat that runs fast, gets great battery life and makes it easy for everyone. In fact, I'm going to remove them from my stock debloated ROM's and the KangVIP ROM's from now on due to the fact that a lot of us are having permission issues. I'll have three ROM's for each. A stock original bloated one, a medium debloated one with most of the Chinese apps we don't use removed but all the stock apps like Email will remain and a maximum debloated ROM and all the Huawei apps that can be removed will be.
[Huawei MediaPad X2] Rudolpht:
I really think the third option, thinnest + gaps + ROM switching would be my winner. Thanks.
[Huawei MediaPad X2] Rudolpht:
I could find and freeze Power Genie 5.6.1.11 to freeze but no Phone Diagnose
[Huawei MediaPad X2] Rudolpht:
Ditched (froze) Swype also
[Huawei MediaPad X2] ajsmsg78:
I updated the thread with an Ultra Slim KangVIP and SIM switching fix.

http://xdaforums.com/mediapad-x2/development/rom-kangvip-5-1-1-b108-t3215851
[Huawei MediaPad X2] Rudolpht:
Cool. I have transparent weather clock back working, without phone manager nonsense. This thread has really changed my X2 experience.
[Huawei MediaPad X2] braisdosgoros:
I'm having the same problem with some services at boot (I'm not rooted yet). I'm not sure I understand what you're explaining here. I created the shortcut to the dropzone and made sure everything was allowed in there. What do you mean by "I also had to protect it so it would run in the background during sleep"? (How do i do that?) Thanks!