Database Info

Android 2.2 (Froyo) and Pairing with Car-Kit/rSAP/HFP

Hello everyone,
I would like to share my experience in pairing my Galaxy 3 with the Car-Kit. The configuration is as follows:
Phone: Samsung Galaxy 3 GT-i5800 with Android 2.2 Froyo (not official)
Car-Kit: Bluetooth Touch-Adapter, No: 3C0051435TA
Auto: VW-Passat, Year 2007
In the VW-Specification this phone is not at all supported, and was not possible to pairing with the Touch-Adapter.
Than, I looked into the bluetooth configuration and made some small changes (my phone is rooted) to activate Hands Free Profile.
And it works!!! now I can pairing my phone and get the contacts form SIM into the adapter.
If you're interested I can provide the modified config files and for the users with no rooted phones an update.zip (I must try first).

Yes, please do ))
I've been having the same problem.

guerrpaz said:
Yes, please do ))
I've been having the same problem.
Click to expand...
Click to collapse
Ok. I'll try this weekend to post something.

Bluetooth configuration
Hello,
As I promised, the user with ROOTED phone must unzip and overwrite the attached config audio.conf file in the folder
/system/etc/bluetooth/audio.conf
The config file is from Android 2.2 (Froyo) but you can look to the similar settings for other versions of android.
If it works PLEASE give me a feedback with the following infos (useful for other users too):
Phone: - brand, model, android version
Car-Kit: - brand, model, etc.
Auto: - brand, model, year

Will do, thanks a lot.

It doesn't work, keep getting "incompatível phone" error.
Tried swapping the audio config file with yours, deleting autopair and blacklist files, restoring the old audio config without restoring autopair and blacklist...
No results.
My phone is an HTC Desire with unofficial froyo.
The car is a VW golf from 2010, equipped with a premium rcd 510 radio.
Thanks and have a nice weekend.
Sent from my HTC Desire using XDA Premium App

guerrpaz said:
It doesn't work, keep getting "incompatível phone" error.
Click to expand...
Click to collapse
I'm really sorry. I flashed my phone with a new version, rechanged the audio.conf and still works. But for HTC there are mod roms? Aren't they? These mods are supposed to be better than the stock ones!?

I'm using the latest MCR Rom witch is quite good,i think the problem is brand related.
This Android - RSap incompatibility is well documented, its open issue #4402 .
I read somewhere Samsung had implemented RSAP in their software, so maybe it's brand specific and only Samsung Android Phones will work with RSAP.
Thanks for your kindness.

BT problem on KK (cyano11 based)

Good morning,
I'm using the Mackay rom based on Cyano 11 (android KK 4.4)
I've got a big problem on the BT module...when i pairing it i get alwais a FC after the "code request" ....
Do you know if there are any slution?
maybe a "zip file" that i can test to solve it (modem? the bt is related to it??)?
Thank you in advance
Runner75

After many try i've seen that time to time the "pairing" work... but is still really instable...
often i can't update information from my phone even if the settings of the pairing are ok (all permission on) ... someone has suggestion?
Ty all
Runner75

Bluetooth pairing bug, it can be solved only by the developer or ask in your device forum, they may have been fix for that problem
Sent from my GT-I9070 using Tapatalk

[App] Srlabs releases "SnoopSnitch" for detecting IMSI-Catchers, silent SMS...

