yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] matthewbudraitis:
I can't say for sure, but based on the test circuit in the spec, I'm assuming they're using a known voltage and resistor value in the device in series with these remote resistors to make a voltage divider. As the headset button resistances decrease, it puts a lower voltage on the mic terminal which can be read by an analog to digital converter in the device. The voltage set points would then be done in software, possibly at a device driver level.

Assuming it works like I think, the set points could be adjusted.
[Nexus 6P General] chowhoundb:
Anyone having issues similar to the Piston 3's (volume down button not working), check out ElementX kernel. Flar2 has included a patch to fix this. Piston 2's still are not working, but it looks like this is fixable in software. Fingers crossed.
[Nexus 6P General] chichu_9:
I just found a partial fix for Piston 2 by trial & error, Remember all the buttons are still not functional yet, but atleast you can hear music using your headphones on Piston 2.

To make it work on your Nexus 6P, Press and hold any button on your headphones while plugging your headphones to your Nexus 6P. Again, none of the controls work but at least you can listen to music. Also, the inline mic does not work during calls :(
[Nexus 6P General] chowhoundb:
The gentleman who figured out how to fix the piston 3's is currently looking into a solution for the 2's. The issue has also been passed onto google engineers to look into.
[Nexus 6P General] Suckers:
Thanks!!!!! Great tip, I was worried about this, I can't believe I can't use my Pistons on my new Nexus 6P.

My two cents, you can plug in your headphones and then press any buton and they start to work, it is not necesary to press a button while you are connecting them.
[Nexus 6P General] subhani:
I have a set of cheap in-ear earphones with a volume slider which works brilliantly. Is this problem affecting only a few 6P owners or is it applicable to button operated volume controls?
[Nexus 6P General] bikeryder007:
I realize you guys might not want to hear this, but my piston 2s have always worked perfect on my 6p. Controls and all, and they sound great with viper.
[Nexus 6P General] chowhoundb:
That is interesting. I thought this affected everyone. Just curious, do you know if yours are piston 2.0 or piston 2.1's. I have a white pair of 2.1's and a brown pair of 2.1's and both do not work.

UPDATE: nevermind, it looks like the 2.1's are the same as 2.0 with just a slightly longer cable, and different earpieces. They have the same internals so there shouldnt be a difference.
[Nexus 6P General] chichu_9:
That's nice to know. I love how my Pistons sound. I cant believe that I am not able to use these puppies with my new phone. I am bummed. :confused:
[Nexus 6P General] bikeryder007:
I just tested them again when I got home from work, and everything is working as it should. I just checked up and down volume and everything. I have the piston 2's with the white cord, silver buds etc... It is weird that so many others are having problems.
[Nexus 6P General] chichu_9:
I have the brown ones.
[Nexus 6P General] subhani:
So I just checked with another cheap set of earphones (you can tell I am not an audiophile and am on a v tight budget) and these ones wouldn't even play the sound! So I followed one of the tips mentioned above i.e insert into jack while pressing volume buttons and voilà, I had playback. But now I can confirm that the buttons on the volume unit don't respond to anything. I'm stumped... My other set of cheapos work just fine! This is the first time I've ever seen a problem of this kind on a phone. It's an even bigger shame for those of you guys who have invested in more expensive gear for your audio. Is Google aware? How can we get them to address this? I do not want to root yet.
[Nexus 6P General] [hfm]:
I've been waiting for my Sennheiser MM30G to exhibit some strange issue but the vol up/dn and pause/play controls have continued to work flawlessly. I have two pairs of them and they both work fine.

Sent from a 128th Legion Stormtrooper 6P
[Nexus 6P General] Raghav_K:
wow thanks.

just flashed elementalx kernel yesterday, did not know a patch was included. tried piston 3 and volume down button is working fine!! [emoji2]
[Nexus 6P General] subhani:
Is there are way to notify Google about this, since the pros here have clearly found a software fix for this. If Google bundles it in one of their updates, it saves us guys who don't have root to address the official way.
[Nexus 6P General] Suckers:
Thats weird. Aye you 100% sure that your Pistons are legit? Thats the only explanation that I find, maybe the original Pistons 2 doesn't work but the cheaper ones yes...
[Nexus 6P General] Raghav_K:
No idea, my understanding is that mi piston 3 is also at fault, by not adhering to android spec. So why should google patch to fix faulting peripherals??
[Nexus 6P General] bikeryder007:
When I got them, I checked to see if they were the original ones, because I was paranoid about it. They checked out. So, I don't know the deal but mine are working.
[Nexus 6P General] subhani:
So what do you advise? Ditch your pricey Pistons and buy earphones that adhere to Android spec only? Isn't there supposed to be a universal standard when it comes to spec? Or are we saying that this is just the proprietary nature of things. Even though they are using a universally standard port, the 3.5mm headphone jack.

(This doesn't apply to just Pistons, but also to my cheapo set of earbuds)

Furthermore, there appears to be inconsistency with the same model of earphone between different owners of the 6P. If out of spec, EVERY Piston owner would have had the same experience. Just saying...
[Nexus 6P General] [hfm]:
I would only accept this argument if it's been proven that the same exact physical pair of pistons have different results on an array of 6P devices.

Sent from a 128th Legion Stormtrooper 6P
[Nexus 6P General] subhani:
I just wanted to confirm that I have tested my earphones on another Nexus 6P and they play sound. In my own Nexus, it doesn't play any sound. I hope that is satisfactory.
[Nexus 6P General] [hfm]:
Oh, I thought we were discussing the controls not working correctly. You definitely need to RMA if you can't even listen to music.
[Nexus 6P General] matteventu:
I have Piston 2.1 and the first time i plugged them in, no sound.

Then I pressed a key and they started working (key pressed after having them plugged in).

After that time, that way never worked again.

Now I have to keep a button pressed while plugging in to make them work.

I also have a pair of Sony MH1c and they worked perfectly as with the Nexus 5 (play/pause, volume + and -).

Now I'm planning to buy the Sony MDR-EX650, hoping that they will work correctly (but they have a single button so there should be no problem).
[Nexus 6P General] fivecheebs:
I picked up my 6p yesterday and had exactly the same experience. No amount of fiddling has helped so far, only thing I haven't done is flashing stock again. Fwiw I'm stock with systemless root.

I wonder what changes have been made to the elementalx kernal?
[Nexus 6P General] J_Dutch:
I fixed it for myself using this app https://play.google.com/store/apps/details?id=com.llamalab.automate

I only had to check how the signal came in and then assign it to the right control. I have a simple Samsung headset and volume up didn't work. Now it does and I couldn't be happier. I think it's a software bug, not hardware.

Edit: look at the screenshot, my volume up enters my phone one the media next instead of volume up, just remapping fixed it.
[Nexus 6P General] subhani:
Does this need root? Does it work on more than one of your headphone sets?
[Nexus 6P General] J_Dutch:
I only have one headset. No root needed for this rule:
[Nexus 6P General] malimal:
Having the volume down issues with some samsung earphones. Both the cheap ones that come with phones and a set of Level headphones. These worked fine on a 5x and a BB Priv. Very disappointed.
[Nexus 6P General] qtipbailey:
My post went to this thread by mistake. Can't delete. ¯\_(ツ)_/¯
[7" Kindle Fire HD General] MeowDude:
Yes, many would say running CyanogenMod 12.1 and having the latest CM Recovery would be great, I did too, and i soft bricked my beloved KFHD7 (tate) :crying: . Now, I will be looking into this, but I don't think CanogenMod makes the recoveries custom for our device :crying: :(. in either case, only trust CWM, TWRP, or Philz for our device. (I personally use TWRP "all day, every day") Just a warning to crack flashers like myself who flash anything and everything available on there device (I've flashed every rom on this forum except for a few recent 5.1.1 roms) :laugh: .
[7" Kindle Fire HD General] twfs:
I have to agree. Wish you had posted this before I flashed it to mine now I'm waiting on a fastboot cable so I can get mine back up and running lol. I think on the one I flashed it didn't even have the option to restore from a backup
[7" Kindle Fire HD General] MeowDude:
Yeah, I just got a 8.9 kindle, (already bricked :'( ) but it was a real bummer when it just kept rebooting into CM recovery. My advice: keep a flash able TWRP zip handy, just in case you get there again, also, I don't think you need a cable, the "reboot to boot loader" option lets you boot into fast boot. And I think a normal cable works once your in it (so long as you have to right drivers).
[7" Kindle Fire HD General] monster1612:
Try running fastboot oem idme bootmode 4000 while the kindle initially powers up (add in -i 0x1949 if needed) to reset the boot mode. After that, it shouldn't stick to booting into recovery.
[7" Kindle Fire HD General] MeowDude:
I will when I get the chance, thanks.
[Galaxy S 5 Q&A, Help & Troubleshooting] tom1314:
First I will start off by apologizing if this has been answered in a different post. I have search and searched but end up with conflicting answers. That being said.,

I have a S5

G900V

Version 5.0

G900VVRU2BOG5

Kernal 3.4.0

Build # LRX21T.G900VVRU2BOG5

Hardware G900V.05

Knox (what ever that means) 2.3

Config J13.SAM.SMG900V.1

Can I root this phone?

If not can I recover any photos after a factory reset with out rooting the phone?

If I can recover photos without rooting what is the best post to follow for directions?

If I can root it what is the best link or post to follow?

I appreciate the knowledgeable people here that will help and guide me to the answers that I seek.

Thanks again,

T
[Galaxy S 5 Q&A, Help & Troubleshooting] ShadowT:
Same problem here. Locked bootloader by Verizon. Several threads mentioned this problem making it not possible to load firmware from earlier versions. Awaiting a solution from other hackers/developer community. Pay for root software solutions not working either at this time.
[ONE Q&A, Help & Troubleshooting] MidnightJava:
I've had the OPO for over a year, and just now had the need to root it. An OTA happened to come in the next day, and the update process didn't work as I expected. So I'd like to know if I did something wrong, a random problem occurred, or this is the way it's supposed to work.

Until a couple days ago, the OPO was stock + all OTAs that had been released. I unlocked the bootloader, installed TWRP recovery, and installed SuperSU. All that went as expected. When the OTA notification arrived the next day, I tried to install it with "Update Cyanogen recovery" still unchecked (because original reports with CM 11S said you could keep your custom recovery with an OTA).

When I tried to install the update, the phone just rebooted to TWRP and the update was not stored anywhere on /sdcard. I then checked "Update Cyanogen recovery" and tried to install the OTA again. It did not install, and TWRP was still my recovery. Several repeats of this had no different result.

Then I flashed the stock CM recovery with fastboot. After verifying I had the CM recovery, I installed the OTA again, and it failed again, reboting to recovery and doing nothing else. Then I downloaded the incremental update and tried to flash that via CM recovery, and that failed too. I checked the file /System/build.opt, and line "ro.build.version.incremental" said 49d90510ef, which meant I should have been able to install the cm-bacon-49d90510ef-to-d91bf047f5-signed.zip file. But it failed and said the current build number was not as expected. The number it gave me was not anything that made sense looking at the list of recent incremental updates.

So at that point I bailed out and installed via recovery the full flashable zip file, and that worked.

If this is what I have to do each time, it's certainly doable, but I don't think this is how it's supposed to go. I'm surprised the OTA didn't work with the custom recovery installed, and I'm even more surprised that the incremental installation failed. Maybe trying to install the OTA without updating the CM recovery messed things up, but that doesn't seem likely either. When the next OTA comes out, I'll see if any of these troubles are repeated. But I'd like to know how the OTA was supposed to work after installing a custom recovery.
[ONE Q&A, Help & Troubleshooting] vince.lupe:
I am still yet to figure this one out also, my friend :) I'm sure with time someone will respond who had better experience with this; just be patient :)

Have you been able to root yet? I can't seem to be able to on the new incremental yet.

[MENTION=4829458]MidnightJava[/MENTION]
[ONE Q&A, Help & Troubleshooting] distante:
Looks like I'm not the only one with this problem.

I'm trying to find now the link for Cyanogen Recovery flashable to see it that fix the OTAs
[ONE Q&A, Help & Troubleshooting] vince.lupe:
Check the CyanogenMod website, [MENTION=4857600]distante[/MENTION]
[ONE Q&A, Help & Troubleshooting] MidnightJava:
After installing the latest CM 12.1 ROM, I had to re-flash SuperSU. After doing that, root access is working fine. If you're having trouble rooting after installing the incremental, then my experience is perhaps not applIcable—since I was not able to do an incremental installation and had to re-flash the entire ROM.
[ONE Q&A, Help & Troubleshooting] MidnightJava:
This thread with Cyanogen mirrors and info has exactly what you need.
[ONE Q&A, Help & Troubleshooting] vince.lupe:
I had to completely re-flash stock 3JL full also, but this time root doesn't work. Tried to use WugFresh's Bacon Root Toolkit - didn't work - then, I tried to flash SuperSu via TWRP recovery (after unlocking bootloader), and that didn't work either? In other words, I have bootloader unlock, custom recovery installed, but no root :/
[ONE Q&A, Help & Troubleshooting] MidnightJava:
What happens when you try to root? Does it seem successful, but then you don't actually have root access? Or do you get some failure indication when you flash SuperSU? I've rooted a few phones in the last few years, but I'm far from an expert. Hopefully someone else will jump in with some idea of what went wrong. Shooting somewhat in the dark, I'd say look at the version of SuperSU and make sure it's the latest and the right one for the ROM, look at read-write permissions on your storage (if you can, you may need root access to check it properly). Of course wiping cache is always a good step, and if nothing else works, maybe factory reset, re-lock the bootloader, and then unlock and flash custom recovery again, and see if root can be successful then.
[ONE Q&A, Help & Troubleshooting] Cholerabob:
Once on custom recovery ( TWRP ) OTAs will NOT not install, unless you revert back to CM stock recovery. If you don't want to do that, wait for a signed flashable version to come out, which is normally 1-2 days after. Everytime you flash an update you will have to reinstall TWRP and SuperSU.

---------- Post added at 03:31 PM ---------- Previous post was at 03:25 PM ----------

Did you guys remove the " Update Cyanogen recovery" in Dev options and "respect CM root settings " In SuperSU settings ?
[ONE Q&A, Help & Troubleshooting] MidnightJava:
I figured that was the case when it failed. What seems anomalous in my case is that even after reverting to the stock recovery and verifying that it was installed, OTAs would not succeed. I didn't know about the "respect CM root settings " In SuperSU settings that you mentioned. Maybe that was the problem? Either that or the fact that I tried to install the OTA first with the custom recovery. Certainly the fact that the incremental installation reported I was at a different build number than what was listed in /System/build.opts indicates something was out of whack on my phone.

Temporarily reverting to the stock recovery and installing the OTA, then going back to custom recovery, seems a bit simpler than flashing the signed zip file and then re-installing recovery and SuperSU, but either way is not too bad. But being an engineer, I always have to find the optimum path and understand why things don't work the way I thought they should.

:)
[ONE Q&A, Help & Troubleshooting] vince.lupe:
It just tells me that I don't have access :/ Everything flashes perfectly fine, but then when I boot up and try to access root, it tells me that I don't have access. I've tried everything already :/

---------- Post added at 06:51 PM ---------- Previous post was at 06:47 PM ----------

I did do both :/
[ONE Q&A, Help & Troubleshooting] Cholerabob:
Not really since the signed zip file come with superSU, after the install it will ask you if you want to install superSU automatically, and TWRP will too when you start your TWRP app on your phone after reboot. But to each his own :)

---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------

Is your bootloader unlocked ? Reinstalled superSU ? Did you check with the fastboot command ? If you don't know how, look at Heisenberg's guide.
[ONE Q&A, Help & Troubleshooting] vince.lupe:
Yes, bootloader is unlocked and SuperSu was reinstalled :/
[Verizon Galaxy Note 3 Q&A, Help & Troubleshooting] stk23452:
I'm still on the OEM MI9 build. I got my phone about a week after it was released, rooted it using the Root de la Vega method, I then froze all OTA methods with Titanium Backup and, due to the lack of custom rom availability back then, was happy with just installing some Xposed modules. But 2 years later my Note 3 is feeling a little old and I want to try to breathe new life into it with a custom ROM.

I've been reading up on the state of custom ROMs with this phone but there is a lot of information to take in. I want to try to install and run JasmineROM v6.1 (Seems to be the most active ROM available for this phone) as my daily driver. I have seen numerous posts stating that going above android 4.4.2 will put me at risk of losing root and I want to prevent that as much as possible.

Is there an easy way for me to clean my system (remove all apps and data) without me moving to a higher android build and losing my root?

Would it make the most sense for me to install multisystem, use my MI9 build as the stock partition, and then just run the JasmineROM in a virtual slot or am I completely misunderstanding how multisystem and custom roms on this phone work?

Can I stay on MI9 or do I need to update to NC2/NC4 that most threads talk about before installing any custom ROMs.
[General Topics] Sefy:
I hope someone will help me sort this out, i have two SDA's with WM6 now and on one of them i installed the Eyron Hebrew Support and on the other I did not. Mostly because i don't need to type and i just want to view.

Unfortunately the Eyron Installation causes serious display problems with regular English program because of the Bidi Interface (and they expect people to pay?!) but what i want is just the hebrew visibility even if it's mirrored.

The problem is that if i import the FontLink of the registry, it makes my English letters in a lot of section seriously bolded out and ugly. So i'm hoping if you guys see the Hebrew FontLink Registry, you'll be able to tell me what to remove.

Attached are two images so you can see the Bold Fonts:

1) With Eyron

2) Without Eyron

and this is the FontLink registry from after installing Eyron Hebrew Support:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\Software\Microsoft\FontLink]

[HKEY_LOCAL_MACHINE\Software\Microsoft\FontLink\SystemLink]

"SegoeWGLCondensed"="\\Windows\\nina_cs.ttf,Nina"

"Segoe Condensed Bold"="\\Windows\\TahomaBb.ttf,Tahoma Bold"

"Segoe Condensed"="\\Windows\\Tahoma.ttf,Tahoma"

"Nina"="\\Windows\\Segoe.ttf,SegoeWGLCondensed"

"SC_Song"="\\windows\\segoe.ttf"

"Tahoma"="\\windows\\segoe.ttf"

"Courier New"="\\Windows\\segoe.ttf"

and this is from the WM6 English ROM:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\Software\Microsoft\FontLink]

