yashsingh1/xdaforums huggingface dataset:
[G2 Q&A, Help & Troubleshooting] zac413:
This issue only seems to occur with my car, a 2013 WRX. I connected fine and typically every subsequent time I get in the car and start up as long as Bluetooth is on my phone will automatically connect. This was the case with my Gnex and the moto x. The G2 connects the first time fine but then the next time it won't connect, almost as if it's a different phone. The cars Bluetooth is pretty basic so it will only save one device so I end up having to delete it and start over.

The phone auto connects to other devices like my obd dongle and my outdoor speakers just not the car. And it worked in the car with other phones so I'm stumped. Anyone have any ideas?
[G2 Q&A, Help & Troubleshooting] canecbr600:
Mine auto connects everytime n 2 different vehicles. Doubt its the phone...
[G2 Q&A, Help & Troubleshooting] tron2968:
same problem

I have the same problem with my 2011 WRX. G2 will connect fine the first time but every time after that i need to manually connect and that will only work every 3rd time.Very annoying.
[G2 Q&A, Help & Troubleshooting] chrisexv6:
Have you tried letting it go for a while? I noticed its very slow to reconnect in my car (Infiniti), but it does eventually reconnect.

I havent tested it yet, but I noticed if the screen is on during reconnect, I get a message box saying the car is accessing the phonebook....Im wondering if it pulling the phonebook every time is slowing down the reconnection process.
[G2 Q&A, Help & Troubleshooting] tron2968:
Found a Solution

Found a solution, want to thank 2011_ST over at forums.androidcentral.com for pointing me in the right direction. The WRX head unit is very weird. The paired devices it shows you when you use the buttons to see all devices is different from the paired devices it tells you when you use the voice navigation to pair and delete devices. I had to use the voice navigation to delete my last 2 phones, than pair the LG G2. Problem solved, phone connects in the first 10 seconds after car starts.
[G2 Q&A, Help & Troubleshooting] zac413:
Could you elaborate a little on where you see the different devices?

Since this I've actually gotten a new G2 due to issues with calls not coming through with the first. Still having the same issue. I cleared everything out today and started navigation and tried connecting after that started but I don't see a difference. After turning the car off and back on it doesn't reconnect. It saves the car in my BT settings and if I go in and uncheck and recheck phone and media audio it then reconnects without repairing but it will not auto connect.

For others the WRX Bluetooth I'd very basic, no contacts syncing or anything like that so I know this isn't the issue.

Thanks
[Moto X Q&A] bso44:
Is anyone experiencing this? A significant number of people over on the Android Central forum are experiencing their voices cutting out pretty frequently, especially when there's background noise. To clarify, the people on the other end of the line are saying that the person with Moto X's voice is intermittently dropping out.

Some are speculating that it's a problem with the noise cancelling software.
[Moto X Q&A] johnny grep:
Yep, same problem here... It's all over the Motorola forums too, but they're talking about the Verizon edition. I told them that it happened on Rogers phones too.
[Moto X Q&A] bso44:
That would suck. Mine's on the way but this would be a deal breaker for me if it's not fixed very soon.
[Moto X Q&A] johnny grep:
Well, I think it'll be fixed by software at some point, apparently the bug isn't being exhibited when using voip apps (Skype, csipsimple, etc)...
[Moto X Q&A] Yazzinit:
Not having any of those problems
[Moto X Q&A] bso44:
Motorola is aware of the problem and working on a fix:

https://plus.google.com/104011926387527754068/posts/9bSuwT3YSqg
[Moto X Q&A] Mrglass86:
Confirmed. Def an issue for my. The pizza place hung up on me cause they couldn't understand me. 4 bars too
[Moto X Q&A] jackdforme:
Allow me to be thanked. For cdma versions (VZ and rogers) go to phone then settings and disable voice privacy. First it's BS anyway since cdma to cell is digitized anyway with basic encryption. Second the 48key encryption method I think called is95 umm sucks! It's uses bandwidth on a network that has none and causes breakup and delay. It's an immediate night and day difference.
[Moto X Q&A] nh25:
Thank you for that tip. I was so frustrated with my phone cutting out on the other end I was ready to throw this one in the trash. I exchanged my phone once already because of the call quality and I was on the verge of making the switch to another phone altogether.

