Develop Bugs

Bluetooth HID for MIUI

This guide is based heavily on the one found here: http://i-miss-erin.blogspot.com/2009/09/connect-bluetooth-keyboard-in-android.html
In fact, all information was gleaned from Erin's blog (super props to Erin). This guide is just slightly simplified, with a flashable zip instead of a few ADB steps/
Step 1.) Download the MIUI_Bluetooth_HID.zip from the Download page
Step 2.) Turn Bluetooth ON from Setting UI and click 'Scan for devices'
Step 3.) Select your bluetooth keyboard and pair it.
Step 4.) Under your keyboard android will state "Paired but not connected"
Step 5.) Open up a command prompt/terminal. I am working on a script to automate this part, but for now, you need to use ADB).
Note: Some of the following commands will output text.
adb shell
hcitool scan
(All bluetooth devices in range will be listed here. Look for your bluetooth keyboard, and copy down it's MAC Address)
hidd --connect xx:xx:xx:xx:xx:xx
(Replace xx:xx:xx:xx:xx:xx with your bluetooth keyboard's MAC Address)
hcitool con
(This command shows all connected HID devices, and should list the MAC Address of your bluetooth keyboard)
And that should be it - try typing and see if it works.
If anyone knows how to do the following in a bash script, I'd be grateful if you could tell me.
- Search for a text string in a text file, and replace it with a different text string.
The idea here:
- Script1 runs the scan
- The user copies down the keyboard's MAC Address
- The user enters the MAC Address and it is stored as a variable (is it possible for this to happen automatically?)
- The Script1 then duplicates a second script file called Script2
- The Script1 replaces a preset string (eg xx:xx:xx:xx:xx:xx) inside Script2 with the correct MAC Address of the bluetooth keyboard.
- Script1 runs Script2
- Script2 completes the HID control command
anyway, Thank Erin if it works for you - it worked for me.
Josh

Sense Integration
Can someone PLEASE integrate this into a Sense ROM? IE: Currently using PAYS 2.2...
I tried forcing the files in to /system/xbin but I get the following:
# hcitool scan
Device is not available: No such device
I just got an Rii mini BT Keyboard because it said it was Android compatible, but the drivers won't validate... apparently there's a licensing issue with the OEM or something (found this info on a Google search).
Can someone help?

bdusmc said:
Can someone PLEASE integrate this into a Sense ROM? IE: Currently using PAYS 2.2...
I tried forcing the files in to /system/xbin but I get the following:
# hcitool scan
Device is not available: No such device
I just got an Rii mini BT Keyboard because it said it was Android compatible, but the drivers won't validate... apparently there's a licensing issue with the OEM or something (found this info on a Google search).
Can someone help?
Click to expand...
Click to collapse
Not possible.
Sent from my HTC Desire using XDA App

hi
hi
can u please help me to connect desire hd to rii mini blue tooth keyboard
it is detected but not pairing. Please help me

Hate to bump an old thread like this, but I've been trying to get this type of support on my phone and keep getting pointed to the Desire thread.
On that note, on the Download page the file we are told to download (MIUI_Bluetooth_HID.zip) isn't there. Any idea where it went?
Thanks!

any progress on this dude? i mean automating the connections?

I know this is a thread about HTC Desire, and I beg your apologies in advance for the intrusion, but...this solution is expected to work also in a Motorola Defy, or it will not work?
(just wondering if can be applies in other phones too...)

AT Commands + other kind of Commands

In amss.bin you can find several AT Commands...
Few short tested by me:
AT+DEVEXTMEMINSCHK?
Hmmm. returns only 2
No idea, I thought something for Memory...
AT+USERMEM
Returns 0k or maybe okay
AT+HEADERINFOSHOW?
Shows for instance the Memory name...
MemoryName:KAC007021M(S8500)
Btw... This is exact what we can read on Application Processor Chip.
1 hint that RAM is integrated with S5PC110 Processor...
Best Regards
TRY at your own risk. I have no idea what could happen.

s8500 support several types of at commands.
First type is common at commands set (70 commands), including AT+CPIN, AT+CMGR etc
the second (samsung specific, 171 commands) has many useful commands like etc
s8500 support 293 at commands (including common commands like AT+CPIN, AT+CMGR, and samsung specific like AT+IMEITEST, AT+CPU also)
complete list in attachment.
Do not use if you do not know what the command is for

AT+PRODUCTCODE?
Result:
AT+PRODUCTCODE? +PRODUCTCODE: GT-S8500BAADBT
If I enter:
AT+PRODCODE
Result:
Invalid Parameter
Hmmm. I'm not up to date in using AT commands.
Is it maybe possible to change Product Code via AT Command?
How is the correct Syntax for AT+PRODCODE ?
There are more interesting Commands.
Best Regards
P.S.:
I was only in Kies Mode, maybe other results in Debug Mode possible...

AT+DEVCONINFO
MN(GT-S8500);BASE(GT-S8500);VER(S8500XXKK7/S8500OXAKK7);HIDVER(S8500XXKK7/S8500OXAKK7);PRD(GT-S8500BAADBT);SN();IMEI(3xxxxxx3);PN();TZVER(20111025);CON(AT,MTP);HVID(Osp:2097153,IntSys:2097154);LOCK(NONE);LIMIT(FALSE)
Oh, not realized before... few changes...
On previous bada 1.x... looks like this:
MN(GT-S8530);VER(S8530XXJL2/S8530OXFJK3);HIDVER(S8530XXJL2/S8530OXFJK3);PRD(GT-S8530BAASEB)
MN should be manufacturer I think... this is very funny text string.
Best Regards
Edit 1.
My fault... MN is Model Name...

Ooh, this reminds me of the days when I had a SonyEricsson T68 and K750.... Good ol days ... One thing missing from those days .. Our samsung wave telephones don't do the Bluetooth HID protocol...

How do you send these commands?
Can you post output from:
AT+DGLOCK
AT+LVOFLOCK
AT+DETALOCK
?

How do you send these commands?
Click to expand...
Click to collapse
You can choose... there are hundrets of Tools, or write your own Terminal...
Few Tools I've used for this...
Revskills very often...
WinComm
QuB...
.
.
AT+DGLOCK
AT+LVOFLOCK
AT+DETALOCK
Click to expand...
Click to collapse
I'm little wimpy old man as you know...
But as I have 0 info about this... I'm scared to lock something and brick my handset...
No idea how to unlock ...
I'll investigate more...
Google research etc. and report later more... I'll try to be on the safer site...
About DELTA files/FOTA...
http://www.megaupload.com/?d=Z53R1IVX
I have upload few of S8500.
Maybe we find Commands or way to install manually these *.cfg Deltas...
Maybe AT Command also work...
Best Regards
Edit 1.:
Found this... untested yet:
Code:
AT+FOTALOC
AT+FOTAREADY
AT+FOTASTART
Edit 2...
Or maybe more such DEV Commands...
GetFotaEngineVer
Get FOTA Engine Version
Edit 3...
Maybe for Update... beter search for something like this:
SML_DM_FUMO_STATE
Or SCOMO
SCOMO Download Complete go to ui event 1...
SCOMO...Warning!!!! Delta Over Size
DownloadAndUpdate...org.openmobilealliance.dm.firmwareupdate.devicerequest
http://www.openmobilealliance.org/t...ram/docs/ets/oma-ets-fumo-v1_0-20061215-c.pdf

I'm sure LVOFLOCK gets level of lock - doesn't overwrite anything
The same about DETALOCK (detailed lock)
Just don't remember what was the code for DGLOCK, so don't use it for now if u're scared. You won't find these in google I think, these are Samsung specific, maybe only Mocha specific.
//edit:
Btw, many of AT commands goes to AMSS, but only what AMSS do is calling Mocha function in AP corresponding to AT command and returning result. For eg LVOFLOCK make AMSS invoke Bada function (also accessible from QuB) GetLevelOfLock and get it's return value. Can you compare result of these 2 maybe?

http://electronix.ru/forum/index.php?act=attach&type=post&id=46875

Tested by me...
AT+FOTALOC?
: Others
This seems location... folder... Others
AT+FOTAREADY?
COPYRETRY
But AT+FOTASTART seems correct...
Handset reboots... like if I delete *.cfg files...
Hmmmmmmmmm.
Will log with WinComm... maybe then more info...
Best Regards

At+preconfig=2,tmb
at+lvoflock=1,0
at+factrst=0,1
at+lvoflock=0,0
600 pages FOTA OTA Command with explain :
http://www.scribd.com/doc/63560940/47/FOTA-Commands
http://www.google.fr/url?sa=t&rct=j...sg=AFQjCNFTQzBSwRrZg82TEZSOleqClg4dbA&cad=rja

AT+FOTASTART 2400258.cfg
Error...
AT+FOTASTART after Download of package, not start downloaded update.
Maybe wrong syntax or FOTA of Qualcomm part only... amss.bin...
I can't see anything with WinComm... maybe next try with QXDM... if amss related...
@ Tigrouzen
Many thanx for helpfull Links.
Best Regards

adfree said:
AT+FOTASTART 2400258.cfg
Error...
AT+FOTASTART after Download of package, not start downloaded update.
Maybe wrong syntax or FOTA of Qualcomm part only... amss.bin...
I can't see anything with WinComm... maybe next try with QXDM... if amss related...
@ Tigrouzen
Many thanx for helpfull Links.
Best Regards
Click to expand...
Click to collapse
But i remember some time Samsung change this thing like not AT+FOTAUIMODE but
AT&FOTAUIMODE
Now its work but no Carrier
In our wave AT+CPIN doesnt work but AT&CPIN works

Code:
AT+FOTALOC?
AT+FOTAREADY?
AT+FOTASTART
Short tried on bada 1.0... JE7 Firmware...
All 3 output was Error...
Okay, not included in amss...
2400258.cfg also as text String in apps_compressed...
Will play little bit with Delta... then move to XXJL2...
Best Regards

Little progress...
AT+DEVCONINFO
Code:
MN(GT-S8600);VER(S8600XXKJC/S8600DBTKJ4);HIDVER(S8600XXKJC/S8600DBTKJ4)...
My S8500...
Best Regards

Did you get S8600 fw on your S8500 !!!!
Man this JTAG playing could kill your phone
Best Regards

Nah, he got FW ID from S8600 on S8500, while S8600 ShpApp & RC may be possible to run on S8500 and vice versa, rather no way about other things. ;P

"DEVCONINFO"="MN(GT-S8600);BASE(GT-S7250);VER(S8600XXKK5/S8600DBTKL1);HIDVER(S8600XXKK5/S8600DBTKL1);PRD(GT-S8600HKADBT)
Click to expand...
Click to collapse
Many thanx to S8600 user for nice info.
Best Regards

AT+SECUKEY +SECUKEY:"DXDxxxxxxxxxxxx=="
OK
AT+AUTHKEY +AUTHKEY:FAIL
OK
AT+DEVAUTH +DEVAUTH:SUCCESS
OK
AT+CERTKEY +CERTKEY:"X5Mxxxxxxxxxxx=="
OK
AT+PASSWORDINPUT +PASSWORDINPUT:SUCCESS
OK
Found Commands in WsSyncml.so, see here:
http://forum.xda-developers.com/showpost.php?p=21541765&postcount=4
No idea yet, what it is.
Best Regards

b.kubica said:
complete list in attachment.
Click to expand...
Click to collapse
Nice post b.kubica
Are you aware of the Qualcomm commands?
AT+CLAC lists these extra commands:
$QCSIMSTAT
$QCCNMI
$QCCLR
$QCDMG - Diagnostic Mode initiation.
$QCDMR - Diagnostic Mode (Baud) Rate. at$qcdmr=? shows available baud rates, at$qcdmr? shows current baud rate
$QCDNSP
$QCDNSS
$QCTER
$QCSLOT
$QCPINSTAT
$QCPDPP - Packet Data Protocol authentication Parameters - see w w w . shapeshifter . se/2008/04/30/list-of-at-commands/
$QCPDPLT
$QCPWRDN
$QCDGEN
$BREW
$QCSYSMODE
$QCCTM
$SUSBC
$NWMDCHNG
$SHPSLEEP
Not sure what they do. All I've found so far is at$qcsysmode restarts the phone with what looks like a file list coming out on the serial port. BREW is the Qualcomm application language.
Does AT_OWANCALL exist in the ROM? That is sometimes used to set up UMTS/HSDPA connections.

[FAQ][DEV] BT, WiFi and MAC Address on HD2

I hope all this is just a little bit interesting for some developers because I can't do any further investigations on ANDROID because my device is broken. At the moment it's on the way and I hope I will get a change of my broken HD2. I have summarized some more or less insteresting facts and I hope someone of you will think about all this informations and can work with them.
First at all: I'm not a developer but I have done some search on ANDROID and logged and logged and logged it again. All this is just a collection of facts and results of compare log files.
When you disassemble some Files within Android, you will see that something will not work because it can't. Let me start with the init.rc what is missing or might be wrong:
1. MISSING FOR BLUETOOTH:
Code:
# create mountpoints
mkdir /mnt_data/download 0777 root system
2. WRONG?
Code:
chmod 0666 /dev/ttyHS1
chown root radio /proc/cmdline
chmod 666 /proc/cmdline
There is no ttyHS1 device within the ANDROID. Can't find it.
3. NOT SURE
rfkill is seems not working. Recommendation on the website:
http://www.gitorious.org/openaos-te...5f360fec4c21c1e06d145a5fe?diffmode=sidebyside
Code:
chmod 0666 /sys/devices/platform/wifi_bt/bt_enable 0
write /sys/devices/platform/wifi_bt/bt_enable 1
but based on ANDROID Developer FAQ it should be:
Code:
chmod 0666 /sys/modules/board_[platform]/parameters/bluetooth_power_on
write /sys/modules/board_[platform]/parameters/bluetooth_power_on 1
and this MUST also done after the change:
Code:
on property:persist.service.bluetoothd.enable=0
write /sys/modules/board_htcleo/parameters/bluetooth_power_on 0
...depend of the settings it also could be:
Code:
write /sys/devices/platform/wifi_bt/bt_enable 0
on property:persist.service.bluetoothd.enable=1
write /sys/modules/board_htcleo/parameters/bluetooth_power_on 1
...depend of the settings it also could be:
Code:
write /sys/devices/platform/wifi_bt/bt_enable 1
Also interesting is the command write which is used a lot of times by the init.rc. I don't know where this command is located. But if you open a SHELL on Android and try to "write" something you will see that this command is not available. Can someone explain how this will work when this command is not available????
4. WRONG!
Code:
chmod 666 /dev/uinput
chmod 666 /etc/bluez/audio.conf
chmod 666 /etc/bluez/hcid.conf
chmod 666 /etc/bluez/input.conf
On the one hand this path is not existing and on the second hand the hcid.conf is also not existing. If you take a look only within /etc you will see that /etc/bluetooth is only existing.
5. BT INITIALIZATION
Code:
service hciattach /system/bin/brcm_patchram_plus --enable_hci –enable_lpm --baudrate 3000000 --patchram /etc/firmware/bcm4329.hcd /dev/ttyHS0
user bluetooth
group bluetooth net_bt_admin
disabled
This is also not working at all. If you try to run this command via the shell nothing will happens. And if you need to load the firmware into the device you need also setup this device by nvram.txt which you can see within the bluetooth.c file. The nvram.txt is important to get a valid MAC Address from the hardware. If you take a look into the source code of the BCM4329 you will see additional informations about this.
The second problem is the value of 3000000. This is to small. If you want to work with head set than a value of 4000000 is minimum required. From my point of view this initialization should be:
Code:
service hciattach /system/bin/logwrapper /system/bin/hciattach -s 57600 /dev/ttyHS0 any 4000000 flow
The value 57600 is the minimum value for initialize bluetooth and it could be that this value will downsize the standby drain. Not sure, just an idea.
Why? Lets take a look into the main.conf or hcid.conf:
Code:
# What value should be assumed for the adapter Powered property when
# SetProperty(Powered, ...) hasn't been called yet. Defaults to true
InitiallyPowered = true
# Remember the previously stored Powered state when initializing adapters
RememberPowered = true
This was the reason why I think the initialization speed "...-s 57000 /dev..." should be lowerd down which might also solve the battery drain issue. Again, not sure - just an idea.
Btw, if you open the ADB shell and try hciconfig, hciattach or hcitools non of this are working because there is no Bluetooth Adapter even if you have BT enabled. This tools are requried for BT analyse, test and command options. You can call each of the files within the Shell but whatever you try to do you it will fail because BT is not enabled. Try to run rfkill which could initiate a reset on the BT device. If you try to rfkill ttyHS0 which is the BT adapter on HD2 device this will not work. From my point of view all this problems are not only related to the kernel.
6. TAKE A LOOK INTO THE init.htcleo.rc
Code:
# Make sure we startup btld before hcid
# Set target address to emulator host loopback IF
# Limit baudrate to 460800 to ensure reliable uart operation
service btld /system/bin/logwrapper /system/bin/btld -hwtun 10.0.2.2 -hb 460800 3000000 -lpm 1
# service btld /system/bin/logwrapper /system/bin/btld -lpm 1 -hb 3000000
Not sure what will run first. The init.rc or the init.htcleo.rc. If the init.rc will run first this could be also a problem. Btw, the first value is 460800. From my point of view this is too much for initialization.
7. WiFi INITIALIZATION
Just an example but if you do a Google search for "BCM4329 nvram.txt" you will get more than 3 links. Let me show here an example:
http://android-wifi-tether.googlecode.com/svn-history/r465/trunk/res/raw/tether_edify
Search for Value 4329 and you will see SAMSUNG Device bla, bla – don't know from top of my head:
Code:
!file_exists("/sdcard/android.tether/bcm4329.bin") && ( module_loaded("dhd") || log(insmod("/lib/modules/dhd.ko", "firmware_path=/system/etc/wifi/bcm4329_mfg.bin nvram_path=/system/etc/wifi/nvram_mfg.txt"), "Loading dhd.ko module<br>(bcm4329_mfg.bin from /system/etc/wifi/)"); );
Hmm... That was the reason why I grabbed the SAMSUNG i9000 from a friend of me and double checked the device. If you take a look into the /etc/wifi you will see the nvram.txt. I'm not sure how this will be loaded into the device but the i9000 has the same BCM4329 Chipset.
Now let us take a look into the wifi.c for QUALCOMM devices which is also valid for the HD2:
http://gitorious.org/linux-on-qualc...f8dffe668c0448/libhardware_legacy/wifi/wifi.c
Code:
Line 61: Take a look. Nothing of this is existing on the HD2
Line 71: there is no wlan.ko on the HD2
But now, where the hell the MAC Address is stored for the WIFI Adapter? Just take a look at this location:
Code:
sys/module/board_htcleo/parameters/bdaddress
or use this:
Code:
/system/sysroot/module/board_htcleo/parameters/bdaddress
If you check this file you will see there your current MAC Address of the WIFI device. The stupid MAC for the BT device seems not stored on the device. And this is the point where I guess to need the fu***ing nvram.txt.
I have done a search for some BCM files and found something interesting which is attached as "Broadcom Files.7z." There are some (!) more or less firmware files within (?) and also the famous nvram.txt
For additional informations about WiFi and more just open the wifi_suplicant within the /system/bin directory with a simple text editor and browse down to the end. There you will see also a lot of interesting settings for the WiFi environment.
8. W.t.F. IS THIS STUPID NVRAM.TXT?
Download attached Broadcom.7z and check the txt file within. If you open the file you will see the nearly same content as within the
Code:
/etc/calibration
file.
But this file you can ignore on your HD2 device. Delete it, rename it – do whatever you want and you will see no changes on the device. The more interesting thing is within
Code:
/sys/calibration
Huhhhh...! The same file but less values. But where does it come from??? Currently I don't know.
It seems that the nvram.txt is as same as like a BIOS for the device. The BCM4329 is a BT AND WiFi Chip within one CHIP. It might be wrong but I guess this is the easy explanation for this.
And because of this the thing can't work. First it needs to load the BIOS (nvram.txt) and then it needs the OS for it (BCM4329 Firmware).

Okay here is something by reading and following your examples:
sys/module/board_htcleo/parameters/bdaddress
That lines exists in the current NAND Android roms, but this line:
/system/sysroot/module/board_htcleo/parameters/bdaddress
doesnt exist, not in Rafs rom or in imilka's 0.1 GB sense rom.
But here is my key interest: "bdaddress" is where the BLUETOOTH MAC Address is!
Another interesting thing, in imilka's 0.1 GB Sense rom, I can change this to whatever I want and it Sticks till I reboot, but in Rafs it does not.
Key Question, How do we make this file KEEP the changes we make to it??? I know its a dirty fix but none the less its a FIX!! So anyone got a clue?!??

First of all there is a WRONG that is big like an house
the init.rc "syntax" is not shell syntax.
so as example, command "write" will not work in shell... but only in init.rc
I see also a lot of confusions about stock froyo/gingerbread stuff and sense stuff.
Example: Sense uses it's own stuff for BT so a clean init.rc for sense is really different from the one for a non-sense build.
Also some stuff/commands needs to be changed/replaced to have them working with our hd2 kernel.
I have no time now but really this posts is about 30 different things that cannot be explained all togheter.
My suggestion is to google for "android init syntax" and start from there understanding all the android boot process and the android init syntax.

About the wifi mac address.
The wifi mac address is "read" from the libhardware_legacy.so
normmaly this lib reads the mac address in /etc/calibration
this file is a "kernel" file so you are not able to change it.
You can use a modified libhardware_legacy.so that reads the mac address in /system/etc/calibration so you can change it, as I did on my builds where you can change the wifi mac address.
Unfortunately the modified libs causes other issues like gps not working.
---------------------------------------------------------------------------
About the problem that you cannot write permanetly the changes on stuff inside the folders
/
/etc
/proc
/sys
and so on.. this is because those folders are the "kernel" that normally is read-only
you can make it write enabled but it's not a safe way to proceed...

so is there a chance to fix the issue with the bluetooth mac?!
would be important for me
(can't use my parrot car kit with my wifes hd2 because of the same mac adress )

rafpigna said:
First of all there is a WRONG that is big like an house
the init.rc "syntax" is not shell syntax.
so as example, command "write" will not work in shell... but only in init.rc
I see also a lot of confusions about stock froyo/gingerbread stuff and sense stuff.
Example: Sense uses it's own stuff for BT so a clean init.rc for sense is really different from the one for a non-sense build.
Also some stuff/commands needs to be changed/replaced to have them working with our hd2 kernel.
I have no time now but really this posts is about 30 different things that cannot be explained all togheter.
My suggestion is to google for "android init syntax" and start from there understanding all the android boot process and the android init syntax.
Click to expand...
Click to collapse
Thanks mate! The problem is that I have no clue how to do it but I hope someone outside who has more experience with all this knows what to do.
Btw, I have had also tried to do a simple test with this "write" command by fill a line within /etc/test and also /proc/test which fails. Usually I added some lines into the init.rc to see if this will work.
But I'm not sure if I have had something wrong.

rafpigna said:
About the wifi mac address.
The wifi mac address is "read" from the libhardware_legacy.so
normmaly this lib reads the mac address in /etc/calibration
Click to expand...
Click to collapse
Sorry, but this is not true. Check this:
http://developer.android.com/reference/android/net/wifi/WifiInfo.html
If you check this from Android SDK you will see that the wpa_supplicant is responsible for this. And this would be O.K. if you also check the BCM4329 source code.
First the CHIPSET will be initiated and prepared by the firmware and the nvram.txt and after that the wpa_supplicant do the rest.
How this exactly will work - sorry, too less coding knowledge
A good thing is it to compare the MAC & BT issue with the i9000 devices and Sony X10. The Sony X10 has the same QUALCOM chipset as the HD2.

Here are the files from the original Desire HD 1.8x.
The initrd.zip contains is the original file and the initrd~.7z is the extracted who is interested to read and compare.

see this http://gitorious.org/linux-on-wince...mmit/ce69804632e64b397758c1c9835f06efd0c8cb54
in file arch/arm/mach-msm/board-htcleo.c i see from markinus some changes to file bdaddress.but it is not in the main git tree we use for hd2 kernel
maybe someone kernel developer can see it and make a kernel for testing;

clio94 said:
see this http://gitorious.org/linux-on-wince...mmit/ce69804632e64b397758c1c9835f06efd0c8cb54
in file arch/arm/mach-msm/board-htcleo.c i see from markinus some changes to file bdaddress.but it is not in the main git tree we use for hd2 kernel
maybe someone kernel developer can see it and make a kernel for testing;
Click to expand...
Click to collapse
Looks good, but this is not valid for HD2. This is HTC Tattoo. If you check this code you will see "akm8973".
Damn!

http://nagaraj-embedded.blogspot.com/2011/02/guide-on-adding-wifi-drivers-on-android.html
and
http://www.jetdroid.org/forum/viewtopic.php?f=78&t=456&start=20#p4502
Can someone double check this???? From my point of view this looks quite good...

MrT69 said:
Sorry, but this is not true. Check this:
http://developer.android.com/reference/android/net/wifi/WifiInfo.html
If you check this from Android SDK you will see that the wpa_supplicant is responsible for this. And this would be O.K. if you also check the BCM4329 source code.
First the CHIPSET will be initiated and prepared by the firmware and the nvram.txt and after that the wpa_supplicant do the rest.
How this exactly will work - sorry, too less coding knowledge
A good thing is it to compare the MAC & BT issue with the i9000 devices and Sony X10. The Sony X10 has the same QUALCOM chipset as the HD2.
Click to expand...
Click to collapse
I'm wrong?
Sorry to say, I'm not an andorid guru but maybe I have a little bit more knoledge and trust me in our case, at least with our builds, the mac address is read from the calibration file.
So how is possible that in my builds you can change the wifi mac?
I just take yor desired wifi mac, write it in the /system/etc/calibration file and replace the libhardware_legacy.so that will read from that instead of /etc/calibration
MrT69 said:
Thanks mate! The problem is that I have no clue how to do it but I hope someone outside who has more experience with all this knows what to do.
Btw, I have had also tried to do a simple test with this "write" command by fill a line within /etc/test and also /proc/test which fails. Usually I added some lines into the init.rc to see if this will work.
But I'm not sure if I have had something wrong.
Click to expand...
Click to collapse
Already said... init.rc syntax is not shell syntax!!!
Anyway.. I still miss the purpose of this thread....

Just the first two google search links appearing with a simple "android init.rc" search
http://www.androidenea.com/2009/08/init-process-and-initrc.html
http://elinux.org/Android_Booting
Read that and something will be clearer.

rafpigna said:
I'm wrong?
Sorry to say, I'm not an andorid guru but maybe I have a little bit more knoledge and trust me in our case, at least with our builds, the mac address is read from the calibration file.
Click to expand...
Click to collapse
It might be that I have had something missunterstand but I only want to say by default (!) the MAC Address is not read from the calibration file by ANDROID. Of cause I have had tested your solution and it's working.
So how is possible that in my builds you can change the wifi mac?
I just take yor desired wifi mac, write it in the /system/etc/calibration file and replace the libhardware_legacy.so that will read from that instead of /etc/calibration
Click to expand...
Click to collapse
I know that the MAC Address could be changed within this way. I hope you don't understand it within the wrong way but from my point of view this is only a patch solution. Because of the fact that the BT & WiFi Chip is ONE (!) chip within HD2 there must be an other solution to read and get the MAC address for WiFi AND BT.
Already said... init.rc syntax is not shell syntax!!!
Click to expand...
Click to collapse
I only was asking why and where it was not working. In the mentime I know it because of your feedback. But I have add some lines into the init.rc and the files and changes was not written to the device. That was the reason why I was asking.
Anyway.. I still miss the purpose of this thread....
Click to expand...
Click to collapse
Hope to find some people who will help to fix all this issues and on the second hand I hope to find a solution for the BT and WiFi MAC to get it from the device.

It is proper time to make an open discussion about the 2.2.1 rom and more tweaks closer to HD2 reveal in the community.

MrT69 said:
I know that the MAC Address could be changed within this way. I hope you don't understand it within the wrong way but from my point of view this is only a patch solution. Because of the fact that the BT & WiFi Chip is ONE (!) chip within HD2 there must be an other solution to read and get the MAC address for WiFi AND BT.
Click to expand...
Click to collapse
maybe this is wrong but it is extremely good that in sense roms,you can change at any time wifi mac address.in my city municipality have free wifi hotspot but after sometime reads your wifi mac address and cut the connection for a time.so with dynamic wifi address i can be almost all time everywhere online and this saves me from a slow (because i live in a small greek city and 3g connection is not everywhere) data edge connection.

ppp widget 1.0 apk

Does anyone still have the 1.0 apk?
I upgraded to 1.1 now it will not find my sprint modem and problems here and there.

Here you go..... [removed]

taqulic said:
Here you go..... http://db.tt/jnAqmyXk
Click to expand...
Click to collapse
Thank you so much, to bad I can only give you one thanks :laugh: , now everything is working again. I dont know what the dev changed on the update but something did dealing with the sprint modem..etc. and it all went down hill.

Seems like someone else had that problem too.... thought I read it in the reviews..

taulic,
please be so kind and remove the public access to the APK file.
The original package is fixed now.
Note that the program itself is free of cost but not free to copy. If people run into trouble I will provide older versions when asked.
Regards,
Author of PPP Widget

JFDee said:
taulic,
please be so kind and remove the public access to the APK file.
The original package is fixed now.
Note that the program itself is free of cost but not free to copy. If people run into trouble I will provide older versions when asked.
Regards,
Author of PPP Widget
Click to expand...
Click to collapse
Done.

PPP works once, then ned to re-installed
taqulic said:
Done.
Click to expand...
Click to collapse
Hi There,
The app works fine when I install it first, my dongle i being recognized no problem. However if I disconnect, and unplug the dongle and try to connect again, the widget shows "no modem found".
I have tried forcing the app to stop, uninstall stickmount as I thought there was clash between both apps and still it doesn't work. the only work around I v found is to re-install the app, which is not very convenient when on the go and needing internet in the first place to be able to access it.
Would you be willing to provide me the APK installer as I am quite happy to install the app whenever I need it, or maybe suggest a workaround?
you have done a fantastic job by the way
G

file is no longer available
Will you please re-upload the file (PPP wedget 1.00 APK) in drop box since the hyperlink says (The file you are looking for has been deleted or moved). Thank you very much

You should first, email the author of the app and see if he can help you with your problem.
I'm not sure I still have the app in backup... as I only save them for so long. (But I'll check).

For those people having problems with this app, there is a forum and active discussion
Here, click forum link at bottom of page.
http://www.draisberghof.de/android/pppwidget.html

Will you please email this file; thanks
Unknown Zone said:
Thank you so much, to bad I can only give you one thanks :laugh: , now everything is working again. I dont know what the dev changed on the update but something did dealing with the sprint modem..etc. and it all went down hill.
Click to expand...
Click to collapse
Dear "Unkown Zone", will you please email this file (PPP Widget 1.00); thanks

Please email link
Unknown Zone said:
Does anyone still have the 1.0 apk?
I upgraded to 1.1 now it will not find my sprint modem and problems here and there.
Click to expand...
Click to collapse
If you have older version of PPP Widget 1.00 (apk file), please post a link. I have tried many changer.bat options since your last post; both uberoid v11 and 12.1. Nothing seems to work so far to make the ZTE-MF190 work again since upgrade from stock ROM. Tried 2 look for this file however no success. Thank you.

Deleted.

samsung note i717 no drivers found
PPP Widget version 1.3.3
USB_ModeSwitch log from Tue Sep 24 21:36:19 IST 2013
Raw args from udev: 1-1/1-1:1.0
Using top device dir /sys/bus/usb/devices/1-1
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product USB Storage
serial 000000000002
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/19d2.fff5
! matched. Reading config data
devList 1:
config: TargetVendor set to 19d2
config: TargetProductList set to fff1,fffe,ffff
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 2 -v 19d2 -p fff5 -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.7 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x19d2
DefaultProduct= 0xfff5
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="fff1,fffe,ffff"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
QuantaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
BlackberryMode=0
PantechMode=0
MessageEndpoint= not set
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/002 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:fff5
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x0a (out) and 0x89 (in)
USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: USB Storage
Serial No.: 000000000002
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x0a for message sending ...
Trying to send message 1 to endpoint 0x0a ...
Sending the message returned error -6. Trying to continue
Resetting response endpoint 0x89
Could not reset endpoint (probably harmless): -6
Resetting message endpoint 0x0a
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 19d2:fff1 (ZTE, Incorporated: ZTE CDMA Tech)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /system/bin/insmod
Trying to find and install main driver module "option"
Checking for active driver path: /sys/bus/usb-serial/drivers/option1
Driver not active, try to find module "option"
Can't find module "option"
Existing path found:
No way to use driver "option"
- try falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding did not work for this device
All done, exiting
QUOTE=taqulic;34223799]Here.
http://www.filesend.net/download.php?f=4c6891af31cb635623fac53e094def52[/QUOTE]
Sir,
Using samsung note i717with official jb rom 4.1.2, ppp app says driver not found, device log is as above. Request you to help in this regard.

[PX5][MD725] Solution for the bluetooth echo v2

Hi,
I release final solution for the bluetooth calls echo issue. Solution is for the PX5 units. For now it works only with MD725 module.
Donate to me
If you want to use this solution in your custom ROM, please put my "Donate to me" button in a noticeable place.​
Changelog:
26.08.2017:
-Added patched version of sdsdk
-Fixed problem with auto connect after sleep
24.08.2017:
-Added libgnustl_shared.so to zip archive because not all ROMs have it.
Click to expand...
Click to collapse
All needed files are available in the attachment
!! You have to be rooted in order to use this solution for the bluetooth echo !!​
1. Copy gocsdk, sdsdk, libf1xaec.so, libgnustl_shared.so and f1xaec.ini files to your SD card
2. Install a file manager (like ES File Explorer) which supports exploration of Android system dirs.
3. Go to /system/bin directory
4. Find gocsdk file and rename it to gocsdk_backup
5. Copy gocsdk file from your SD card to /system/bin
6. Set permissions (access rights) to 777 for /system/bin/gocsdk
7. Find sdsdk file and rename it to sdsdk_backup
8. Copy sdsdk file from your SD card to /system/bin
9. Set permissions (access rights) to 777 for /system/bin/sdsdk
10. Copy libf1xaec.so to /system/lib directory
11. Set permissions (access rights) to 777 for /system/lib/libf1xaec.so
12. Copy libgnustl_shared.so to /system/lib directory
13. Set permissions (access rights) to 777 for /system/lib/libgnustl_shared.so
14. Copy f1xaec.ini to /system/etc directory
15. Set permissions (access rights) to 777 for /system/etc/f1xaec.ini
Now it is very important to figure out what binary is used by your Head Unit. It can be either sdsdk or gocsdk. Right now rules of choosing binary by a Head Unit are unknown - probably it depends on MCU.
16. Install a terminal emulator (like Termux)
17. Execute command ps | grep gocsdk and ps | grep sdsdk
18. Remember what process is running (gocsdk or sdsdk) (if execution one of these commands gave you more lines of output, it means that this binary is used by the Head Unit)
19. Open /system/etc/f1xaec.ini
20. If your Head Unit is using sdsdk, change value of the streamDelay parameter to 280
21. If your Head Unit is using gocsdk, change value of the streamDelay parameter to 210
22. Restart Head Unit.
Click to expand...
Click to collapse
gocsdk and sdsdk are taken from HA 20170726 rom. If someone of you would have a problem on newer firmware, then we will consider update of binaries.
Short info: libf1xaec.so is a shared library containing implementation of webrtc algorithms with my patches and adjustments for RK3688 SoC. Do not worry - any viruses or other spyware are not included .

I'm sorry and I personally disagree with what was done by XDA moderators, I hope the manufacturer will listen to you.
In any case thank you for all the hard work you have done.

I also disagree.. I will donate back. The donation is a thank you for all the hard work.
So thank you.

hi,
thank you for the refund, but i sent it to you back, it is for your hard work as write Nomader0, thank you

Joining the others here in what they say, I will also donate again. - your work is worth it regardless of this isolated fix.
Looking forward to what happens here, and to see what you can achieve with the manufacturers...

We have so many great people here . Guys, thank you very much for all your messages and donations - I really, really appreciate that . Now I see that is worth to sitting even 3 months in the car D) just to read such good words.
So, there is no time to wait. Please read the first post and enjoy .

