yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] ckeegan:
OK, so I'm using the Titan (XV6800) and a 2008 Altima 3.5SE with nav. Obviously I'm having the same problem as everyone else. Anyway, I am getting so frustrated with everyone (Microsoft, HTC, but less so with Nissan). I e-mailed HTC yesterday, and received the following response:

This was actually a follow-up to a previous e-mail they had sent me stating that it is an issue with the Microsoft BT stack in WM6 and 6.1 devices.

Anyway, I e-mailed Microsoft Support last night, and received a response this morning. The response simply told me to contact MS tech support via phone. I did. I think the guy I spoke to thought he had an easy out, when he told me I would have to pay $35. Well, no easy out here, since I paid it.

I was on the phone with Microsoft for 1 hour, 42 minutes, and 37 seconds this morning. I explained the issue, and his response was that it was a problem caused by HTC's custimizations after the OS leaves Microsoft. I told him that they told me it was a result of Microsoft's Bluetooth Stack. The Microsoft tech actually conferenced HTC support into the call, which I thought was hilarious. Microsoft said that this was the first they had heard about the issue. HTC told the Microsoft guy it was their fault, and Microsoft guy told HTC it was their fault. It was actually funny to listen to. Basically once it was all said and done, the Microsoft guy said that he would talk to his "lead tech", and HTC said there was nothing they would/could do about it.

I told the Microsoft guy that some people had success by reverting their OS to WM5, and he said that Microsoft would not be willing or able to provide a driver update, that would actually degrade the BT drivers to the WM5 drivers. I basically ended the call by saying that it sounds like Microsoft is unwilling to resolve an issue obviously caused by them.

Needless to say that I got my $35 back, since they were unable to close the support ticket as a resolved issue.

Maybe if we all annoy the crap out of them, they'll do something about it. Being that the Fuze doesn't work, I have to imagine that the XV6850 won't either. So, a year after the XV6800 was released, Microsoft/HTC are basically not even acknowledging that the problem exists, or else they would have revised the drivers.

Total BS in my opinion. Since we're all talking about HTC phones here, I thought the Samsung i760 (also WM6.1) worked with the Altima. Therefore, isn't there any way to extract the BT drivers from that device, and install them on the XV6800, or whatever other device?

PS - I've seen scattered posts in forums stating that the problem does not exist with the 2009 Altima and HTC Diamond.
[Tilt, TyTN II, MDA Vario III General] zen313:
Well, finally found this thread after a while.

You can add me to the list...

2007 G35 sedan with Nav.

Horrible BT connection with:

Mogul (stock and cooked roms)

Touch Pro (Fuze stock)

Sprint Touch Diamond

Suffice to say, I'm pretty pissed. I'm going to go and buy a Jawbone 2 for now, until somebody comes up with a permanent fix.
[Tilt, TyTN II, MDA Vario III General] nc88keyz:
This would have to be either one of two scenarios.

There are different versions of the GPS head unit by zenrin / bose.

OR

its a non GPS bose radio head unit.

Where have you seen these posts.

Im collecting them .

Your call with MS is hysterical btw. Classic.

Noone will accept ownership of the issue.
[Tilt, TyTN II, MDA Vario III General] innoman:
Ugh...

I have the HTC Fuze and Infiniti G35 Sedan... Same as others, choppy audio, etc... I have also tried the Sony Ericsson (HTC) X1 to no avail. The exact same issue. I am certain it is Microsoft, who else would make something so poorly and refuse to fix it? I think Microsoft is the only company that seems to get away with broken software time after time after time... :/

I think we all need to bombard MS with calls and emails.
[Tilt, TyTN II, MDA Vario III General] nc88keyz:
This is the first I have heard of a SE phone doing this. The X1 is sourced by HTC then?

My guess is another phone that uses the MS stack vs widcomm, hence the issue.

At least now its two different phones with results that can be duplicated. Anyone have an omnia yet, CDMA variety?

I could get one and return it i suppose at vzw.

I managed to install M2D on my titan XV6800 running WM5. It works great though. How did i live without it.

The more and more i think about it, i think im going to pass on the Touch Pro. Same small ass screen and same stale BT issues with Nissan/ Infiniti

Somone has been in touch with MS here and giving them some data. Perhaps this should be shared as well.

HTC should feel good that all their phones are borked with WM6 and Nissan / Infiniti Navigation Equiped cars.