[App] Srlabs releases "SnoopSnitch" for detecting IMSI-Catchers, silent SMS...
unfortunetely it only works with some qualcom based devices, you can find a list of working devices under:
https://opensource.srlabs.de/projects/snoopsnitch/wiki/DeviceList
new version is out: 0.9.3
Version 0.9.3
Support Android 5
Fix initialization issue on newer devices
Translation to German and Dutch
Click to expand...
Click to collapse
SnoopSnitch is an Android app that collects and analyzes mobile radio data to make you aware of your mobile network security and to warn
you about threats like fake base stations (IMSI catchers), user tracking and over-the-air updates. With SnoopSnitch you can use the data collected in the GSM Security Map at gsmmap.org and contribute your own data to GSM Map.
This application currently only works on Android phones with a Qualcomm chipset and a stock Android ROM. It requires root priviliges to capture mobile network data.
Requirements:
Qualcomm-based Android phone (see list below)
Stock Android ROM, version 4.1 or later
Note: Unfortunately, custom Android ROMs like CyanogenMod are not supported, as they lack the drivers necessary to collect radio data.
Root privileges on phone
Tested Devices:
The following devices have been verified to work:
Samsung S3 Neo (GT-I9301I)
LG G2 (LG-D802)
Sony Xperia Z1 (C6903)
Samsung S5 (SM-G900F)
Motorola Moto E (Moto E)
Samsung S4 (Qualcomm variant)
It is very likely that other Qualcomm-based Android phones also work, if they are rooted and have a stock firmware.
Incompatible Devices:
The following devices have been found to be incompatible and can not be used with SnoopSnitch:
UNSUPPORTED: Every device without a Qualcomm chipset
UNSUPPORTED: Every device with custom ROM
UNSUPPORTED: Samsung Galaxy S2 & S3
UNSUPPORTED: Nexus 5
UNSUPPORTED: Huawei Ascend Y300
Click to expand...
Click to collapse
from https://opensource.srlabs.de/projects/snoopsnitch (project site)
or google play link:
https://play.google.com/store/apps/details?id=de.srlabs.snoopsnitch

Not working on my HTC ONE M7 converted to GPE 5.0.1 .
Root, S-OFF etc. available. Is there any information about this?

geminga said:
Not working on my HTC ONE M7 converted to GPE 5.0.1 .
Root, S-OFF etc. available. Is there any information about this?
Click to expand...
Click to collapse
Possibly your kernel lacks the necessary support. For instance people with a Nexus 5 can flash this kernel: http://d-h.st/mmb (thanks to this thread: http://forum.xda-developers.com/google-nexus-5/general/radio-enable-lte-band-3-nexus-5-d820-t2928561). About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.

xd.bx said:
About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
Click to expand...
Click to collapse
Well, Carsten Nohl, one of the developers, said yesterday on 31C3, that on CustomROMS like CM certain proprietary drivers are missing, which are needed for getting certain debugging information. Later yesterday in a workshop on 31C3 participants found out, that on some CM11 Phones the app is working.
There the app worked on:
Samsung S3 Neo
Samsung S5
LG G2
Sony Xperia Z1
Motorola Moto E
and dind't work on
Samsung S2, S3, S4 and S5 Exynos
Nexus 5
Fairphone
you can watch the presentation from Nohl on 31C3 here:
http://media.ccc.de/browse/congress...830_-_mobile_self-defense_-_karsten_nohl.html
on my nexus5 with slimkat 8.20 it says:
"device /dev/diag does not exist"

About the compatible devices - I can confirm the app works on on Xperia V with the stock 4.3 Android. It gives no errors, but I have not yet encountered malicious GSM cells to verify the detection works ok.

Why do we have to make long distance calls and send sms to use this app?

http://forum.xda-developers.com/showthread.php?t=1422969

Celestial Fury said:
Why do we have to make long distance calls and send sms to use this app?
Click to expand...
Click to collapse
This is part of active testing, the number called should be busy. Read more on the project site mentioned in the first post.

rudolfm said:
This is part of active testing, the number called should be busy. Read more on the project site mentioned in the first post.
Click to expand...
Click to collapse
Sure I did. It doesn't say why we have to call/sms a specific number and why we data can't be gathered from our every day call/sms and why data can't be sent to the test site through the internet rather than call/sms.

XsheldorX said:
on my nexus5 with slimkat 8.20 it says:
"device /dev/diag does not exist"
Click to expand...
Click to collapse
You need to flash a compatible kernel. http://d-h.st/mmb

Works on my SONY Xperia Z1 with CM11.
Though, when doing the test call my device was banned, for whatever reason....

Yeah I can (probably) confirm this with Z1 compact with CM 11. Works since day one I guess. The test works (around the first days incoming calls and sms did not, probably because of overload of the callingserver), but never had any sort of attacks. Now I'm in doubt if radio-part does not work with cm 11, as mentioned in the description, or there were zero attacks.
Another thing I observed. The software sometimes produces many wake-locks. But I guess thats normal if backgroundservice is active.
@ papperlapapp: Did you monitor any attacks (SS7 or silent sms)? Or even IMSI-catchers?