Great! Is there any precautions in install if I already have one of your earlier fix? (testing the old "C" right now)
Is the old gosdk_orig ok, just rename to _backup? The other "sdk" file in the first fix should be taken back to original?

[email protected] said:
Great! Is there any precautions in install if I already have one of your earlier fix? (testing the old "C" right now)
Is the old gosdk_orig ok, just rename to _backup? The other "sdk" file in the first fix should be taken back to original?
Click to expand...
Click to collapse
Nothing special to upgrade from previous solution is needed. Just replace gocsdk from old solution with newer one and follow the README.
Yes, sdsdk can be taken back to original. Name of the gocsdk backup file does not matter - it can be _backup, _orig, etc.
What I observed, Sdsdk* binaries are not executed by Android at all. They are almost the same as gocsdk. The only difference is implementation of the audio pooling.

Hi, I have an xtrons PB7653BAP with the same problem. I tried your solution, but cannot rename or copy in the directory with ES File Explorer. It is read only. How can I change that? Afterwards, how can I set permission codes to 777?
Thanks

clsbuilder said:
Hi, I have an xtrons PB7653BAP with the same problem. I tried your solution, but cannot rename or copy in the directory with ES File Explorer. It is read only. How can I change that? Afterwards, how can I set permission codes to 777?
Thanks
Click to expand...
Click to collapse
you have to be root.
after that use root explorer