I simple firmware update from MS, or Nissan will do. Anyone know if we can swap the BT module for the navigation unit out with a maxima or murano and it would work perhaps. I know its up in the dash behind the AC vents somewhere. I saw a diagram once.
[Tilt, TyTN II, MDA Vario III General] ckeegan:
You must have missed my post in the other thread, but I had the Omnia for about 18 hours. Didn't work with the Altima, but the problem was different. As opposed to choppy audio, there was just dead silence. Transfering the call to handset, and back to Altima worked.

Obviously the same issue, which totally leads me to believe that this is a Microsoft issue, rather than HTC. Especially now with the news about the X1.

I'm the one that contacted Microsoft, and the person I spoke with basically had no answers, but claimed that he would bring it up at a meeting with the other tech leads.

You know, I would be curious to see what happened if one of us loaded an Android ROM on one of our phones. From what I've read, apparently it's still pretty unstable, but am I wrong in thinking it might overwrite the BT drivers in WM6?
[Tilt, TyTN II, MDA Vario III General] nc88keyz:
How about we make a fund for a developer to get the Widcom stack working in WM6+ for our HTC devices with a working HF profile OR fix the MS stack for these vehicles.

I will donate $50 to the cause.

WM5 and Titan however still works fine. I cringe at the thought but is there a WM5 cooked rom for the Pro or diamond at this time?

The biggest problems is that none of the smart people around here have a nissan altima / infiniti apparently, otherwise this would have been fixed with a cab file by now :)
[Tilt, TyTN II, MDA Vario III General] HellsChicken:
I'd donate to that cause. It infuriates me to no end that I can't use the bluetooth connection between my Raphael and my '07 Altima. Bah.
[Tilt, TyTN II, MDA Vario III General] ckeegan:
I just seriously hope that the Touch Pro2 ends up having the problem somehow resolved. Apparently it will be launched with WM6.1 AKU6, and upgradeable to WM6.5.

