Recently updated from ICS 4.0.4 to JB 4.1.2 and since then my car won't connect to the phone with bluetooth. Error on car display says the phone is not compatible.
I've reflashed the bluetooth.zip, and have reflashed ROM to make sure nothing wrong there. Did reset/wipe, and dalvik, and cache partition. Phone has been rooted all the time. I've tried the rSAP install system files tool from the market which made no difference unfortunately. Also tried the trial version of bluetooth SIM access which didn't work.
Car radio is the VAG premium RNS510 unit.
Any thoughts or suggestions?
i9100
AOKP-CM10
Thanks,
Related
Hi Guys,
I got a HM1000(Smaung) bluetooth headset.My galaxy S2 came with KF3(I am located in India).
After that i tried non wipe ROM like Litepro4.2 and it was working.
Then i decided to get brave and tried a host of other WIPE ROMS like Batista,MIUI,CheckROM but my bluetooth HS would not be recognized. Other bluetooth services are okay
Currently I have fallen back to LitePro in which it works again(Restored from backup in CWM). Am i missing something?what is the issue here?
PS: I tried to get back to KF3 (had to wipe otherwise bootloop) and it still does not work after wipe.
Hi all,
I use a GPS Receiver (qStarz 818XT) and Trackmaster App with my Galaxy S2 whilst doing trackdays.
Previously running 2.3.3, 2.3.4 & 2.3.5 the system worked perfectly.
Having upgraded to 4.0.3 (XWLP7 stock) I found that as soon as the phone locked itself (screen off) the software stopped logging/receiving. If I keep the screen on all is fine. Now unfortunately on a motorcycle trackday my phone gets locked and put in my pocket.
Having reverted back to 2.3.5 (XWKJ1) the App / GPS Receiver works perfectly, as intended with the screen locked, continuing to log data.
Is this a known Bluetooth problem with 4.0.3 dropping out? Any solutions?
Many thanks all.
cptmorgans said:
Hi all,
I use a GPS Receiver (qStarz 818XT) and Trackmaster App with my Galaxy S2 whilst doing trackdays.
Previously running 2.3.3, 2.3.4 & 2.3.5 the system worked perfectly.
Having upgraded to 4.0.3 (XWLP7 stock) I found that as soon as the phone locked itself (screen off) the software stopped logging/receiving. If I keep the screen on all is fine. Now unfortunately on a motorcycle trackday my phone gets locked and put in my pocket.
Having reverted back to 2.3.5 (XWKJ1) the App / GPS Receiver works perfectly, as intended with the screen locked, continuing to log data.
Is this a known Bluetooth problem with 4.0.3 dropping out? Any solutions?
Many thanks all.
Click to expand...
Click to collapse
It is not a known bug ... for me.
Maybe you should try some of the newer ICS ROMs, such as XWLPD or XWLPF.
Official Firmware thread is here => http://forum.xda-developers.com/showthread.php?t=1075278
Try to wipe cache partition (and Dalvik cache) after flashing ICS.
If that does not help, you may have to do a factory reset.
So, please make a backup before !
Good luck !
Hi,
You can try my app "Bluetooth Keepalive" from the market, it automatically prevents android standby when being connected via bluetooth.
Regards
...Alex
My friend asked me to look at this phone that was softbricked and kept going to CWM recovery everytime it was booted. I updated the CWM to the latest touch version via ODIN then formatted the phone clean. :good: Then I flashed 4.3.1 stable AOKP ROM and the GApps. It was fine, everything else was working. I connected the wi-fi, used bluetooth, signed into google account everything was normal and stable.:highfive: But then I tried calling and it said "no mobile network". Tried sending a text, could not. I went in and searched for network signals then registered to the correct(I AM SURE!) one.:silly: Still no luck. Then I let it choose automatically. Nothing. Then I thought maybe installing another ROM will somehow fix it and flashed CyanogenMod 10.2 stable. Still no luck. I searched around for a flashable radio but could not decide if that would fix it because as far as I am aware if the radio wasn't working no wireless connectivity should've been either.
The phone is Samsung Galaxy S III GTI9300 white 16GB (unlocked) and has been here in Nepal with Nepal Telecom Sim since it was bought. I have no Idea how the soft brick happened but I think this guy tried to manually update the phone with a stock firmware during which some **** must've happened.
Can you guys please let me know if this could be fixed?
Any help would be highly appreciated.:fingers-crossed::fingers-crossed:
There are hundreds of identical threads, search and read about efs and imei issues.
Sent from my GT-I9300 using Tapatalk
I just purchased this device using swappa, I actually received the device as of today...I do not have a sim card in it, yes it's rooted...Im currently using a stock JB rom 4.0.4 (have no idea which one)...Here's my problem, it's not connecting to any open SSIDs, I have tried atleast 3 or 4 different ones around my town. Its not connecting, just continues to say saved...I have no tried connecting to any secured SSIDs yet because I dont have wifi at my house. I dont think it's a problem of not having a sim card...Im new to this device and this is the first time Ive ran across this problem. Its not my first android phone, Ive been around for a while...Just trying to get some experienced help from some other users with the same phone. It might also help to tell you that I have shut the phone down and restarted. That did nothing....So has anyone had any kind of problems connecting to any open SSIDs using a stock JB 4.0.4 rom ?
JDRhodes28 said:
I just purchased this device using swappa, I actually received the device as of today...I do not have a sim card in it, yes it's rooted...Im currently using a stock JB rom 4.0.4 (have no idea which one)...Here's my problem, it's not connecting to any open SSIDs, I have tried atleast 3 or 4 different ones around my town. Its not connecting, just continues to say saved...I have no tried connecting to any secured SSIDs yet because I dont have wifi at my house. I dont think it's a problem of not having a sim card...Im new to this device and this is the first time Ive ran across this problem. Its not my first android phone, Ive been around for a while...Just trying to get some experienced help from some other users with the same phone. It might also help to tell you that I have shut the phone down and restarted. That did nothing....So has anyone had any kind of problems connecting to any open SSIDs using a stock JB 4.0.4 rom ?
Click to expand...
Click to collapse
4.0.4 is ICS not jb. You can try flashing the appropriate radio. Since you dont know the history of the device LGNPST is a option, so that you have a fresh start with partitions updated and a working recovery. Here is the link for LGNPST http://forum.xda-developers.com/showthread.php?t=2230994
And here are the radios http://forum.xda-developers.com/showthread.php?t=2270319
If it's on 4.0.4, that's ICS, and if its rooted, it's possible that the JB radio was installed, which could be a problem, because WiFi only works on ICS with the ICS radio, the JB Radio breaks wifi on ICS; also, teh ICS radio breaks wifi on JB.
I'd recommend either flashing a more up-to-date rom, or flash the ICS radio.
Problem was fixed with up to date rom
Sent from my LG-E970 using XDA Premium 4 mobile app
Ok so I bought a second hand s2 on a stock firmware then I flashed it with cyanogenmod 9. I then bought a mhl to HDMI cable and upon further info found out that cyanogenmod don't support mhl and apparently I needed a touchwiz rom, so I flashed a rom called chameleon and Viola my cable worked. I then looked into the multiwindow feature and decided to move to a rom with mhl and multiwindow support so I chose a rom called alliance rom. Everything seemed fine and then my data wasn't working for some reason, so I contacted my carrier (giffgaff) and they said they have blocked my data as the IMIE I have has been used before on multiple accounts for data abuse, I explained I have not done this but they said they would not remove the bar. I thought something was odd about this and upon further inspection I realised since I flashed my s2 my IMIE has changed to a weird 0049 number, I looked this up on Google and it says that this IMIE is a generic one and is caused by flashing sometimes. A lot of property seemed to have the same problem. As a solution to try and get my normal IMIE back I tried flashing back to a stock rom via recovery which has ended up bricking my s2 and I can't access recovery, only download mode. As this was the case I thought I'm gonna have to use Odin on the laptop to install stock rom but now I'm faced with a new problem. My PC wont install the Samsung USB modem, I have tried installing kies mini, installing the Samsung device drivers, installing pdanet al just to get the Samsung USB modem to install but it just doesn't. I've spent all day installing, rebooting, uninstalling, rebooting, reinstalling to no avail. So now I'm stuck with a laptop that can't read my s2 and forced to use my Samsung mini for internet and Downloading on a data plan (lucky its unilimited). Can anyone help me. Thanx in advance.
Honestly, to get this done as easily as possible, try another PC (and use paragraphs; attempting to read what you've posted was nightmarish & I almost didn't bother).