[HKEY_LOCAL_MACHINE\Software\Microsoft\FontLink\SystemLink]

"SC_Song"="\\windows\\segoe.ttf"

"Tahoma"="\\windows\\segoe.ttf"

"Courier New"="\\Windows\\segoe.ttf"

"Nina"="\\Windows\\segoe.ttf"

"Segoe Condensed"="\\Windows\\segoe.ttf"

Just tell me what i need to do to NOT have the BOLD fonts in English! :rolleyes:
[General Topics] Sefy:
Anybody ? :(
[T-Mobile Samsung Galaxy Note5] Raul69.atl:
I hate that when I'm watching a movie I click them and it messes up my movie or video.

Is there a temporary disable or anything??
[T-Mobile Samsung Galaxy Note5] JonathanRAZ:
Well i think graviti box does something but if you dont have xposed or you dont use it you might want to download Mx Player It Has A Lock When Watching A Movie

TEKHD ROM[Advanced Hybrid Edition ll][UrV4.1]
[T-Mobile Samsung Galaxy Note5] Raul69.atl:
I'm stock
[T-Mobile Samsung Galaxy Note5] Joecascio2000:
Settings > Lock screen and Security > Other Security Settings > Pin Windows

Then just uses the recent apps button and tap the pin icon for the app you want to lock.
[One (M9) Q&A, Help & Troubleshooting] Malvarose:
Title says all. I want to back to stock so I can get latest firmware. I am S-ON, and don't plan on paying $25 to get S-OFF. I did search, but any results were for S-OFF or had dead links.
[One (M9) Q&A, Help & Troubleshooting] Tirofog:
If you unlocked bootloader/installed TWRP the right way then you will have a stock System image backup. If you don't then get one here. This can be restored in recovery after mounting system read-only, see this post. You will then also need to restore stock recovery to be able to take an OTA, details in the same post.

This stuff is all out there if you search and read!
[One (M9) Q&A, Help & Troubleshooting] aer0zer0:
Might need to SOFF so that way u can RUU and go back to full stock, the take an OTA.
[One (M9) Q&A, Help & Troubleshooting] s3lphctr1:
No Need to S-Off to return to stock, Im S-On and went about it this way. Go to this link HERE and start at step 5 to get back to stock. Then for the firmware updates go to his link HERE and download the the ruu that you would need (for me it was att's offical 2.11). Then connect your phone to a pc, make sure you enable USB Debugging and give permission for the pc to connect. Run the RUU, this will upgrade you to the newest firmware and stock rom. It will remove your recovery and root so you will have the go threw the steps to flash TWRP or what ever recovery (start at step 1 at the first link posted) and then re-root your phone. After that your all good :D
[One (M9) Q&A, Help & Troubleshooting] Snookers:
Are all the M9 recoveries the same? The only RUU my carrier (Telus) has is on 1.32, and the links provided were AT&T's. I'm currently S-ON.
[One (M9) Q&A, Help & Troubleshooting] efrant:
No they're not all the same. There's always a recovery in the the OTA update, so you can extract it from there on the next update if you can wait.
[One (M9) Q&A, Help & Troubleshooting] s3lphctr1:
you could look at Android Ruu to see if they have your carriers ruu listed, my bad on the att links, the Windroid Tool at This Link Here might be able to help you find other ruus and recoveries, Ive used this tool a lot, but not sure if it fully supports your M9 version. Hope this helps you some.
[XDA Assist] cristianflorea78:
My phone is stuck on.the message look like this. "WARNING BOOTLOADER UNLOCKED".Please help!thanks!

i rase by mistake the android sistem :(.What can i do?