yashsingh1/xdaforums huggingface dataset:
[MTCB Android Head Units General] halloj:
It says in the plug schematic w/o 9C1........ What unit is that?
[MTCB Android Head Units General] countbuggula:
Yep. No response at all when I connect the Key1 and/or Key2 wires to the PAC module's SWC wires. If I tap the factory SWC wire directly to Key1, it beeps when I press a button but it's the same voltage for every button so I can't actually map more than one function. If I connect Key1 to the factory SWC wire without that wire continuing on to the aftermarket harness, there is likewise no response at all. So it must be some sort of digital signal that the PAC adapter is interpreting - I read that it's called GW-LAN.

I haven't yet taken a multimeter to the wires coming from the adapter to see what's what - if nobody else has any suggestions that's my next step.
[MTCB Android Head Units General] countbuggula:
Ok. Spent a bunch of time last night with a buddy of mine who's a much better electrician than I am trying to figure this out. After much searching and probing, we determined that key1 and key2 should be connected to the white and red wires coming from the PAC adapter. But the HU still isn't recognizing anything and the multimeter doesn't detect any ohm difference registered on those wires when we press steering wheel buttons. So I'm going to contact the manufacturer of the PAC adapter and see if I have a faulty unit or if I'm missing something.
[MTCB Android Head Units General] halloj:
You haven't answered my question #3 yet. Which might be a way to figure out a solution. Anyway

you talk constantly about key1 and key2, but you never mention key-ground.

The resistance is referred to ground not a balance between key1 and key2.
[MTCB Android Head Units General] countbuggula:
Sorry, I didn't answer because I didn't know the answer. Based on our testing last night though, it's a variable voltage that sends a slightly different load based on what button is pressed.

Also, Key-ground? Maybe I'm missing something but I never saw a key-ground wire. What color is it?

edit:

here's the wiring harness. I don't see a key-ground.

[IMG="Wiring Harness"]http://www.carjoying.com/skin/frontend/rwd/default/images/accessories/Harness/ISO/UISO1/1.jpg[/IMG]

[img="alternate image"]http://www.carjoying.com/skin/frontend/rwd/default/images/accessories/Harness/ISO/UISO/1.jpg[/img]
[MTCB Android Head Units General] halloj:
That's a pity because as I said it might be a part of the solution. It's black. The way SWC works is what you found out last night.

It's normal resistor ladder with a different voltage drop depending on which resistor/resistors is/are active. Key1 is normally for the left side switches

and key2 for right side. Not all cars are using both keys. Some, like Hyundai/KIA uses only key1 for both sides. If your car is using the Can-bus

for SWC that's when you need the PAC.

This has already been described several times in different threads. Even how the PAC is used in different cars have been discussed several times.
[MTCB Android Head Units General] benklop:
This vehicle has a single key wire coming from the wheel. An oscilloscope connected to the vehicle key wire shows every button gets tied to +12 through a different resistor. When the key wire is tied through a 3.3k resistor to ground, we got varying voltages from ~10v to ~1 volt for each button, so i think it's safe to say the key wire in this vehicle is referenced to +12 instead of ground.

We did test the key1 and key2 outputs from the PAC module against ground and each other, and never measured any resistance there no matter the combination of wires tested, so I think it's safe to say the PAC module didn't know how to handle the signal the wheel was providing. Since [MENTION=1008438]halloj[/MENTION] is suggesting the PAC module is supposed to be interpreting can-bus and converting that to a resistor ladder, I think that makes sense.

It also makes sense, if the head unit is supposed to be detecting resistance from the key wire to ground, that it wouldn't work connected directly since the vehicle key wire seems to reference +12 instead.

---------- Post added at 11:16 AM ---------- Previous post was at 11:14 AM ----------

in case it wasn't clear, I'm the friend who was trying to help decipher why this wasn't working.
[MTCB Android Head Units General] countbuggula:
You're talking about just the regular ground then? I mentioned in my first post that I tried that (Key1 to Factory SWC) and it doesn't work - turns out as Benklop said that's due to it wired to +12v instead of ground.

Since my car only has one factory SWC wire, it would seem I'd only ever need Key1. However, there are three SWC wires coming from the PAC module, which I'm guessing would be connected to Key1, Key2, and ground. Is there a separate Key-ground wire coming from the HU that I should be connecting to that? When I connect it to the regular black ground, it still does nothing.