Since turning off privacy I no longer have the issue. Thank you!
[Moto X Q&A] jackdforme:
Same here. I was so upset. My first cdma phone. Who knew
[Moto X Q&A] nimos001:
I am also having this issue, but I am unable to find this voice privacy settings? It must be right in front of me here? :o
[Moto X Q&A] jackdforme:
Go to phone and see the dial pad. Bottom right is the three dot menu. Scroll down.
[Moto X Q&A] nimos001:
Got it! Thanks!
[Moto X Q&A] mchimney:
omg yes,

I only spoke to 3 different people today, everyone of them at some point said they couldn't hear me. I love this phone, but this is seriously a major issue. Unfortunately i'm on at&t so i can't try the above fix
[Moto X Q&A] denenatse:
I can't that in Phone Settings. I looked in settings and dialer settings.
[Moto X Q&A] arabanoan:
YOU CAN PUT A PHOTO OF MENU and that I do not find it

pd: sorry my bad english
[Moto X Q&A] jackdforme:
Look at the bottom
[Moto X Q&A] arabanoan:
mine is not equal

Enviado desde mi XT1058 usando Tapatalk 2
[Moto X Q&A] 9kracing:
It doesn't matter because this doesn't fix anything. I'm on Verizon and every phone call I have people complain. I can tell they can't hear me, because I'm asking questions and they just sit there silent. Its really annoying. Especially since I shelled out $705 for a Developer Edition and I can't even use it for its main function.

I really hope Verizon pushes out this update soon.
[Moto X Q&A] bleeper4:
Mine still does it...

Hey everyone, I know it's been a year since this thread has abruptly stopped (to which I credit an OTA update that fixed the voice cutting in and out issue)...but...I just bought a moto x and my phone is doing it. I have the latest OTA software, stock everything, and I pretty much have to yell for my voice to get above the noise cancellation level to be heard on the other end of the phone call. Interestingly enough, if I speak directly into the mic on the backside of the phone, I come through loud and clear.

I've tried the "voice privacy" setting to no avail. I've tested all (three!) of the mics with the phone's built-in "CQATest" app and can confirm that all three are working. I've spoken with motorola support, cleared my cache, did a full factory reset, and still no dice. Can anyone help?? I hate to send this thing back because I'm almost certain that it's a software issue and not a hardware issue.

Thanks in advance, this is frustrating!! If I don't get replies then I'll start a new thread, seeing as this one is old.

[edit] update: I got a replacement phone and everything works fine. Turns out it was the hardware. I have a suspicion that the used phone I bought had its screen replaced, and it messed up the noise-cancelling features of the mics.
[Droid Ultra Q&A, Help & Troubleshooting] xkwwwx:
Hangouts video call Bluetooth keeps disconnecting after 10 seconds. It goes back to speaker. If I try to reconnect Bluetooth it disconnects again after 10 seconds.
[MDA III, XDA III, PDA2k, 9090 General] Robson:
was browsing through ebay and came across this...

http://cgi.ebay.com/Windows-Mobile-...435096710QQcategoryZ32242QQrdZ1QQcmdZViewItem

apparently someone's cashing in on the wm2005 rom upgrades... :?:
[MDA III, XDA III, PDA2k, 9090 General] TheLastOne:
Not AGAIN. What bastards.

This is the XDA 2 version though.
[HTC Droid DNA] platypuss94:
So my DNA was sitting on the bedside table last night and my girls cat pulled the charger cable and knocked it off of the table. When it fell it hit the leg of the table on the top left-hand corner and shattered the screen. I am having digitezer issues now and it is very annoying. Does anyone know where I can get the screen replaced? If that's even possible.

Thanks for any help.
[HTC Droid DNA] _phoey:
They sell DIY kits on eBay, but most cell repair places should be able to do it.

P.S. you can never trust a cat :D

Sent from my CarbonROM 4.3'd HTC DNA
[HTC Droid DNA] fr4nk1yn:
Damn it. These screens must be made of glass! I don't think I've ever heard of screen breaking as easily.

There's lots of threads and tutorials and videos on screen replacement.
[HTC Droid DNA] platypuss94:
You think it's worth trying to do it myself? I used to work in a cell phone repair shop but never done anything like the DNA
[HTC Droid DNA] incident:
I have original screen+ cracked digitizer . The screen is fully working and from original Dna. Do you need? If yes, tell me , i will give u good price
[HTC Droid DNA] platypuss94:
Well my screen is still working I just want to know if it's worth getting replaced. How much were you thinking? I might be intrested
[HTC Droid DNA] fr4nk1yn:
It doesn't appear too bad to do. I'd suggest getting a "frame" and the adhesive as well. Separating them seems to be the hardest step.

