Related
Hi all,
I've just recently upgraded to the above ROM- everything else seems to be fine but I've just realised that the 'Settings' for BT are slightly different to my original rom version.
I can pair the JAM fine with the PC but it won't let me connect. As I look at the BT settings, I can see the following tabs: Mode, Devices and COM Ports; it's the COM ports that has changed. It's got New Outgoing Port and New Incoming Port. When i select either of these I can't assign any port number; the drop down list is blank.
P.S. I was able to connect fine via BT using my original ROM v1.00 or something.
Any help appreciated.
Thanks.
hey man
i just posted another querry regarding the card reader ...
hope u read it !!
getting back to yr problem
follow the instructions on this link and yr problem will be solved (HOPEFULLY)
http://howardforums.com/showthread.php?t=544932
I remember reading that link a while ago but I got the BT working without Pocket Tools software...
Anyway, I've tried both versions from the website but after installing either of them, the connect via bluetooth in Tools of ActiveSync is not there; just the IR. As soon as I uninstall the software it's back there.
I thought I had mastered the myth of Jam and Bluetooth- looks like back to square one!
Sorry - I'm just impatient- reinstalled and re-paired a few times and all is fine now.
Thanks for your help.
reinstalled what may i ask? im having this exact problem at the mo
Instructions from the top of my head (excuse any errors)
1) I removed the Pocket Bluetooth tools from remove programs
2) Perform soft reset and remove any existing paired devices
3) Reinstall the Bluetooth Tools (i used the an earlier version)
4) Select ActiveSync check box
5) The device should be paired
6) Go to to ActiveSync on PPC; go to tools and you should see Connect BT with ***
This should work.
Hi
I am new here and i have problem
When i turn on my qtek9000, i recieve message Serial V.100.
If i connect USB cable it displays USB instead of Serial.
This happened when i tried to do radio upgrade (through usb hub, sim and sd were also in phone...).
I have 1gb SD card and also card reader mounted in laptop, so transfering files should not be problem.
Can someone help me with step-by-step procedure how to make my qtek work back. I used a lot of search but i am even more confused....
I just remember that when qtek worked Radio was something like 1.0.3.1 and also WWE was writen somewhere....
Probably i should put rom to sd with ntrw (which wersion of both),.......
please help....
might be a dumb question on my part - but have you tried a reset (initially a soft one but then a hard one of course, if nothing else works...) ???
I mean you will at least be able to revert back to the condition 'out of the package'...
Hope everything works out!
jup.both things NOT HELPED
looks like you're stuck in the bootloader mode....
try flashing the rom & the radio rom once again by connecting it to your laptop's usb...
i guess something screwed up while you were upgraging your radio rom...and you'd need to redo it!
Best,
San
can you please write me a procedure?
You might want to check the following thread. Everything is well described.
Cheers
hrb
http://forum.xda-developers.com/viewtopic.php?t=32725
i am trying to download files but i get permission denied all the time
You mean you get an error when clicking this link ?
ftp://xdaupload:[email protected]/Universal
I don't understand that, it works perfectly well for me
Cheers
hrb
I have solved problem with Radio upgrade. I am in much better mood now. 8)
Anyway i have 4 more questions.
1.) I am using bluetooth car-instalation Parrot CK3100. I am wondering if is possible to transfer any other sound except telephone conversations to that device. When i had Nokia 9500 i was able to hear every single click,tone,...i made on phone also on car-instalation. I also heard nokia ringtone in car instalation.With qtek i am getting generic car-instalation ringing tone instead of phone ringing. Otherwise primary intention (hands free talking) works fine. I would like to have that to be able to hear voices from various GPS software.
2.) Since QTEK9000 is PDA and phone in single unit I would like to have in car GPS application "always on top". Like previously mentioned i can easily manage my calls with car-instalation. Therefore i would like to run Phone section in background or GPS applications on top.I hope you will understand what i would like to say
3.) I also need in-car holder for qtek. Do you have any reccomendations?
4.)
My settings:
R: 1.04.02
G: 42.37.P8
D: 1.13.64.WWE
Is that ok or should i upgrade?
Stuck in bootloader mode
Hi guys,
Got stuck in bootloader mode following an upgrade attempt. Tried to reflash radio using the files from the pload folder only to get an error saying it's for the wrong device - tried this several times with the same result.
any ideas?
Is there a binary and a tool I can just do a straight upload?
thanks
Re: Stuck in bootloader mode
Bauser_uk said:
Hi guys,
Got stuck in bootloader mode following an upgrade attempt. Tried to reflash radio using the files from the pload folder only to get an error saying it's for the wrong device - tried this several times with the same result.
any ideas?
Is there a binary and a tool I can just do a straight upload?
thanks
Click to expand...
Click to collapse
try it with this file -
1. put radio.nbf and the file attached below in the same folder and run the exe with ur device connected to usb in bootloader mode...
2. hope it flashes it
S
Thanks DreamTheater
Thanks for your help - unfortunately I got the same message, ie this rom is not meant for this device etc...
Will see O2 can do anything (who's that laughing...???) - was going to buy a new xda mini anyway...!
1. REMOVE your SD/MMC card.
2. Soft/hard reset.
3. Run the upgarde again.
Step 1 above solved my problem.
Hi there. Thanks to everybody for answers.
I just have got some DVP from USA (not new). Its in good cond. Unfortunatelly unusable It cannot see sd card. System info says 15MB free. Service menu (##634#) says SD card 8GB inserted but unusable.
But the main problem is, that ZUNE (and win7 as well) dont see the phone - win7 dont recognize it and its marked as UNKNOWN device with pid USB\VID_045E&PID_04EC . I tried find proper driver on inet, tried search in zune directory, tried update zune... nothing helps.
Firmware is 2250.1500.7004.105
carrier:TMO-US
revision: 112.576.2.0 OS
OS: 7.0.7004.0
So i think its basic firmware. My first idea was, that i havent original DELL data cable (using ericsson). BUT when i connect phone in recovery mode, its recognized properly by windows mobile recovery SW. (but that sw says this device cannot be recovered blabla So i think cable is good (all data cables i guess are the same) I tried update firmware via wifi - it says no update available.
Is there ANY OTHER WAY to UPDATE FW ? (without zune)?
Is there any way how to find right drivers for it?
SD card problem can be solved by new sdcard, maybe. But i need some FW uodate, in this satus is phone unusable - restarts, it dont keep my settings after restart, and many other troubles.
Thank you for your hints !!
Regards Gisbern
just call in for a replacement they will send you a device with 212. They wont make you send your current device until after you receive the replacement at which point you just put it in the box they sent your replacement in, seal it back up, put the label they gave, and call fedex for a pickup. Takes about 3 days for the replacement to arrive although the last replacement I received I got in 2 days.
No warranty
Hi, thank you for reply. It was the answer i didnt want to hear )) For my phone service tag is no warranty in dell pages. Of course i can pay for repair, but the question is, how much ? Anybody know +/- price for such type of repair?
Secondly im from EU, so shipping to usa will be little bit higher (but not killing).
Thats way im asking for some alternative method of flashing FW. (without zune)
Regards Pete
I know this thread is ancient. But I post a solution anyway, for other people who have this problem and find this with google.
The solution is easier than you might think: in device manager right-click the device and choose "update driver". Let windows search for drivers and it will install the proper drivers. Done!
Ciao,
Heathcliff74
I'm using the NexusHD2-ICS-4.0.4-CM9-HWA v2.0 ROM on my HTC HD2. But since i've switched to ICS my car kit doesn't recognize my phone anymore.
I have a Volkswagen Passat with a RNS315 navigation system and Bluetooth Premium.
I could connect my phone to my carkit by installing Gingerbread, pairing the phone and install ICS, but since v2.1 and higher my carkit doesn't find the phone anymore (probably because the MAC address for bluetooth has changed). When I make the phone visible and do a search for mobile phones I get the message that no compatible phone has been found. Though it does still recognize the phone as a Media Player. Does anyone has any ideas to make this work? Especially v2.3 of the NexusHD ROM is really interesting now since mute is working!
Thanks in advance.
Regards,
Patrick
Starting from ICS, Android no longer supports rSAP protocol (only HFP). Your car kit probably does not support HFP protocol and this is why it is not finding the phone.
Thankfully, there is an app on play store that adds the support back.
First install "Bluetooth SIM Access Install", then "Bluetooth SIM Access (Trial)" or Full version (paid). You can also see instructions on their website: http://www.android-rsap.com
After installing the trial version, my Skoda GSM II car kit (probably same as yours VW) finally recognized HD2 with Paranoid 1.1a ROM.
Maybe you could drive to the nearest dealer, and ask for an update of your carkit system. It would be pretty lame if VW doesn't support Android 4.0.
I'll try to connect the phone using the rsap app. The weird thing is that once it's paired using Gingerbread and then installing Android 4, it still connects. (With the older ROM version though, not with the newer anymore). I don't know if it is the ROM, or if it is ICS.
So I'll try to connect using rsap, and if that doesn't work I'll visit the dealer. Thanks for your replies. I'll let you know the outcome.
I've installed the rSAP app on my phone. Now the carkit indicates I have a premium Bluetooth connection and I get additional functionality. But if I try to find the phone it still indicates that no compatible phone can be found. It must be something else. I'll call the dealer to ask if they have an update..
Btw, I've found the following note in the ROM thread, so I guess it's a general problem: http://forum.xda-developers.com/showthread.php?p=27533851&highlight=vw#post27533851
Have you tried to find the car kit from the phone? This is what I did and it worked for me.
In order to do it I had to first make the car kit discoverable. It was only possible when I've connected another Android 2.2 phone, then the car kit showed an additional menu item to set BT visibility. Then I was able to find it on my HD2 and make a pair.
Sqter said:
Have you tried to find the car kit from the phone? This is what I did and it worked for me.
In order to do it I had to first make the car kit discoverable. It was only possible when I've connected another Android 2.2 phone, then the car kit showed an additional menu item to set BT visibility. Then I was able to find it on my HD2 and make a pair.
Click to expand...
Click to collapse
Hi Sqter,
Yes, I've tried that. I can pair with my carkit then, but it will only see the phone as Media Player, not as phone.
In two weeks I will go to the garage for a software update, hope that it will bring some solution. The current ROM i use (NexusHD2-ICS-CM9-HWA V2.0) works with the carkit, but as soon as I upgrade to a later version ([9.Jun.2012] NexusHD2-ICS-4.0.4-CM9-HWA V2.3), the carkit stops recognizing the phone as a phone..
When I read it the ROM's thread that the phone bluetooth doesn't manifest itself as phone, I think that's a good possibility and I hope that Tytung has time to look into that.
I found the following:
Thanks for this great ROM. However after a clean install of the latest version (I was using version 2.0 before) I could not connect my phone to my Skoda Amundsen carkit. It only recognises the phone as mediaplayer but not as a phone. After searching the internet for a solution I found the following:
The bluetooth configuration is written by ICS in /data/misc/bluetoothd/<device MAC>/config
When you replace the line "class 0x5a0000" by "class 0x5a020c" with a root shell, and rebooted the phone the phone is recognized as a phone.
After applying this setting I found my phone could indeed connect to the carkit and everything works fine.Could you please replace the bluetooth config file in new versions of your ROM?
This works for me!!!!!
I used the terminal emulator. Typed in "su" to get super user access browsed to the directory and edited the file with vi. (vi -> e, browse to line, adjust class to 0x5a020c -> ESC -> :wq. Rebooted the phone. Now the carkit does recognize the phone.
Thanks for your finding. I will also try it out - it seems to be easier solution than the one I had found.
Workaround
Try to edit /data/misc/bluetoothd/<device MAC>/config and replace the line "class 0x5a0000" by "class 0x5a020c" with a root shell
Reboot and enjoy!
This file is generated by ICS at the first boot , but i do note know how...
Workaround
patrickvdw said:
I found the following:
Thanks for this great ROM. However after a clean install of the latest version (I was using version 2.0 before) I could not connect my phone to my Skoda Amundsen carkit. It only recognises the phone as mediaplayer but not as a phone. After searching the internet for a solution I found the following:
The bluetooth configuration is written by ICS in /data/misc/bluetoothd/<device MAC>/config
When you replace the line "class 0x5a0000" by "class 0x5a020c" with a root shell, and rebooted the phone the phone is recognized as a phone.
After applying this setting I found my phone could indeed connect to the carkit and everything works fine.Could you please replace the bluetooth config file in new versions of your ROM?
This works for me!!!!!
I used the terminal emulator. Typed in "su" to get super user access browsed to the directory and edited the file with vi. (vi -> e, browse to line, adjust class to 0x5a020c -> ESC -> :wq. Rebooted the phone. Now the carkit does recognize the phone.
Click to expand...
Click to collapse
I think you found my post on forum.android-rsap.com/viewtopic.php?f=10&t=347&start=20
patrickvdw said:
I found the following:
Thanks for this great ROM. However after a clean install of the latest version (I was using version 2.0 before) I could not connect my phone to my Skoda Amundsen carkit. It only recognises the phone as mediaplayer but not as a phone. After searching the internet for a solution I found the following:
The bluetooth configuration is written by ICS in /data/misc/bluetoothd/<device MAC>/config
When you replace the line "class 0x5a0000" by "class 0x5a020c" with a root shell, and rebooted the phone the phone is recognized as a phone.
After applying this setting I found my phone could indeed connect to the carkit and everything works fine.Could you please replace the bluetooth config file in new versions of your ROM?
This works for me!!!!!
I used the terminal emulator. Typed in "su" to get super user access browsed to the directory and edited the file with vi. (vi -> e, browse to line, adjust class to 0x5a020c -> ESC -> :wq. Rebooted the phone. Now the carkit does recognize the phone.
Click to expand...
Click to collapse
Worked for me! Thank you very much, was desperately searching for a solution for hours now.
Hello from France,
I just bought a KC BX-411 Android 6.0 head unit on aliexpress, I found the manufacturer with the name , it is a KC Cartech product www_kccartech_com/eacp_view.asp?id=226 , I’m very happy with it except that I can not pair my OBDLink LX OBD adapter.
No problem with bluetooth to connect a phone and it works, the only problem is for the obd adapter, only one chinese model of a friend is working and it have to be named "OBDII" and have MAC Address (identity card) : AA:BB:CC:11:22:33 , it is the generic chinese typical OBD but the problem is that mine has a different name and obviously another MAC Address and the car radio can't pair it (see video) , It seems that the firmware of the car radio is locked to use only a generic chinese "OBDII" with MAC Address : AA:BB:CC:11:22:33. It has been confirmed by a friend who have a android car radio too with same problem and had to replace the original firmware by a sda developer firmware update to solve the problem.
Do you have a firmware update to upload in the car radio to replace mine to be able to connect any OBD adapter ?
ANTUTU Benchemark v6.2.7 (Score 19695):
CPU Allwinner T3 Cortext A7 Quad Core 1.2GHz
RAM DDR3 1GB INAND 16GB
Android 6.0.1 (32bits) SDK 23
Renderer Mali-400 MP2
GPU OpenGL ES 2.0
screen 800x480 (240dpi)
RAM 752MB
HDD 3,87GB
HDD 7,51GB
Thanks,
PIFOUBMW
Same problem as well...
Were you able to find ny solution to this?
No
From OBDLink support Forums:
You can try renaming your OBDLink with the command STBTDN.
Once connected, you can issue the command "STBTDN OBD". You will then have to power cycle the unit. Once it powers up the device should now broadcast as "OBD".
You can also try changing the Class of Device with the command STBTCOD.
Once connected, you can issue the command "STBTCOD 200400". You will then have to power cycle the unit.
Hi,
Do you have a link to that or to instructions on how to send the command to the OBDLink LX?
Thanks.
marchnz said:
From OBDLink support Forums:
You can try renaming your OBDLink with the command STBTDN.
Once connected, you can issue the command "STBTDN OBD". You will then have to power cycle the unit. Once it powers up the device should now broadcast as "OBD".
You can also try changing the Class of Device with the command STBTCOD.
Once connected, you can issue the command "STBTCOD 200400". You will then have to power cycle the unit.
Click to expand...
Click to collapse
PIFOUBMW said:
Hello from France,
I just bought a KC BX-411 Android 6.0 head unit on aliexpress, I found the manufacturer with the name , it is a KC Cartech product www_kccartech_com/eacp_view.asp?id=226 , I’m very happy with it except that I can not pair my OBDLink LX OBD adapter.
No problem with bluetooth to connect a phone and it works, the only problem is for the obd adapter, only one chinese model of a friend is working and it have to be named "OBDII" and have MAC Address (identity card) : AA:BB:CC:11:22:33 , it is the generic chinese typical OBD but the problem is that mine has a different name and obviously another MAC Address and the car radio can't pair it (see video) , It seems that the firmware of the car radio is locked to use only a generic chinese "OBDII" with MAC Address : AA:BB:CC:11:22:33. It has been confirmed by a friend who have a android car radio too with same problem and had to replace the original firmware by a sda developer firmware update to solve the problem.
Do you have a firmware update to upload in the car radio to replace mine to be able to connect any OBD adapter ?
ANTUTU Benchemark v6.2.7 (Score 19695):
CPU Allwinner T3 Cortext A7 Quad Core 1.2GHz
RAM DDR3 1GB INAND 16GB
Android 6.0.1 (32bits) SDK 23
Renderer Mali-400 MP2
GPU OpenGL ES 2.0
screen 800x480 (240dpi)
RAM 752MB
HDD 3,87GB
HDD 7,51GB
Thanks,
PIFOUBMW
Click to expand...
Click to collapse
I have the same issue, I found that the issue is with the Bluetooth Module (Chip) itself.
You need to check the Bluetooth Module# manually. If you have bluetooth module RDA 5850SM then you need to go through this process CLICK HERE (Credits @****-jones )
rizu3544 said:
I have the same issue, I found that the issue is with the Bluetooth Module (Chip) itself.
You need to check the Bluetooth Module# manually. If you have bluetooth module RDA 5850SM then you need to go through this process CLICK HERE (Credits @****-jones )
Click to expand...
Click to collapse
hello,
do you know where i can find the files of the russian forum (goc.rar)?
it seems that the link is dead
thnk you
nirudha said:
Hi,
Do you have a link to that or to instructions on how to send the command to the OBDLink LX?
Thanks.
Click to expand...
Click to collapse
I know this is old but I just got my OBDLink mx to work with the android head unit
You need to change the class of device to 001f00.
You can follow this instructions here. I had to use my laptop to make the changes with obdwiz and then power cycle the OBDLink mx.
https://www.scantool.net/forum/index.php?topic=15863.0