It seems that in the case of these GM cars instead of converting can-bus to resistive, the PAC module is converting the +12v resistive signal to a ground resistive signal that can be read by the HU.

I promise I searched extensively and found those threads before posting here. None of them either matched my car's setup or resolved my issue. I also found a review on the wiring harness on Amazon that indicates at least one other user having success connecting this particular harness to my same year Chevy vehicle and getting the SWC working, but he doesn't describe exactly how he wired it in the end other than setting it to 7 for Pioneer.
[MTCB Android Head Units General] countbuggula:
So I ended up calling PAC tech support and after him insisting that they don't support Android headunits, and my insistence that it's Pioneer compatible (and a little white lie about it having a 3.5mm headphone jack for the SWC input) plus explaining that even without the HU plugged in it wasn't registering anything on my multimeter, he finally decided he'd walk me through some troubleshooting. This is what he had me do.

(pre-call) I had reconnected the Key1 and Key2 wires to the white and red wires from the PAC SWC output.

Turn off the car, unplug the PAC harness from the car, make sure the driver's side door is open

Turn the adapter SWC from 7 to 2, then back to 7

Cycle the ignition key from off to on 3 times, leaving it set to "on" the third time

Plug the harness back in to the factory connector

Wait for the HU to fully boot

Lo and behold, now the steering wheel controls work. I don't know what kind of voodoo magic this is, but it worked. Thanks for those who responded and took time to try and help me with this crazy issue. Hopefully this helps for someone else who runs into the same issue.
[Verizon LG G4] phonepie:
Originally thought to be just serial numbers ending in 509 and lower were doomed to get the bootloop issue I can confirm that it also affects G4's made after October ending in 510. Ticked to say the least. Bought it brand new on ebay to make sure I could specifically get a later release and it did it anyway so no warranty. I'll never buy LG again. Sticking with Samsung and the S7 will be my next phone.
[Verizon LG G4] Juice3250:
What were you doing when it happened?
[Verizon LG G4] phonepie:
Wasn't doing anything. And hadn't for about an hour. It was just sitting on my desk about a foot from my laptop just sitting there and then it shut down and has been stuck at the lg screen. I was only able to get it to turn back on again for about 2 minutes by leaving it in my freezer for 10 minutes so I could contact a few people that only have apps to let them know I wouldn't be back on for a while.
[Sprint Samsung Galaxy S6] MP808:
I'm looking for a way to copy my Google account, then delete it on reset or shutdown, and restore it when the phone turns back on. This is an attempt to bypass FRP locks due to rooting/recovery manipulations. This is my way of being able to use Google sync features, root, and TWRP without FRP bothering me. I didn't want to have to reflash on restart due to an update or in case the phone froze or something. I've been deleting my Google account before restarting and thought if there was a way to copy the info, delete the account, and restore it, then my phone won't turn off at boot from FRP. Is there anyway to do this? I had to post here because of low post count. I'm using the G920P on PD3 w/CF Root. I can also use PF4 as well with same root. I don't currently have TWRP on the phone, but I can put it on there.
[Sprint Samsung Galaxy S6] MP808:
Anybody? Is it to long of a post, or just a mess of information? It seems like a fairly easy solution to avoid FRP lock...What were the security updates in PF4 and PG1 anyway?

Thanks everyone!
[Sprint Samsung Galaxy S6] koop1955:
First off, I have never had this problem, not sure why you would run into it.

Secondly, you can use Samsung's SideSync program to solve this. Google it or look at the videos on YouTube.
[Sprint Samsung Galaxy S6] MP808:
Koop have you rooted your G920P with CF Auto Root? My Knox counter is at 0x1. I had used CF Auto Root and added TWRP on PD3 and even PF4. If I have a Google account added to my accounts section and root, I will get a FRP lock when I restart the phone. That's even without TWRP. As long as one of two banks in download mode are custom, FRP is there to ruin the day. Are you not getting a FRP lock with root and/or TWRP with a Google account?? FRP lock goes away if I go into accounts and remove my Google account before shutting down or restarting the phone.