Also get a tool kit.
[Nexus 4 General] OfficialTylerBig:
To start with you'll need TWRP

http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.6.3.0-mako.img

Second you'll need the drivers for the phone

http://www.mediafire.com/download/8xb50uktar8096i/usb_driver.rar
[Nexus 4 General] OfficialTylerBig:
I'll post a text tut soon
[Nexus 4 General] OldDroid:
reported ...

(As reference - take a look in the xda rules)
[Nexus 4 General] Toledo_JAB:
I have moved this to the general section.
[LG Thrill 4G] Necrocom4:
ive had the phone since at&t had it on display. rooted it and had various roms for the last couple years and never had any serious issues. last night i flashed jellycream v2 and then did a factory reset inside the rom. the phone prompted that it would reboot twice and that it was normal. it rebooted into twrp and did nothing afterwards. i rebooted it from the recovery and all it did was reboot back into recovery. i decided to flash a different version of twrp and still the same. then flashed clockwork and still got the same result. i wiped the bootloader and basically went through the rooting process again. flashed the latest version of twrp and the phone is still only booting into recovery.

i am at a loss because this is as far as my knowledge goes. its like the phone is stuck still trying to wait for that factory reset from the jellycream rom or something and it wont do anything else but load TWRP.
[LG Thrill 4G] drastic00:
If factory hard reset will not work (with phone off, press power and volume up together for some seconds. You might want to try also holding home on the touch screen.) flashing firmware will fix it unless you have hardware failure, which I doubt.

http://xdaforums.com/showthread.php?p=39269819

Part 1 can be tricky, so take your time and get that right before proceeding.
[LG Thrill 4G] Necrocom4:
so far i get the grey LG screen with 'booti mmc_read xxxx' at the upper left with the hard reset. it only takes 2 seconds to show up but the phone shuts off if i continue to hold the power and volume buttons. ill read up on that link here.
[LG Thrill 4G] drastic00:
I missed that you wiped bootloader. You need that :p. So you could maybe just install the wkpark bootloader in recovery. You would do 1 and 3 here (1.25a file is down the page)

http://xdaforums.com/showthread.php?p=39130435

I think Jellycream actually requires you have it, if I remember correctly.

Not sure why factory reset would cause that issue, but it will definitely not start without bootloader.

Flashing firmware will also write the (stock) bootloader if that does not do it. It will also reinstall the OS if system is corrupt or missing.
[LG Thrill 4G] drastic00:
I can't find the thread for Jellycream2. Would you post a link? Are you sure it is for P920/P925 (same device, one is AT&T branded. I have the Thrill P925). If it is not for those device numbers, you may need xbsall's unbrick guide.

Also, if Jellycream2 is based on ICS and you were on a GB ROM, you would likely have needed to first upgrade to ICS and then install the ROM.

I'm just trying to understand why a factory reset could brick your phone...
[LG Thrill 4G] Necrocom4:
ok basic rundown of what i did in the last year;

when first played around with rooted it about a year ago i used all-in-one to do it. i had already upgraded to ics using the lg mobile support tool prior to rooting. rooting went off fine until i installed a Beats Audio app from the play store. when the phone rebooted after it would be stuck at the grey LG logo. i didnt know what to do so i used twrp and wiped the whole phone. then i used all-in-one and flashed the ICS bootloader and did the flash kernel 4 fix or something its one of the last options to do. then using twrp i flashed ICS_V20_P20, Stock_V20P_Rooted, and a Thrill Update, the phone rebooted fine in an ICS rom but it ran like complete ****, so i tried various roms and the one i settled with was called OptimusRS V1. i used that up until 2 days ago when i flashed the jellycream rom.

after i factory reset that i tried to flash the different wkpark bootloader and twrp that came with the megatron tool hoping that would fix the issue. but it did so i reflashed the original twrp and ics bootloader from all-in-one.

failed to mention this before but i tried 3 different recovery files in between each attempt and it would flash and reboot fine but the phone would still do the same thing and just load recovery.

ill find links when i get off work today. thats the basic history of the phone though.
[LG Thrill 4G] drastic00:
Hmm. Stil not sure then . Maybe a corrupt zip or you wiped something important. Flashing with LG Flashtool should recover it. And always make a Nandroid backup before installing anything from recovery.
[LG Thrill 4G] Necrocom4:
http://xdaforums.com/showthread.php?t=2392309