Nomader0 said:
you have to be root.
after that use root explorer
Click to expand...
Click to collapse
OK, thanks for that. Stupid question (I'm not used to Android) perhaps but how to get rooted? Do you mean at the reboot (menu) of the radio?

clsbuilder said:
OK, thanks for that. Stupid question (I'm not used to Android) perhaps but how to get rooted? Do you mean at the reboot (menu) of the radio?
Click to expand...
Click to collapse
ok..
1st, is your unit a PX3 or PX5?
there are 2 ways to root
1. install Malaysks ROM which is rooted
2. use tools like kingoroot etc..

Nomader0 said:
ok..
1st, is your unit a PX3 or PX5?
there are 2 ways to root
1. install Malaysks ROM which is rooted
2. use tools like kingoroot etc..
Click to expand...
Click to collapse
OK, I can manage that. About px3 or 5, no clue; where can I find that? Can you help me on that? I cannot post a link (because I am new), but if you search for xtrons PB7653BAP you will find it; It is a 7" HD Digital Octa-Core 64bit 32GB + 2G RAM Android 6.0 Multi Touch Screen Car DVD Player Custom Fit for BMW E53 / X5.

clsbuilder said:
OK, I can manage that. About px3 or 5, no clue; where can I find that?
Click to expand...
Click to collapse
Settings >> About tablet >> Build number - what is at the beginning of the line?

clsbuilder said:
OK, I can manage that. About px3 or 5, no clue; where can I find that? Can you help me on that? I cannot post a link (because I am new), but if you search for xtrons PB7653BAP you will find it; It is a 7" HD Digital Octa-Core 64bit 32GB + 2G RAM Android 6.0 Multi Touch Screen Car DVD Player Custom Fit for BMW E53 / X5.
Click to expand...
Click to collapse
ok this is a little off-topic.. but here it goes.
99% you unit is PX5. you can go to settings-->about.. and see.. you will also find the word "MTCD" tell me what 2 or 3 letters are next to that... (GS?, MX? KSP?)
this would be you manufacturer..
you will also find the word PX5 somewhere there or PX3..
now if it is PX5 (which probably it is) go to:
https://forum.xda-developers.com/an...lopment/rom-malaysk-roms-mtcd-device-t3598908
and you will find info there on how to install Malaysks ROM.. your unit will be reset. i advise you to install v.2 of the ROM, and not v.3/v.3.5/v4. v2 is the most stable for now.

Hi f1x,
Like everyone I renewed my donation too, you really deserve it.
I am among those who have the new Dasaita unit that uses a new Bluetooth module (SD-968 module) (see attached image)
I launched the two commands: `ps | Grep gocsdk` e `ps | Grep sdsdk`
With the first command (`ps | grep gocsdk`) Terminal Emulator does not return any result (see attached image)
With the second command (`ps | grep sdsdk`) Terminal Emulator returns this result (see attached image):
root 1643 1 35768 10552 do_wait 0000000000 S /system/bin/sdsdk968
root 17880 1643 45060 2900 futex_wait 0000000000 S /system/bin/sdsdk968
[email protected]:/ $
Hope this information can help extend the fix to this new Bluetooth module.
Thank you

Nomader0 said:
ok this is a little off-topic.. but here it goes.
99% you unit is PX5. you can go to settings-->about.. and see.. you will also find the word "MTCD" tell me what 2 or 3 letters are next to that... (GS?, MX? KSP?)
this would be you manufacturer..
you will also find the word PX5 somewhere there or PX3..
now if it is PX5 (which probably it is) go to:
https://forum.xda-developers.com/an...lopment/rom-malaysk-roms-mtcd-device-t3598908
and you will find info there on how to install Malaysks ROM.. your unit will be reset. i advise you to install v.2 of the ROM, and not v.3/v.3.5/v4. v2 is the most stable for now.
Click to expand...
Click to collapse
+ Please check in factory settings what bluetooth module is installed. For now solutions works only for MD725.

apollo1976 said:
Hi f1x,
Like everyone I renewed my donation too, you really deserve it.
I am among those who have the new Dasaita unit that uses a new Bluetooth module (SD-968 module) (see attached image)
I launched the two commands: `ps | Grep gocsdk` e `ps | Grep sdsdk`
With the first command (`ps | grep gocsdk`) Terminal Emulator does not return any result (see attached image)
With the second command (`ps | grep sdsdk`) Terminal Emulator returns this result (see attached image):
root 1643 1 35768 10552 do_wait 0000000000 S /system/bin/sdsdk968
root 17880 1643 45060 2900 futex_wait 0000000000 S /system/bin/sdsdk968
[email protected]:/ $
Hope this information can help extend the fix to this new Bluetooth module.
Thank you
Click to expand...
Click to collapse
my 2nd unit also has sd968. i will try tonight and post my results.. hope f1x can make it work for that too

apollo1976 said:
Hi f1x,
Like everyone I renewed my donation too, you really deserve it.
I am among those who have the new Dasaita unit that uses a new Bluetooth module (SD-968 module) (see attached image)
I launched the two commands: `ps | Grep gocsdk` e `ps | Grep sdsdk`
With the first command (`ps | grep gocsdk`) Terminal Emulator does not return any result (see attached image)
With the second command (`ps | grep sdsdk`) Terminal Emulator returns this result (see attached image):
root 1643 1 35768 10552 do_wait 0000000000 S /system/bin/sdsdk968
root 17880 1643 45060 2900 futex_wait 0000000000 S /system/bin/sdsdk968
[email protected]:/ $
Hope this information can help extend the fix to this new Bluetooth module.
Thank you
Click to expand...
Click to collapse
Yes, now I have all needed info to start work on solution for new bluetooth module. But I will not have possibilty to test it.
I hope I release it still today.

f1x said:
Yes, now I have all needed info to start work on solution for new bluetooth module. But I will not have possibilty to test it.
I hope I release it still today.
Click to expand...
Click to collapse
i can help you any way i can