What I was asking was, is there a way to copy your Google account to somewhere, remove it from the Accounts section in the phone before restarting or shutting down through an app or from the power button, and then restore it when the phone has completely booted to avoid FRP. Running Flashfire without even flashing anything gave me custom status. I would love to have CF Auto Root and TWRP or CF Auto Root and Xposed and still be able to have a Google account in my phone.

Any other solutions? I believe I may have confused those who have read this post.
[Sprint Samsung Galaxy S6] koop1955:
Just FYI, not only have I rooted my phone with CF-Auto-Root but I have written the tutorials on how to do it. And no, no FRP lock for me ever.

You will find if you read these forums that most people aren't experiencing any such issue. You are simply doing something wrong.
[Sprint Samsung Galaxy S6] koop1955:
Of course that is the issue. But the bigger issue is not searching the forums or even just using Google.

My tutorial here: http://xdaforums.com/sprint-galaxy-s6/general/guide-links-files-update-root-restore-t3366862

Step 4) Let your phone finish its rebooting process. Then, on your phone, go into Settings -> About Device. Scroll down to Build Number and tap that until it says "Developer mode" has been turned on. Go back to settings and you should see Developer Options. In Developer Options, make sure that OEM unlocking is turned on. It never hurts to turn that off and back on to really make SURE! Simple step that can save you a lot of grief.
[Moto X Q&A] Raulino4567:
Hi i did something stupid with my moto x, i downgraded my moto to kitkat and i tried to update to lollipop so i installed the ota update for lollipop later it just turn off, it doesnt charge or turn on, i have a problem who can help me pls. Green light not works, i dont know what to do PLS HELP
[Moto X Q&A] dtrud0h:
Try using a different charging cord, also just try plugging in and out a few times. Mine did the same thing (not due to update) but it turned out it was the charging cord was bad.
[Moto X Q&A] Raulino4567:
Nothing man, but thanks for try
[Moto X Q&A] fireandknives:
Exact same thing happened to me

After getting "update now or in <24hours" for the last 6 month I decided to properly re flash my phone to get the latest version so the update would go away.

I used this guide to install the recommended version 5.1.0-LPA23.12-15.0

http://xdaforums.com/moto-x/general/xt1053-222-27-5-stagefright-ota-update-t3210786

only thing I did differently was use my already installed mfastboot which worked without error

Everything worked fine, battery at 90%. I downloaded the OTA update and rebooted to install and put the phone down and come back after a moment. Phone is black, try to power on with Power and Power + Vol Down. Nothing works. I also tried charging and charging and pressing the buttons.

As far as I know it's just ****ed and there is nothing to do about it but any suggestions I would be willing to try. For anyone else I would not recommend this just in case try the TWRP System Image or the newer builds.

Edit:

I made an error by updating to the more recent one before re-flashing to the recommended one, this is known to hard-brick your device. http://xdaforums.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057
[Moto X Q&A] Comixz:
Moto X won't charge or turn on

My MOTO X xt1056 doesn't charge while it is off and the charger port is broken due to the plug becoming lose from daily use for 3+ years. The best bet to do is to return it to the store and tell them that it just stopped charging and they should replace it with the same device or a slightly used newer model.
[OnePlus 3 Questions & Answers] acheney1990:
I'm wondering what to do, should I sent it in for repair? I've had it about a month. Since day 1 I've noticed a few issues. First Bluetooth has been terrible and would disconnect from my car. Well would say connected but would start playing over phone speakers. Also when using GPS apps such as Google Maps the phone would restart. Also I keep getting GPS signal lost over and over in both Google Maps and Pokémon Go. I tried reinstalling different versions of of Oxygen and they help for a few hours but then the issues start up again. I've also tried CM 13 and the issue still persists. I have ordered a shipping label from One Plus. I know RMA is a nightmare but do you think I should do it? What will they do when they get the phone?
[OnePlus 3 Questions & Answers] acmerw:
got sensors problem, no proximity, compass, camera started to lag. reflashed stock rom, still the same. ordered rma, today checked at Arvato, they replaced motherboard and sended back phone to me. it was repaired in Germany, tooked 4 work days till dispatch. If your phone isn't 15 days old from purchase, i recommend to get replacement instead of repair. Good luck
[OnePlus 3 Questions & Answers] acheney1990:
Unfortunately it's been more then 15 days. Thanks for the info though. I was wondering what the process was. I just don't know what else I could do to fix it other then send it in.
[OnePlus 3 Questions & Answers] Gerrit507:
I also have issues from time to time with bluetooth. I'm currently on CM btw. If I connect my phone to my car, it shows connected and also the bluetooth volume is available but it does not play music at all.I have to reboot and everything is fine but I found also a workaround. If I start playing music before connecting it worked 100% of the time... Very strange... My GPS disconnects didn't went to zero with cm but it's a lot better. With OOS I had disconnects like every 15 min and with CM randomly every few days.
[OnePlus 3 Questions & Answers] Xeese:
Do you have another device you are ok with using if your phone is off to RMA for a week or more?
[OnePlus 3 Questions & Answers] vmartinez39:
Support is pretty good they'll fix it. Just have to have a spare should that be an issue.