thats the jellycream rom.

im downloading the files for your xbsa rom at the moment. i do remember yesterday when i used the megatron tool i saw an option to flash the stock bootloader and recovery. i tried it but all i got was the pink LG logo then a security error message below it and the phone shut off.
[LG Thrill 4G] drastic00:
Oh, ok, OptimusRS's ROM.

Hmm, I thought v20 was GB or something... If it is not ICS then that would be the problem. Also it does say there you need wkpark bootloader for that ROM.

Also, xbsall's v28B includes recovery but it is in system partition. I don't know if that ROM requires you install it from recovery partition or not.

If you still want Jellycream you should be able to flash xbsall's ICS v28B (the normal partitions one, not large partitions), then install wkpark bootloader 1.25a in recovery, then the ROM.
[LG Thrill 4G] Necrocom4:
well that breaks down that a bit better. my progress at the moment is step f6. when i connect the phone nothing installs though. it just reconnects and disconnects every second or so. im guessing its because i already have those files. dunno though. i cant get my pc to install the adb drivers for the life of me when the phone is connected in recovery mode.it sees the new hardware just cant find the files.
[LG Thrill 4G] Necrocom4:
actually i got it. for some reason the phone wouldnt install anything until i put the battery back in at that step. i continued successfully to step M. the phone is setting up my google account at the moment.

will flashing the baseband be necessary if my apn and sim work like the phone is now? my provider is h20(canadian i heard) but im the usa.

HUGE thanks regardless :D
[LG Thrill 4G] drastic00:
Cool :thumbup::beer:

The no battery part is just for driver install, which is fiddly for this phone. Sometimes trial and error is a factor.

The baseband you have now would be the one you had previously. If it works, no problem. The one in the v28B pack is supposed to be optimized for the v28B .bin file, but hey, whatever works.
[LG Thrill 4G] Necrocom4:
im only getting E for data. i tried to flash a baseband meant for at&t but it says failed after about 90 seconds. still no 4g though. i did flash the xbsav8 before i set my apn up. i might just go with an optimusRS rom again though. i was happy with it. probably not jellycream this time.
[LG Thrill 4G] drastic00:
Baseband fail after 80 or so sec is normal. It means it worked. Check your baseband in android settings/about phone.

You might try speed test app to compare actual speed. ATT 4G icon is a lie on this phone IMO.

Now that your pc is set up you can flash any P925/920 bin. Kdz files (combo of bin and fls, there is another tool for flashing those files) can be extracted into separate bin and fls, but I have not done it. The advantage is you can flash baseband separately.

Xbsalls vX3D (see his page) with the P925G fls file gives me 4G icon on Straight Talk in the US, but I like his vR3D better, and I can't tell a speed difference, honestly.

I have not actually measured the speed in either, however.

And for either of those ROMs, you must flash his large partition version of v28B first...very important.
[LG Thrill 4G] Necrocom4:
oh its definitely like 2g speeds. its pretty slow. i tried using my providers app and website and its saying the phone i have isnt registered to them anymore so it might be just that. if thats the case ill just bring it in so they can do that for me. when i rooted it the first time i wasnt getting any data and they had to re-register the phone to get it to work right.

my baseband says OMAPP4430/XMM6260. for comparison and/or confirm differences. i have no idea lol.

side question though; my sdcard still has recovery files for the optimusRS v1 rom i had on it. i really liked the setup i had when i made the recovery for it. Im tempted to reinstall it but im really not too sure if itll work or worse harm my phone again.
[LG Thrill 4G] drastic00:
Lots of variables, but you must remember that xbsall's P940 recovery app he he uses has recovery in system partition. The recovery you had before was probably in recovery partition. They write restores from two different places. Probably you would get an error, but not positive. Understanding that may take some Googling...

If you try it, back up before trying to restore the old backup. Then you could hopefully restore if the restore fails, know what I mean?

Probably the safest thing is to use the all in one tool to install recovery in recovery partition and use that one to restore backup.

I do know when I have restored backups, I have wiped Dalvik, Cache, and Factory Reset (in recovery) and then restore. Then it works. Some people wipe system too.

