Related
Hi. I need help badly. I recently bought an XDa2s - which i later on returned because of a financial dispute (another problem/story!). But before this, i had an XDA2.
Since I had used the cd's that came with the XDA2s on the same PC that I was using the XDA2 on, when i tried to sync my XDA2, it picked up some of these files. I stupidly went on to sync, and now when i recieve/make a call, there is no sound on the phone.
It can make/receive calls, but when the other party picks the phone, they cant hear me and i cant hear them.
I then tried to 'upgrade' the ROM using the files on the O2 website, but I encoutered errors during the process. It shows that my ROM is now 1.72WWE but the other programs like fonetik and zip and MMs cant load, and the phone problem still exists.
Please help. Am so desperate!
Solved
All XDA lovers, I found out what was wrong with my XDA2.
It is after all not a software problem, but hardware.
When using the headpiece - which is a pain, it works just fine!
Thank you all for the mutual support!
Hello everyone,
I'm having a problem with the RCD 510 Premium Bluetooth kit that is installed on the new VW Scirocco and its been troubling me for over 2 months now.
When I first got my Scirocco the Bluetooth connection was working fine (for 3-4 months). One day out of a sudden the Touch Pro II was not pairing anymore with the car's bluetooth kit.
At the time I was using Windows Mobile 6.1 that originally came along with the phone. I tried the basics - deleting the connection, re-pairing - with no success.
So I gave a shot at phone's factory reset - still no luck. The phone is recognized when I use the "Device Search" function on the car, it prompts me to enter the pass code provided, I do so, the phone loses the GSM signal (which of course is normal) but then suddenly I get a message on the RCD510's main screen "No bluetooth connection to phone" that lasts for about 2 seconds.
Since the problem began, I tried factory reset the phone (as I mentioned before), and tried pairing before installing even a single software, still no luck.
I tried multiple ROM's in the meanwhile (I mean third-party ROMs from this forum) and now I am using the official Windows Mobile 6.5 from HTC for my phone.
I also did many tests using third-party applications for the rSAP protocol (JetWare hands-free extension, SAPSettings, some patches and drivers found around the net here and there) even though there is native support for rSAP since the first firmware that came along with the device.
As I mentioned before, the phone was pairing fine the first 3-4 months.
Please note that this phone uses the Widcomm Bluetooth Stack - not the Microsoft one.
Any help/ideas would be greatly appreciated.
PS: I apologize for the big length of the post, but I believe the more the information I provide, the more the chances to get proper help
Sorry i cant help you but.. I want your CAR...
Any pics?
Well.. try this
Unhook the cars battery. Let it reset the radio (make sure you have the radio code if any) and try again.. maybe the radio is holding some sort of setting. Resetting to default (like with the device) might do the trick..
.
Thanks for the idea. I'm kind of worried though plugging out the battery, because there are many settings besides the radio that probably will be lost if I do so.
You know all these new cars and their complicated electronic sensors...I don't mind losing minor settings for the car that I have adjusted, my main concern is that if anything goes wrong, I will probably have issues with the car's warranty. I still have 2 and a half years of warranty.
I' will probably have a talk with the dealership before doing that.
Many thanks for your thought though
hi i like to know if pairing went okay with the 6.1 rom because if so maybe when you switch back to this rom problems are solved
Nop
Unfortunately no
It was one of the first things I tried. Switching back to the official 6.1 ROM. I actually kept it saved on my hard disk and I tried it a couple of times - I mean when I tried other ROMs from time to time - hoping it would resolve the issue.
And that's the strange of this case. I mean, it was working (pairing) fine the first couple 3-4 months when I unboxed the phone, and then out of a sudden, no pairing.
First logical thought would be that something has changed in the car's settings. But I have an Athena X7500 that pairs fine with the car up to this day. My car's dealership isn't much of a help...
Second thought - phone settings mess-up. But as stated in my original post, no factory reset helped, no switching to other ROMs, no playing around with settings.....
I'm really desperate. I'm thinking to switch to another phone, but besides this problem I'm quite satisfied with the TP2. And I do "need" Windows Mobile based phones, because I sync with Thunderbird's Lightning via BirdieSync for a long time now, and I am not willing to revert back to the horror days of MS Outlook. I carry my TB profile for over 2 years now and its customized the way it suits me for manipulating my 10+ email accounts.
Thank you very much for your reply though
Any other thoughts/recommendations?
i downloaded firmware 1.20 from volkswagen hope this will help me will try tomorrow with my laptop i am with a touch adapter connected to rns 510 no pairing with tp 2 at the moment for me the only workable solution is a duo sim with my old blackberry bold meanwhile i love he TP2 so hope i can get it to pair with my premium touch adapter volkswagen carkit any other suggestion or solutions are very welcome cheers
And that's the strange of this case. I mean, it was working (pairing) fine the first couple 3-4 months when I unboxed the phone, and then out of a sudden, no pairing.
what radio where you on first couple of months
Nice thought about the radio....but unfortunately I don't remember.
Currently I am using v4.49.25.17 that was upgraded with the latest official HTC firmware of WinMo 6.5 if I am not mistaken.
I am 90% positive though that the problem started before even upgrading, back when I was using the first release of WinMo 6.1 and the unknown version of radio, and everything was working ok at the beginning.
I know, I am not helpful at all but frankly, this problem surprises me as much as you.
You mentioned a firmware upgrade - for the RNS right? Not the RCD....
Do you by any chance happen to know if there is a firmware upgrade for the RCD510 and where can I get it from?
Thanks for your help.
looking-g:
I just realized that you are having a problem with the RNS.
Did you had this all along? I mean, did you ever managed to get it working and then it stopped, or you never had it paired?
I am just asking to see if I can be of any help...
well the problem is not with the rns 510 but with the touch adapter which come delivered as premium carkit i use to pair everything with it blackberry,s nokia,s and also a touch dual (niki) without any problem but now with my new phone the tp2 its not pairing it also never did after i fill in the pincode it gives an error message it should connect with the touch adapter my car by the way is a golf gti mk6 cheers, mark
You kind of lost me there.
What do you mean "touch adapter"? Is this a component of the RNS 510? Because I have never heard of it...
Have you determined a solution?
I just picked up a new VW Jetta with premium bluetooth and it worked the first time and not since.....
You guys are scaring me -- I have an Audi A3 TDI scheduled for delivery in January, and it'd be a bummer if its Bluetooth didn't work. FWIW, my current car has a Sony MEX-BT3700U headunit and the Tilt 2 pairs with it in both handsfree & A2DP modes.
3waygeek: You will be probably fine. I think Audi does not have anything to do with Nokia regarding building their units.
Wish you best luck with that.
Extra info
Some more information regarding the whole subject:
I found out that when I press the "Emergency Call" option on the touch screen of the RCD510 (i.e. try to call the international emergency number - 112) and then immediately end that emergency call, the next time I try to pair the Touch Pro 2, it does pair!!! But it has no signal at all, and if you try to make a call you get a "Dial up error" (or something like that, can't remember exactly)!
Any ideas what could be the reason for that?
Thanks.
Your problem is common to VW/Audi's. Chances are the car kits have the rSAP Bluetooth unit. I had exactly the same issue in my A6 using rSAP, as soon as i upgraded to wm 6.5 the problem went away.
Yes, indeed the car kit uses the rSAP profile, as well as the Phonebook Access Protocol (PBAP), but both of these protocols are supported by the TP2. Actually the rSAP functionality I believe is support in Windows Mobile 6.1 and above - I mean besides the fact that your phone's BT radio must support it in order to work correctly. (Without being entirely sure for the above comment).
And some more info for those who are willing to give an opinion:
I did eventually decided to remove the car's battery. I left the car without battery for approximately 40 minutes. Now here's the strange part: All the settings of the card indeed reset (window settings, light settings, etc) BUT the RCD510 was not affected at all by the battery removal! Yes, as weird as it might sound, the station list was there, bass/tremble customizations were there also, everything in place (regarding the radio unit always).
Side note for all those who might remove the battery from a similar VW car:
As soon as I plugged the battery back on, I had somewhere 15+ warning indicators on my dashboard turned on. From ABS malfunctions, air pressure, EPS malfunctions etc. But after rolling the car for 3m or so everything turned off. Back to normal. Probably had something to do with the electronic sensors giving proper signal to the car's "brain". Just my opinion.
Now, besides that - the fact that removing the battery didn't perform a reset of the radio (RCD510) unit, I also tried reverting my Touch Pro II to a WM 6.1 cooked ROM - don't remember which one exactly - but that didn't helped either. Same stupid error message after pairing for 2 secs: "No bluetooth connection to mobile phone".
And to confirm again: My X7500 (Athena) with a cooked WM6.1 ROM from michy still pairs and works fine. (Tested it last night, just to make sure that battery removal didn't had any side-effects)
PLEASE help me if you can. Any suggestion/recommendation will be greatly appreciated.
PS: I decided to contact the car's dealership to inform them about the whole problem. I will post soon regarding how that went...
Thanks for your time everyone...
By the way, does anyone knows the proper way to reset the RCD 510 to it's factory default settings? Besides the function that is given inside the menu itself - I already tried that. I was just wondering if there was a "hidden" way that will entirely wipe all settings/customizations from the unit....
Hi guys! I m in the same situation: Sirocco + TP2 with 6.5 from Orange. Any progress from your side? Ideas would be greatly appreciated!! Cheers, P
Unfortunately!
No friend, sorry. No news yet.
I do keep the post open hoping that someone will give me a new year's present
It's nice to know that I am not alone though
I just picked up a Note II from Sprint and it had 4.1 on it. I connected it to my Jeep Wrangler (2012 Unlimited) UConnect Radio (Model 130) and everything worked great when making a phone call. (I first this last friday tried a Note 3, but that wouldn't make calls at all from my jeep and Sprint said that they know and it might never be compatible, so I had to return it and swapped it out for the Note II on monday.)
The phone then upgraded to Android 4.3. Now I have a unique Bluetooth issue that I have exhausted searching for an answer to but cannot find one.
The phone will answer calls just fine through the UConnect radio, and it will make calls to some people just fine through the bluetooth. But when I call some people it will ring thought the speakers just fine, and then when they answer the UConnect radio announces "Call Ended." However the person is still connected and it still shows the bluetooth connected just fine in my action/notification bar and the headset button in the call is still highlighted green. But I have to hit the speaker button to speak top the people at that point. Again, this doesnt happen on every call so thats why I am confused.
I have found a solution however, and this is where I need the help of one of the superusers on here. (To preface this, I have read about 150 posts online about the Note 2 and bluetooth issues. I have deleted and repaired the phone from the Jeep UConnect and removed the Uconnect from the phone about 20 times. I have tried Bluetooth Auto connect, I have tried Tasker, I have tried disabling the media audio option, IU have tried bth allowing MAP and not allowing MAP. I have tried both allowing the phonebook and call history download and tried not allowing it. I have called Sprint...NO HELP, and I have called Jeep...NO HELP. Both Sprint and Jeep told me there were no firmware updates available to fix this (Jeep said they cant do firmware updates on my radio) and Sprint said there were no plans to fix this kind of bug in the future)
When the UConnect announces "Call Ended", I can drag down my top action/notification bar, click on the gear for settings, click on Bluetooth, then click on the UConnect gear for settings, uncheck the "Call audio Use for phone audio", and then re check it. Once this has been rechecked, the Uconnect picks back up the audio just fine and I can continue the call on the radio handsfree like it is supposed to be.
I live in CA where is is required to be handsfree so I really need a solution to not fumble with the phone for 10 seconds trying to make it do what it should do automatically. (Like my 4 year old Galaxy S2 did just fine).
I have tried tasker but cant seem to find a way to make it perform those steps I need.
My big question then is this... Is there an app or someone that knows how to write a simple app that would simply disable then re-enable the call audio checkbox under the Uconnect settings with the press of one button. or the press of an app icon from the home screen or something. Or has anyone seen this and knows of a fix?
Sorry for being long winded, just want to make sure the problem is clearly explained. I am truly at my wits end.
Thanks in advance for any help you can give, it is greatly appreciated.
So couple questions. Are you pure stock, got root, custom recovery?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Sorry, guess I forgot that part.
I am pure Stock Sprint (Afriad to try a rom yet since my friend bricked his Note II)
Android Version 4.3
Android Model SPH-L900
Build JSS15J.L900VPUBMK4
Hardware Version L900.09
Kernel version 3.0.31-2106854
Hi guys,
I am experiencing a bug on my Swift where the phone reboots itself during almost all calls after a minute or so. When the phone comes back on, there is no record of the call in the call log! The phone does not reboot during any other activities. Phone details below:
Wileyfox Swift
Cyanogen OS 12.1.1-YOG7DAS2FI
Kernel version 3.10.49
Build Number LMY48Y
I have checked for another similar thread without any luck. Thanks!
I have a similar,though not identical issue. Phone keeps rebooting,seemingly at random,every other day or so. During a call, listening to spotify,idle on the desk...i have an untampered with original Os on the phone.
Cheers,
Me too.
Hi, I just registered to say I'm having the same problem. If you check the Amazon UK reviews too there are several people with this rebooting problem.
So far I have:
- uninstalled all additional apps I installed
- tried it with wifi and data off
- tried the other SIM slot
- done a factory reset
and it still reboots during calls. After the factory reset things appeared to work better in general (alarms now worked properly, and there were more options available, eg in the power button menu), but it rebooted 5 seconds into a phone call, which is a record. It's usually a few minutes into it.
The factory reset didn't actually delete my data (photos, files, etc), so I am going to do a reinstall via Fastboot now; firstly because I'll have to do that I guess if I want to send it back, and secondly to see if it finally fixes it.
I personally think the update process has screwed something up. It did an update as soon as it was powered on for the first time (it to 12.1), then a couple of weeks ago did another update to 12.1.1. It was rebooting before 12.1.1, so it is either 12.1 or earlier where the problem exists.
If it still reboots after a Fastboot reinstall then it's getting send back, and I probably won't ask for another. It's a nice phone, and a nice idea but I can't have a phone that reboots during >50% of calls. That's useless.
Pretty sure you can discount the update process too! I have also had this issue on cyanogenmod nightlies, I honestly thought I had inadvertently pushed the power button..but, NO
*edit* CM13 nightlies
That's strange as I have had no such problem with mine (bought in October) and mine is rooted with the unofficial builds of CM13... Maybe it is a manufacturing error and only on some devices...
Have you tried contacting Wileyfox?
I have not experienced this yet on the Swift when making or taking calls on it.
i'm on the latest cm13 nightly for crackling. each and every time the phone is called, whichever sim, the phone reboots. what a waste...
I have the same issue of spontaneous reboots, mostly during calls but also at other times. Spoke to Wileyfox who weren't very helpful. Has anyone found a solution for this?
Hi, I'm having the very same issue (appears a few are on other forums). Has anyone found a solution? I'm about to factory reset if it continues
Update
Hi guys, so i returned my phone for repair, and they gave me a new phone. Must have been a hardware fault I assume
enzoparker said:
Hi guys, so i returned my phone for repair, and they gave me a new phone. Must have been a hardware fault I assume
Click to expand...
Click to collapse
Hi thanks for the update, I've just factory reset, if problem persists I'll try to get a replacement too! Was it quite a quick replacement process?
R
I'm in South Africa and have the same problem. Whenever sound is involved, I get random reboots. Calls, and music/audio books.
Not with videos though.
It doesn't reset any other time except when I've been listening to music, or on a call.
Been doing this from the beginning.
I thought it was Google Play Music, so downloaded different player.. That made it much less frequent, but then it started affecting my calls as well.
Not happy.
Hi, UK user here. I got this phone less than a week ago and have already had this issue a few times. Two spontaneous reboots on resuming from sleep, being connected to a large WiFi network was the only change from normal use here; then twice regarding calls, once when answering then immediately after reboot it rebooted again while the missed call notification was present, although still on the aforementioned large WiFi network. Unmodified, unrooted, Cyanogen OS 6.0.1 with two sims in use.
Same issue on my a1g2.
It reboots on wf swift Roms. It stucks in call screen on a1g2 stock rom. Strange...
i am having same issue, i make any call and mobile Soft Reboots itself.
So, much annoying cannot make a single call on this WileyFox Swift mobile phone.
Making calls is the main basic purpose of every mobile, but this phone just does not let me make a single call.
.Had this issue on Cyanogen OS 5.1. Now updated to Cynogen OS 6.0.1 having same issue. I have done phone setting HARD RESET and Clean Wipe 2-3 times. Still no solution.
DevilMind007 said:
i am having same issue, i make any call and mobile Soft Reboots itself.
So, much annoying cannot make a single call on this WileyFox Swift mobile phone.
Making calls is the main basic purpose of every mobile, but this phone just does not let me make a single call.
.Had this issue on Cyanogen OS 5.1. Now updated to Cynogen OS 6.0.1 having same issue. I have done phone setting HARD RESET and Clean Wipe 2-3 times. Still no solution.
Click to expand...
Click to collapse
Maybe it's the Dialer in Cyanogen OS, i installed the Google Dialer and made it default Dialer on my Swift, i don't have any problems with reboots during calls and i make long phonecalls. You don't need root access for this.
Although Wileyfox accept that there is a grounds for returns, I believe it is a software bug in Cyanogen OS 13. This fits in with using another dialler. You could also downgrade, or switch to Cyanogenmod.
Also, I only have found the issue when receiving calls, rather than making them, although I don't use a lot of minutes.
Sent bug reports to Wileyfox.. They're saying that what they see is a battery-pull reboot..
I tell them it's happening while I'm using the phone (music or calls)..
They say they can't see what the issue is.
Cos I'm in South Africa, sending the phone overseas is pointless.
Can anyone confirm that the Google dialer does cure a phone that does the reboots during calls ?
Just got a replacement swift from Amazon after Wilyefox service department had my phone since 16th of June. Amazon argued my case and in the end just sent one to me. !
Set phone up on wifi for my wife to use then put in the Voda UK sim, checked the APN setting were OK then tried making a few calls between our phones. first reboot was after 20 seconds or so and then after various tests it rebooted 4 or 5 times at which point I gave up for the night..
Any help appreciated or do I just give up now and throw in the towel, bought original swift in late May and never managed to make it work properly !!
Thanks
phil-w said:
Can anyone confirm that the Google dialer does cure a phone that does the reboots during calls ?
Just got a replacement swift from Amazon after Wilyefox service department had my phone since 16th of June. Amazon argued my case and in the end just sent one to me. !
Set phone up on wifi for my wife to use then put in the Voda UK sim, checked the APN setting were OK then tried making a few calls between our phones. first reboot was after 20 seconds or so and then after various tests it rebooted 4 or 5 times at which point I gave up for the night..
Any help appreciated or do I just give up now and throw in the towel, bought original swift in late May and never managed to make it work properly !!
Thanks
Click to expand...
Click to collapse
Well I've given up !!!
A second Swift was supplied with the help of a Amazon Rep.
We even got a £25 Amazon gift card from Wileyfox direct for all the trouble !
Set phone up on wifi, added all apps required by my wife. Put Vodafone SIM in and ...... Shutting down message.
Restarted phone and it did it a few more times. Ordered a replacement 4G SIM in case there was a problem with the 3G SIM we had. Activated new SIM and fitted it, worked for ten minutes then rebooted itself.
SIM is fine in any other phones I've tried.
Just about to return phone to Amazon, checked and my original swift is still sat with the engineer (since 16th June !!) according to the repair company website.
I feel sorry for anyone wanting their phones repairing after what I've been through.
---------- Post added at 07:07 PM ---------- Previous post was at 07:05 PM ----------
phil-w said:
Can anyone confirm that the Google dialer does cure a phone that does the reboots during calls ?
Just got a replacement swift from Amazon after Wilyefox service department had my phone since 16th of June. Amazon argued my case and in the end just sent one to me. !
Set phone up on wifi for my wife to use then put in the Voda UK sim, checked the APN setting were OK then tried making a few calls between our phones. first reboot was after 20 seconds or so and then after various tests it rebooted 4 or 5 times at which point I gave up for the night..
Any help appreciated or do I just give up now and throw in the towel, bought original swift in late May and never managed to make it work properly !!
Thanks
Click to expand...
Click to collapse
Well I've given up !!!
A second Swift was supplied with the help of a Amazon Rep.
We even got a £25 Amazon gift card from Wileyfox direct for all the trouble !
Set phone up on wifi, added all apps required by my wife. Put Vodafone SIM in and ...... Shutting down message.
Restarted phone and it did it a few more times. Ordered a replacement 4G SIM in case there was a problem with the 3G SIM we had. Activated new SIM and fitted it, worked for ten minutes then rebooted itself.
SIM is fine in any other phones I've tried.
Just about to return phone to Amazon, checked and my original swift is still sat with the engineer (since 16th June !!) according to the repair company website.
I feel sorry for anyone wanting their phones repairing after what I've been through.
Hi,
I've got a strange problem when trying to use Skype for Buisness.
When on call with somebody, I loose sound after 10-15 sec, or sometimes even instantly. The other person is hearing me good all the time, and if someone is presenting files I can still see them moving.
When I connect to WiFi, or share hotspot from another phone it works without problems...
My carrier is Orange, and there were no problems with it on my older phones, S7edge, and Xiaomi - Skype worked allright.
Please help.
EDIT:
It was the same on Oreo, and now on Pie.