You'll need to create a OnePlus account and register your device. Should be there if you bought from them directly. Then open a ticket. Turn around time was like 10-15 days depending on the issue. I've had a good experience.

Experience was alright. Their repair center is in Texas so should be alright.
[Android Apps and Games] theGeekyLad:
Hello guys, an avid follower of XDA, yet posting for the first time I bring you to a simple app for the 2015 Nexus line, call Bio Snap. What it does is simple. We all know that with your root access, we've got everything. Popular smartphones these days sporting a rear side fingerprint sensor let you snap selfies by just tapping the it. However the 2015's Nexus couple don't seem to sport such a feature out of the box. This app bridges that gap - lets you snap selfies with ease using the Nexus Imprint scanner at the back.

Note that this app

• requires ROOT ACCESS

• has been tested only on the Nexus 5X and the Nexus 6P

• *works fine and tested only with Google Camera right now*

• support for more camera apps will be brought in soon

Also this app is still under development and I thought of writing a post since many of my buddies wanted such an app. (Originally suggested by my close friend Siddharth)

Credits go to

• Sid a.k.a. Siddharth Menon (nandasid10@gmail.com)

• theGeekyLad a.k.a. Rahul Pillai (that's me) (rahul.pillai03@gmail.com)
[Android Apps and Games] Heisenberg:
No valid download link, thread closed.

[MENTION=5283490]GizmoAdept[/MENTION]

If you have a link to add please PM me.
[Droid Ultra Q&A, Help & Troubleshooting] yoloman123:
I updated to the latest version a few weeks ago, I am on 4.4.4 SU6-7.7. I am wondering if there is any possible root methods working for this update, or do I need to flash my device to a lower firmware then go from there?
[Droid Ultra Q&A, Help & Troubleshooting] yipitin:
did you get this done?? I'm working same issue.
[Droid Ultra Q&A, Help & Troubleshooting] yoloman123:
Nope... I honestly doubt I will EVER get to find a root my phone. According to some people, it's nearly impossible.
[Droid Ultra Q&A, Help & Troubleshooting] Blazin Ace:
I also gave up, is there a way to use xposed without root?
[Droid Ultra Q&A, Help & Troubleshooting] L504BZ:
Never update...

Just do what everyone else does.. Download KingRoot app and keep checking back momentarily. No root = NO XPOSED :(

Download SunShine from theroot.ninja and check eligibility. If compatible, pay $25 - or not. Good luck to you
[Droid Ultra Q&A, Help & Troubleshooting] fahadmm:
hi i am using xt1080 latest firmware, i was able to root my mobile with kingoroot app which bears a lock in icon, not the crown one ( v3.1), however root is for like 5 mins then root allow option does not work, i would like to invite developers if they can setup anything during this time so we may unlock bootloader setup custom recovery and enjoy marshmallow or nougat i will visit back thankshttps://youtu.be/5-dbcs5LpiwKINGOROOT NOT KINGROOT

V 3.1 LOCK IN ICON

WAITING FOR HELP
[Droid Ultra Q&A, Help & Troubleshooting] bankanidhi:
this looks encoutaging

some developer please come forward and try for a permanent root.

Thanks in advance
[Droid Ultra Q&A, Help & Troubleshooting] immi420:
anyone find the method to root this...?

please share method for latest su6-7.7
[Android Q&A, Help & Troubleshooting] hamalawlaw2004:
Hi all

i have a general mobile Discovery Air Phone which is kitkat 4.4.2 firmware

and i want to change my firmware to android 5 or 6

how to do it???????

PS// There is no official update for my phone

Thanks to ALL
[Nexus 6P Themes and Apps] theGeekyLad:
Hello guys, an avid follower of XDA, yet posting for the first time I bring you to a simple app for the 2015 Nexus line, call Bio Snap. What it does is simple. We all know that with your root access, we've got everything. Popular smartphones these days sporting a rear side fingerprint sensor let you snap selfies by just tapping the it. However the 2015's Nexus couple don't seem to sport such a feature out of the box. This app bridges that gap - lets you snap selfies with ease using the Nexus Imprint scanner at the back.

Note that this app

- requires ROOT ACCESS

- has been tested only on the Nexus 5X and the Nexus 6P

- *works fine and tested only with Google Camera right now*

- support for more camera apps will be brought in soon

Also this app is still under development and I thought of writing a post since many of my buddies wanted such an app. (Originally suggested by my close friend Siddharth)

Credits go to

- Sid a.k.a. Siddharth Menon (nandasid10@gmail.com)

- theGeekyLad a.k.a. Rahul Pillai (that's me) (rahul.pillai03@gmail.com)

Get it from Google Play
[Nexus 6P Themes and Apps] Savetheknot:
Good app. It works! However when I take a selfie it opens the Bio Snap app. Is there any way to let it stay in the camera app? Also there home screen is very hard to read. I get a white background with white text.
[Nexus 6P Themes and Apps] Mikey:
FYI.....

11. Don’t post with the intention of selling something.

Don’t use XDA to advertise your product or service. Proprietors of for-pay products or services, may use XDA to get feedback, provide beta access, or a free version of their product for XDA users and to offer support, but not to post with the intention of selling. This includes promoting sites similar / substantially similar to XDA-Developers.com.

Do not post press releases, announcements, links to trial software or commercial services, unless you’re posting an exclusive release for XDA-Developers.com.

Encouraging members to participate in forum activities on other phone related sites is prohibited.

Off-site downloads are permitted if the site is non-commercial and does not require registration.

Off-site downloads from sites requiring registration are NOT encouraged but may be permitted if both of the following conditions are met:

A) The site belongs to a member of XDA-Developers with at least 1500 posts and 2 years membership, who actively maintains an XDA-Developers support thread(s) / posts, related to the download.

B) The site is a relatively small, personal website without commercial advertising / links (i.e. not a competitor forum-based site with purposes and aims similar to those of XDA-Developers.com.)
[Nexus 6P Themes and Apps] zelendel:
Please follow all rules before making a new thread. We have a paid apps section if you meet the requirement. Thread closed
[Tilt, TyTN II, MDA Vario III General] Behold:
Its not ringing when a call comes in. It also does not vibrate.

The sound is up on the PPC and Ringer and if i go in to the phone settings it will play a ringtone fine.

Any ideas?
[Tilt, TyTN II, MDA Vario III General] mutantblack:
may be a reset might help? It also happened to me and after a reset, it all works good.
[Tilt, TyTN II, MDA Vario III General] Draqula:
Don't know if it's the same thing with me, but my kaiser also at some point of day refuses to ring (still vibrates ok). It won't play mp3s with GSPlayer or MediaPlayer. Sometimes you can hear the song playing really quietly (only hear it if you press your ear to speaker).

It has happened like that for 3 days now. The sound will come back if I hit the tytn II gently (more like knock it). Althoug since today I'm not sure if it's the knock or the keyboard moving wich brings the sound back.

Any ideas?

What I've tried so far:

- Muting, unmuting

- changing volume

- soft reset
[Tilt, TyTN II, MDA Vario III General] mutantblack:
hard reset it. may be some programs you've installed might be conflicting. If the hard reset don't fix your problem, then you have a faulty unit. You can also try pocket mechanic to clean the registry and stuffs. Very helpful program.
[Tilt, TyTN II, MDA Vario III General] Draqula:
Ok, will try hard reset.

Although I doubt it will help. Before hard reset, there was some very faint sound coming from the speaker. And speakerphone didn't work at all.

Back to resetting...
[Tilt, TyTN II, MDA Vario III General] midyatspor1000:
Try to change the ring tone to a different one, mine was doing the same thing it would only virate, I changed to a different ringtone and it worked fine.