Installed the app without problems on my S5 with Phoenix ROM (Stock Based). However, when I start the active test, the app stops responding and android asks me several times if I want to close it. I chose no every time. Now I'm wondering if the tests are still running in the background or if the app just hang. Started the tests about 35 min ago, still waiting, absoluteley nothing happened yet.

Why not install something like https://f-droid.org/repository/browse/?fdfilter=monitor&fdid=com.eolwral.osmonitor and see if that task is stil running?
Usefull tool anyway
happy monitoring

Works on Samsung Note 3 SM-N9005
Sent fra min SM-N9005 via Tapatalk

xperia E1 seemingly working
E1 seems to work.
but now what ? where are the logfiles where I see stuff live?
google 31c3 "mobile self defense" for the thrilling background story
let's all hope the CCC talkers have learnt better English by 2016 (Mr Nohl being one of the best still) !
https://media.ccc.de/browse/congres...self-defense_-_karsten_nohl.html#video&t=3838

xd.bx said:
Possibly your kernel lacks the necessary support. For instance people with a Nexus 5 can flash this kernel: http://d-h.st/mmb (thanks to this thread: http://forum.xda-developers.com/google-nexus-5/general/radio-enable-lte-band-3-nexus-5-d820-t2928561). About what the OP said: I can't see why this app wouldn't work on a custom ROM such as CM11 as long as the kernel has the necessary options.
Click to expand...
Click to collapse
Will this kernel work on Nexus 5 with lollipop 5.01 ? I notice the file name is specific for android 4.4.2

MForce22 said:
Will this kernel work on Nexus 5 with lollipop 5.01 ? I notice the file name is specific for android 4.4.2
Click to expand...
Click to collapse
I don't know. Just try, at worst you'll have to reflash the old kernel back.

itman-ch said:
Why not install something like https://f-droid.org/repository/browse/?fdfilter=monitor&fdid=com.eolwral.osmonitor and see if that task is stil running?
Usefull tool anyway
happy monitoring
Click to expand...
Click to collapse
it is on play store too ^^

srlabs posted a device list:
https://opensource.srlabs.de/projects/snoopsnitch/wiki/DeviceList
and a new version is out:
Version history
Version 0.9.2
Fixed app lock-up issues
Improved device compatibility check
Handled unsupported LTE gracefully
Version 0.9.1
Fix problem where SnoopSnitch would leave the phone muted after a test
Remove issue with disappearing (Skype) dialing dialogs
Resolved performance issue in analysis
Version 0.9.0
Initial public release
Click to expand...
Click to collapse

[Completed] Problem with Bluetooth Stereo.

Hello All,
I am using RedMi, and my current version in phone is MIUI7.0 | Stable 7.0.5.0(KHCMICI). I am facing the problem with Bluetooth when even i connect my phone to my car Stereo Bluetooth device. I am seeing "No Track/Artist name". Earlier which i using JB build, i could see the track name and artist name fine. But getting the issue when i start using KK build. So any one help me to resolve this issue at the earliest.?
Please let me know if we have a hack for this.

TejaGogineni said:
Hello All,
I am using RedMi, and my current version in phone is MIUI7.0 | Stable 7.0.5.0(KHCMICI). I am facing the problem with Bluetooth when even i connect my phone to my car Stereo Bluetooth device. I am seeing "No Track/Artist name". Earlier which i using JB build, i could see the track name and artist name fine. But getting the issue when i start using KK build. So any one help me to resolve this issue at the earliest.?
Please let me know if we have a hack for this.
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
Can you specify your device's model number.?
___
v7
XDA Assist

Sony Xperia L,Cannot use WIFI [cm-12.1-20151103-NIGHTLY-taoshan]

hi all.
before the issue, i wanna thank for your answers.
I've an Xperia L and i've installed CM 12.1 since about 3 days; but unfortunately found that i can't use WIFI.
I searched and found some reasons pointing that the error might be for my country's region and Google (US) restriction, i'm living in IR Iran.
is there any other ways to fix this hell bug?? All i need from my device is WIFI...& i'm not gonna change the ROM again.