You can usually flash to recover from a problem, but then you have to set your phone up again :rolleyes:
[LG Thrill 4G] Necrocom4:
Well I recovered everything. All settings and personalized stuff. Just everything. Everything is running normal again. Just now my data is saying im using an h20 microcell instead of just H20 with a 4g connection. This 2g stuff is for the birds. I'm almost thinking the firmware we flashed has something to do with it. The phone is functional though. Just slow and no mms. I haven't been able to find much on the forums about it. I'll poke around more tomorrow.
[LG Thrill 4G] drastic00:
I'd try another baseband.
[Droid Ultra Original Android Development] jcase:
Warning:

I will not be responsible for damage to your device(s) by using this exploit. Antivirus software and Play services will likely detect this as potentially malicious. It is an exploit, deal with it or don't use it. Do not mirror these applications without my permission!

PwnMyMoto is a replacement for my previously released MotoRoot. PwnMyMoto exploits three vulnerabilities, to gain root access, then to gain write to system. This is a traditional root, and doesn't use any 'hackery' to maintain su access unlike MotoRoot.

First we use bug 9695860 (aka second masterkey) to gain system user, then it uses a symlink attack to gain root access. After gaining root we exploit a flaw in the bootloader, allowing us to bypass the write protection applied to system. In the process we remove stock recovery, so OTAs will not be a worry.

Install PwnMyMoto by running:

Then run PwnMyMoto, depending on the current root status of your phone it will reboot 2 or 3 times, after the last reboot it will uninstall it self and su will be installed on the actual system partition. Please install SuperSu from the market after this step is done.

We have two (ok more but were not going into that) boot modes. First is normal, which boots regular Android, and in this case boots with system write protected. Second is recovery mode, normally it boots recovery without write protection. Our exploit will hijack recovery bootmode and boot Android without write protection.

After running this exploit, if you boot normally /system will be write protected. If you boot to "recovery", Android will boot without write protection. If you wish to edit system, you must boot into "recovery" to do so, any changes made will stick and will work in either bootmode. My suggestion is to make your changes in "recovery" and run the device day to day in normal mode, until we are certain "recovery" mode will be 100% stable for day to day use.

The exploit will uninstall itself after successful exploitation.

To see if write protection is applied, you can run:

If it returns '1' then write protection is applied to /system, if it returns '0' then no write protection has been applied.

In the future we will have a replacement recovery, but at this time it is still in development. Enjoy.

Change Log:

1.4.3 allows detection of failed su installation (0 size su) and reinstallation)

1.4.1 adds reliability, and fixes issues for users when improper permissions are applied to su (Preventing updates).

1.2 - Bug fix for devices which had recieved OTAs.

If you used 1.1 and have a problem with recovery coming back, run the following command:

1.1 - initial release
[Droid Ultra Original Android Development] redpipe:
Thanks!
[Droid Ultra Original Android Development] Indirect:
Figure I should add that this does not allow usage of custom kernels at this time because everything is still signature checked.
[Droid Ultra Original Android Development] alee:
Is there an unroot process?
[Droid Ultra Original Android Development] phositadc:
I'd assume you could boot into the recovery mode and just delete superuser, su, and busybox, but someone more knowledgeable should confirm.

Sent from my Nexus 7
[Droid Ultra Original Android Development] Dr. Carpenter:
Just an FYI, since I panicked a little, when the little Andy is shown lying on his back and it says "No command", just wait it out :D
[Droid Ultra Original Android Development] mbh87:
It probably didn't work for you then. I was having the same problem earlier and again now.
[Droid Ultra Original Android Development] Dr. Carpenter:
I still have root. It did the same thing when booting to recovery. Guess I'll reinstall and give it another go.
[Droid Ultra Original Android Development] mbh87:
It shouldn't boot to recovery since it is being replaced.
[Droid Ultra Original Android Development] Dr. Carpenter:
Sorry, meant when booting to "recovery". It went to the no command screen for a minute then rebooted to Android.
[Droid Ultra Original Android Development] jcase:
If you are running into an issue where it is booting into normal recovery, come find me on IRC. I think 1.1 fixed the bug but if it didn't i need to release 1.2/
[Droid Ultra Original Android Development] Dr. Carpenter:
OK, not sure what's going on now... The first time I ran it, the button said something like Click to root, now this time it said Boot into WP bypass. Hit it and same thing, back to the no command screen for a while and then a reboot. I was previously rooted, but based on the OP, that shouldn't make a difference. Back up now, and the app is still installed (it uninstalled the first time), still says the same thing.