I still think this issue is ridiculous, and I would seriously consider switching to a non-Windows Mobile device if the problem isn't resolved in the Touch Pro2.
[Tilt, TyTN II, MDA Vario III General] HellsChicken:
I just got the Touch Pro, so it's unlikely i'll be upgrading it soon :(

What really sucks is that none of the work arounds I've seen work for me (ie. switching from the car to the handset then back).
[Tilt, TyTN II, MDA Vario III General] ckeegan:
When it gets posted back on HTC's website, any Fuze users currently having problems with their Nissan/Infiniti bluetooth care to see if the update has any effect?

http://www.engadgetmobile.com/2009/05/28/htc-fuze-getting-big-beautiful-firmware-update-shortly/

Just curious if WM6.1 AKU6 helps at all, since that's what will initially roll out with the Touch Pro2.
[Tilt, TyTN II, MDA Vario III General] louis78:
I have the Touch HD with WM6.1. No progress, same problem than my TYTNII (kaiser)

Do we need now to wait for WM 6.5 ?
[Tilt, TyTN II, MDA Vario III General] ckeegan:
Well, my above post was in reference to an update for the Fuze, which is a firmware update to WM6.1, specifically AKU6. I doubt it addresses anything, but it's worth a shot.

As for WM6.5, I sincerely hope that would address the problem. Sadly I'm not getting my hopes up there either. At this point, the only definite solutions are:

1. Get a different car. (not going to happen)

2. Get any smartphone running something other than Windows Mobile.
[Tilt, TyTN II, MDA Vario III General] louis78:
I selected option 2: I am using an Iphone 3G as my personnal phone. It works very well hand-free with bluetooth.

My Touch HD is used professionally and now I can only receive private call in my car :D My boss has to wait...
[Tilt, TyTN II, MDA Vario III General] Superguy:
Just bought an 09 Altima 2.5 SL with Nav. Got the same issue. I was like WTF?

Strange thing is my friend has a 2009 Maxima with a Diamond and hers works fine. Guess cuz she doesn't have the nav package.
[Tilt, TyTN II, MDA Vario III General] HellsChicken:
Unfortunately, that is true. I just checked Nissan's site again, and it looks like cars without the nav system have more compatable phones (including my Fuze (ie. Touch Pro)), which for some bizarre reason isn't compatable with the nav system. So.... the more expensive system has less compatability. Great.
[Tilt, TyTN II, MDA Vario III General] ELMACHOGERACHO:
speaking as someone who works for infiniti and has a tilt, i can say ive never had a problem with BT in the dozens and dozens of vehicles ive had to test it on for work.
[Tilt, TyTN II, MDA Vario III General] online142154:
Well you are lucky.. but dont discount the hundreds of us who have the problem and no one seems willing to help us out.
[Tilt, TyTN II, MDA Vario III General] TheMaster666:
I have about 20+ phones here, and none have had trouble with the exception of a New Nissan.

I've tried just about everything and Nissan has basically said they didn't care.

Get a new phone!
[Tilt, TyTN II, MDA Vario III General] online142154:
I have paired my Tilt with about 6 different cars and the only problem i have is with my altima coupe with the nav system.

Fortunately most people who know me understand when i answer i have to transfer the call to the phone and back to the car to get it to work... so they wait.

I dont understand why it works after the transfer and not before. I had hoped someone could figure that one out.
[Tilt, TyTN II, MDA Vario III General] ELMACHOGERACHO:
have you tried adjusting the volume? i have had experiences with multiple people who have the incall volume turned up too high causing poor call quality.

there is a tsb for 06-07 m35/45 for bluetooth call quality.
[Tilt, TyTN II, MDA Vario III General] bp787:
I too have this problem with my Fuze on a G35S w/ Nav. :( What sucks is that my $50 Samsung Sync works perfectly.

I've tried it with both WinMo 6.1 and 6.5... No luck, just garbles ontop of garbles.
[Tilt, TyTN II, MDA Vario III General] Superguy:
The work around that works in my Altima (2009 with Nav) is as follows:

Once the call is picked up on the other end, move your selection down to headset and press enter.

Wait 1-2 seconds to make sure the handoff happens, and then press the button on the steering wheel. This will bring it back to the BT connection.

It will work - clear sound, no garbles, and they can hear you fine.

It's a PITA, but the only way it will work. Maybe when WM 7 comes out ...
[Tilt, TyTN II, MDA Vario III General] map70:
Obviously the Palm Pre has this issue as well. I was looking for a phone to switch from my current Samsung i760 (which works). But that has all of the issues that most of the WM phones have. I wonder if it's not just a stack issue but a hardware issue?? Maybe the Bluetooth hardware on many of those phones is to blame as the iPhone seems to work..

This is so frustrating as my 07 Altima 3.5SL w/nav is dictating my phone choices!! GRRR.... :mad:

Maybe we need to band together to show Nissan that they need to fix this.. I wonder if the new 09 stuff uses the same module or if we can swap it out with an newer one?? if they work that is...

Mark
[Tilt, TyTN II, MDA Vario III General] ckeegan:
The Pre does have the issue? That's surprising, and will make it the first non-Windows Mobile device to have the same issue, as far I know.

I thought I had posted it here, but maybe it was on another board. I read a review for the T-Mobile Touch Pro2 on pocketnow.com (link) and they said that the bluetooth stacks appears to have changed, since it takes 3 seconds to connect, as opposed to 1.5 seconds on previous Windows Mobile devices.

I know it's wishful thinking, but maybe that extra 1.5 seconds is what we needed to get this thing working!
[Tilt, TyTN II, MDA Vario III General] ckeegan:
Well, I got my Verizon Touch Pro2 today, and guess what. FINALLY! Yep, works with my 08 Altima without issue so far. No garbled audio, and the other person can hear me just fine.

I actually couldn't believe it.
[Tilt, TyTN II, MDA Vario III General] JReb22:
Seriously?!

Seriously, ckeegan?

Wow, that's great news. I went to the vz store yesterday with a new TP2 in mind (my trusty 6800 is getting a little long in the tooth). One of the things I wanted to do was get them to let me pair one in my '08 Armada with nav sys to see if it worked...unfortunately, they don't have any in the store yet...I was told it was only available on the web site for now.

I'm overjoyed if this problem has finally been fixed. It has been pissing me off for two years now.

Please keep us updated and let us know if you encounter any difficulties at all with your TP2 and the Altima.

Thanks for the encouraging news!
[Tilt, TyTN II, MDA Vario III General] ckeegan:
yep, no problems whatsoever so far. i've made about 4 calls from and received about 3 calls when in my Altima with no problems whatsoever.

the only thing i haven't tried yet is a phonebook transfer.
[Tilt, TyTN II, MDA Vario III General] JReb22:
This is really great news. (other than the bothersome hangup prob mentioned in another thread). Has anyone done a phonebook transfer yet? Also, what about voice dialing? Anyother problems/issues that anyone has discovered?
[Tilt, TyTN II, MDA Vario III General] nc88keyz:
RE: minor hang up issues - TP2 - Altima Nav 07-09

ckeegan,

no issues with hanging up with steering wheel for you?

Its random for me. But more faulty hang ups then others.

I deleted the old touchpro profile and the phonebook entrys thinking it could have something minor to do with it. Its strange. My wife got mad because i said look it wont hang up on you im pressing the phone button or the joystick on the wheel and enter. then it did hang up on like the 3rd call. I cant figure the rhyme or reason here.

I deleted the profile and repaired last thing. I have the verizon version btw.

My car is the Altime 08 Hybrid / My phone is Verizon Touch Pro 2,
[Tilt, TyTN II, MDA Vario III General] ckeegan:
Sorry, been out of town. No issues for me with random hangups, but I'll definitely let you know if it starts happening.
[Other Tools & General Discussion] aatishbansod:
I have checked with all the recent blog regarding volte symbol is not appearing on the top of REDMI 3s prime mobile..

I have reliance Jio Sim & I can't place VoLTE calls as it is not showing..

This mobile specifications showing VoLTE Capable & exclusive button is there but still volte not working on red much 3s prime..

I have tried that same sim with REDMI NOTE 3 it's shows HD & able to place the calls..

I hope this is a bug of prime 3s... Reply if anyone have any idea/ trick as this phone is no use of me as I can't place calls using this phone...I have tried youtube links to resolve the same but no luck...
[Other Tools & General Discussion] Aamirfakih:
Even I am facing same issue I purchased this as a budget phone with power n all facilities however I m not able to juice it up as volte is one major issue n I don't think XDA is looking for it
[Xiaomi Redmi Note 3 Questions & Answers] Yogendra Kher:
Hello everyone.......

Need custom roms with VoLte support.

Please give link if anyone has said roms.
[Xiaomi Redmi Note 3 Questions & Answers] manchitro:
There are plenty of ROMs that support VoLTE for Xiaomi Redmi note 3.

Follow this link for the forum of custom ROM and kernel for the snapdragon variant: http://xdaforums.com/redmi-note-3/development

And this one for Mediatek: http://xdaforums.com/redmi-note-3/x...ek-roms-kernels-recoveries--other-development

You just have to read the original posts to find out if the ROM supports VoLTE or not

Hit thanks if helped
[Xiaomi Mi Note Pro] fobikenobi:
Sign and share, please. This is to get new and official updates from xiaomi. Thanks!!

https://www.change.org/p/xiaomi-android-nougat-7-0-para-xiaomi-mi-note-pro
[Xiaomi Mi Note Pro] Art Vanderlay:
Duplicate thread. See rule 5:

Continue discussion here:

https://xdaforums.com/mi-note-pro/general/official-request-updates-mi-note-pro-t3469163
[Android Q&A, Help & Troubleshooting] illquo:
I have the Huawei Ascend Y300-0151 and am trying to unlock the bootloader, in which I cannot get through their website because it's really buggy and won't accept my information.

So these are the steps I've taken:

- Download SDK Manager and install platform-tools and Google USB Driver

- Boot my phone up and connect to the PC

- I can run the command 'adb devices' and my device shows with a unique ID.

- Boot my phone into recovery/download mode (purple screen).

- Connect my phone, the PC detects it.

- However, when I run the command 'fastboot devices', nothing shows up.

Yes, I have installed a driver for my device and it's now showing as Android Bootloader Interface.

I've run out of ideas and have been googling for answers for a very long time, but to no avail.

Any help would be greatly appreciated, thanks!
[Android Q&A, Help & Troubleshooting] LaserOP:
Given that your attempting to unlock the bootloader of your Huawei device, you should probably send an email to Huawei support requesting for your bootloader unlock code (thats what I did and they replied asking for my device information, and I gave it to them to which I then got my unlock code). For ADB to work you need to boot into fastboot mode, not recovery, then simply use the bootloader unlock code with the following command in cmd: fastboot oem unlock <insert your code here>

And then your done. Be cautious when unlocking your bootloader as you should make sure you have your developer options enabled and the "allow bootloader to be unlocked" option enabled as well.
[Android Q&A, Help & Troubleshooting] illquo:
I have e-mailed them 2 weeks ago and they are not replying. You're meant to do it through their website, but as I've said, I supply the correct information and it either re-directs to a page that is not there or says I am not entering my information correctly when I've done it over and over again.

The purple screen is fastboot mode isn't it? Because that's the screen I'm entering the commands in, but it's not showing up. I cannot enter in a code for fastboot oem unlock because my device will not be recognized by fastboot in the first place.

So before I am to unlock my bootloader, I'm trying to get my device recognized by fastboot.
[Android Q&A, Help & Troubleshooting] LaserOP:
You can send them an email to get the unlock code, trust me, thats what I did. Maybe try contacting them via their support section of their site if you didn't do so last time.

By the "purple screen" do you mean the screen with options such as "HBOOT", "Fastboot", "Reboot" etc.? The "fastboot devices" command should work if it is recognised by the command "adb devices"
[Android Q&A, Help & Troubleshooting] illquo:
I'll give it a go again, thanks.

By purple screen, I mean holding down the power button and both volume control buttons and the screen boots into a purple screen. Just a purple screen, that's it. I can boot into two other modes by holding down the power button and the volume up button and another by holding the power button and volume down button. I don't have a boot mode that displays any options as you've listed above.

EDIT: I'm in fastboot mode now! It was the mode where you hold down the power button and volume down button. Hahaha. I'll let you know how I get on with unlocking the bootloader. Thanks for your help :p
[Android Q&A, Help & Troubleshooting] LaserOP:
No problem, if you found my replies helpful please press the thanks button! It is much appreciated!
[Android Q&A, Help & Troubleshooting] Samrach Kem:
Hello Everyone!

I am correctly using LG G2 F320 that run on Marshmallow 6.0.1 (cm13) and after install this ROM I lost my recovery. Is this a normal thing that happen after install new ROM or what? And now I want to get back my recovery( last Time I use TWRP recovery that I use Autorec KK to install it). But anyway, for now when I try to install it again using Flashify and....another.....I don't know what happen there is no recovery mode or anything. It shows me a black screen. But I know how to return to normal. And now What I want is.....I need you guy to make autorec mm for lg g2 f320. I don't know how to install custom recovery. Please help!!!!!
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
Doesn't sound like you followed the correct way to update your device as you need to have the correct bootstack installed. You should be able to find info on it here:

http://xdaforums.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219

Installation guide for CM13 based roms:

-Flash Bootstacks According to your variants from HERE (click the link above)

- Download the latest build

- Download Gapps

- Take a nandroid backup

- Recommended - Full wipe and factory reset

- Flash ROM using latest TWRP recovery

- Flash Gapps

- Reboot.

- First boot will take a while...be patient, it will boot

You might have to flash the original LG OS and start over to make sure everything is set up correctly.
[Android Q&A, Help & Troubleshooting] medelmennaouy:
Hi,

I was trying to install a custom recovery on lenovo lemon x3 lite (mtk6753), and I have used "format" tab by mistake to format the phone, now the phone is dead, it doesn't turn on, it doesn't even vibrate when I press the power button.

When I try to flash it with sp flash tools I have this error:

[IMG="Screenshot of error"]https://2.bp.blogspot.com/-CCGduWEKzMo/V-pCDd-8R-I/AAAAAAAAAok/i5xphM_AHakpAoYHXwyMDnCFiVLL5K2wwCLcB/s1600/img.png[/IMG]

s_security_secure_usb_dl_image_sign_header_not_found (6045), MPS ERROR CODE 0x00

Please help me I'm so disapointed! :(

Thank you in advance!
[Android Q&A, Help & Troubleshooting] qrxczv:
Phone is LGL33L (Sunset). No stock ROMs or any other useful recovery tools from the LG site, I think. Android version 5.0.1. Kernel version 3.10.49. Software version is L33L10a.

It looks like Download Manager got uninstalled/disabled. I made a full batch backup with TitaniumBackup before messing with anything. It's not restoring, TitaniumBackup is just spinning endlessly...

Is there any way to manually restore this component? Is there another solution to restore it?
[Android Q&A, Help & Troubleshooting] es0tericcha0s:
If it was disabled, in Titanium, it would have a soft purplish hue over the line it's on. If it was uninstalled, the text would be grayed out with a line through the name of the app.

If it was just disabled, you should be able to re-enable it in TiBu or in the Application Manager. If you have uninstalled it, then you might have to find someone else with a rooted Sunset and have them send you the files if the stock rom is not available.

This is why I always suggest to people to only disable built in apps. You do not receive any extra usable space for your own apps and media as the system apps are stored in another partition.
[Android Q&A, Help & Troubleshooting] qrxczv:
I certainly uninstalled it, but not before making a backup from TiBu. I have access to another device of the same make/model. If I were to get a copy of what I neeed off of it, would I have to use TiBu to restore it? Since that might not work, is there any way to extract it as an apk or something?