parhamb_76 said:
hi all.
before the issue, i wanna thank for your answers.
I've an Xperia L and i've installed CM 12.1 since about 3 days; but unfortunately found that i can't use WIFI.
I searched and found some reasons pointing that the error might be for my country's region and Google (US) restriction, i'm living in IR Iran.
is there any other ways to fix this hell bug?? All i need from my device is WIFI...& i'm not gonna change the ROM again.
Click to expand...
Click to collapse
Hey, I'm not sure what your exact issue is but I will present you some possible solutions.
1. Was your wifi broken since you flashed CM12.1? If yes:
What stock version did you have before CM? If it wasn't 15.3.A.1.17 (or if you don't know), flash FTF of this version. Then flash CM12.1 again by flashing the kernel img and then the zip file.
2. Sometimes, the wifi just doesn't work because the wpa_suplicant.conf is broken. This file stores all the wifi passwords. Open the file manager and go to /data/misc/wifi and delete the file. You will lose your passwords, but your wifi will work! If you forgot your passwords, copy the file to another directory before deleting it.
I hope this can help you, please tell me if it did!
Sent from a device in our universe

GreyLDroid said:
Hey, I'm not sure what your exact issue is but I will present you some possible solutions.
1. Was your wifi broken since you flashed CM12.1? If yes:
What stock version did you have before CM? If it wasn't 15.3.A.1.17 (or if you don't know), flash FTF of this version. Then flash CM12.1 again by flashing the kernel img and then the zip file.
2. Sometimes, the wifi just doesn't work because the wpa_suplicant.conf is broken. This file stores all the wifi passwords. Open the file manager and go to /data/misc/wifi and delete the file. You will lose your passwords, but your wifi will work! If you forgot your passwords, copy the file to another directory before deleting it.
I hope this can help you, please tell me if it did!
Sent from a device in our universe
Click to expand...
Click to collapse
hi there and thanks for the answer,
well my case was absolutly the number 1.
i lost my WIFI just after flashing into CM12.1
bafore that i had the original update of 4.1.2 jelly bean android version.
i also had flashed the deice after installing cm 12 into the jelly bean using this tft file: C2105_15.0.A.2.17_Customized-CE.ftf
it was the original OS from factory on my device, the WIFI worked correctly and i could use that & tethering & hotSpot
but when i flashed again into cm 12.1 i lost the WIFI & hotSpot again :|
note:i flashed the device using thunderzup kernel. could it be the cause of problem?
i'm still using the cm 12.1 & it's good.but the wifi problem.
i've the following bugs:
-WIFI can't be turned on in anyways
-the notification light doesn't work correctly sometimes
-the LED light can't be switched off from the notification bar once i switch it on,from that area.

parhamb_76 said:
hi there and thanks for the answer,
well my case was absolutly the number 1.
i lost my WIFI just after flashing into CM12.1
bafore that i had the original update of 4.1.2 jelly bean android version.
i also had flashed the deice after installing cm 12 into the jelly bean using this tft file: C2105_15.0.A.2.17_Customized-CE.ftf
it was the original OS from factory on my device, the WIFI worked correctly and i could use that & tethering & hotSpot
but when i flashed again into cm 12.1 i lost the WIFI & hotSpot again :|
note:i flashed the device using thunderzup kernel. could it be the cause of problem?
i'm still using the cm 12.1 & it's good.but the wifi problem.
i've the following bugs:
-WIFI can't be turned on in anyways
-the notification light doesn't work correctly sometimes
-the LED light can't be switched off from the notification bar once i switch it on,from that area.
Click to expand...
Click to collapse
As i know the ThunderZap kernel for Xperia L should get your WiFi work..
Try Zapdos kernel/stock kernel for xperia l.
i'm on Stryflex lollipop 5.1.1 Rom (CM 12.1 based). i don't have a wifi problem.
Use Light Flow Lite - LED Control from play store for customize LED notification.

ishan.ranatunga said:
As i know the ThunderZap kernel for Xperia L should get your WiFi work..
Try Zapdos kernel/stock kernel for xperia l.
i'm on Stryflex lollipop 5.1.1 Rom (CM 12.1 based). i don't have a wifi problem.
Use Light Flow Lite - LED Control from play store for customize LED notification.
Click to expand...
Click to collapse
aye , seems i've to do a same work
i'm goona flash into stryflex in this weekend...let's hope it works...anyway else i should throw the phon away...