Develop Bugs

AT commands and PPC?

Hello All,
Is it possible to send AT commands directly to PPC and If Yes How?
Thanks & Regards,
Usha

Send AT commands from where? From the serial port of an attached computer? In that case, use the Wireless modem feature present in the latest ROMs: the Qtek 4.16.52 ROM, O2 XDA 4.17.03 or our own XDA-developers Special Edition ROM v1.1 (based on O2's 4.17.03 with lots of extras).

Hi
Do you want to have connections both through the gprs and dial-up to an isp from within your stand-alone XDA. In other words using the pocket internet explorer you want choose between GPRS and Dial-Up connection.
GPRS is expensive for large downloads and Dial-Up is expension for extended connections with low activity.
Cheers
Ian Bennetts

Thanks for the replies, but.,
Hello again,
XDA developer Peter Poelman
Yes, I want to send AT commands from the serial port of an attached computer. Will you please elaborate on the wireless modem feature(remember I am new to PPC) and how do I send AT commands such as CSIM, CRSM using Hyper Terminal to XDA?
Ian Bennetts
No Ian, I am not interested in 'having connections through the gprs and dial-up to an isp from within the stand-alone XDA'. As I have mentioned above, I am interested in talking to SIM with AT interface and want to know how its done.
Thanks & Regards,
Usha

Hmmm, talking to the SIM...
First of all: modern ROMs for the XDA come with an application installed in 'Programs' called 'Wireless Modem'. It allows you to 'disconnect' the internal phone application and talk to the modem directly from a connected PC, using either wired RS-232 or infrared. Contrary to the built-in connectivity, this seems to somehow be limited to 9600, as recently reported in another thread here.
But as far as talking to the SIM: I'm not sure whether these commands are implemented, and you'd need to figure out for yourself if the modem will do what you want. I'm not aware of anyone that has talked to the SIM through the Wireless Modem app.
Do let us know how things turn out...

At least on the SPV, I'd say that only restricted SIM commands are exposed through the RIL, which makes the complexity of the call pretty useless (ie we can't do more than what's exported in cellcore, no raw APDU exchanges) - I may be a total newbie at handsets design but I'd have expected (in my dreams) to have SIM1: being a handle to access the card reader and not some virtualization above the RIL :roll:
note that I'm not completly satisfied by this and still investigating - I'd really like a full SIM control, I can be satisfied with envelopes for the moment, but the more the better :wink:

Has any one taken this ROM appart yet? It has uptated BT.

It is from an HP 6315 from 3/31/05
http://h18007.www1.hp.com/support/files/HandheldiPAQ/us/download/22539.html
I would love to see if we could get this stack and the settings on our XDAII and other HTC devices,,, THAT would be cool.
Bluetooth build 1.0.0.3701:
Corrects inaccurate display of headset icon when a call is in progress.
Adds a check to determine if Bluetooth stack is initialized before accepting messages from phone.
Adds a user interface (UI) change to enable a connected headset to automatically disconnect before attempting to connect to a different headset when the user chooses to connect to a second headset.
Corrects check for invalid device name.
Corrects issue where handheld could not reconnect to remote device after a page timeout.
Corrects Object push profile update so it sends all files.
Updates FTP connection wizard to correct service discovery issue.
Corrects issue with call waiting for incoming call handling while dialing out.
Corrects issue with headset connection icon so it is correctly displayed after power cycling.
Corrects audio to make it compatible with an in-car solution.
Corrects audio issue where the right channel for a headset was unavailable for playing audio and during calls.
Corrects issue where the LED and network status were not properly synchronized.
Corrects issue where the user could not send multimedia messaging (MMS) message.

Hmmmm....a few remarks, correct me if I am wrong:
1. There is already a BT version 1.0.0.3900 available
2. This is not a HTC device, so I doubt the tools developed here will work on it.

HappyGoat said:
2. This is not a HTC device, so I doubt the tools developed here will work on it.
Click to expand...
Click to collapse
This is an HTC device. All HPs are designed by HTC.

Well, even though I don't want to stop progress because I would like to have the ROM taken apart for my own personal reasons, the 6315 was actually made by Compal. Bad move on the part of HP in my opinion. However, the bluetooth stack that was taken from an iMate JAM worked on the 6315 and that is how most survived until the update was released. So it very well could work on the HTC's. On a side note, if someone could point me in the right direction, I will take the ROM apart, just don't know where to start.

mamaich said:
HappyGoat said:
2. This is not a HTC device, so I doubt the tools developed here will work on it.
Click to expand...
Click to collapse
This is an HTC device. All HPs are designed by HTC.
Click to expand...
Click to collapse
Oops....my bad....excuses!

no htc dont make ALL hp's pda's the H5400's was oem'd from LG
and even if the ipaq in question is made by HTC then that dont garentee that the xda tools work as they are not made by HTC

I can tell you now that the XDA tools do not work on that ROM as it stands. However, looking through the HEX, it is laid out a little differently than the XDA ROM's but have some of the same portions, just in different locations. Now if I knew more about what I was looking at, I could take it apart for you. The 6315 uses Widcomm BT and like I stated before the BT drivers ripped from a JAM worked great on the 6315 so I have a feeling the 6315 drivers will work on the XDA's.

I can also tell anyone looking at it that in the first header of the ROM the letters are shifted 13 characters. So when you see RAT it equals ENG and so on. It looks like they don't do that for very long though.

BT
HappyGoat said:
Hmmmm....a few remarks, correct me if I am wrong:
1. There is already a BT version 1.0.0.3900 available
Click to expand...
Click to collapse
BT 3900 and 3500 do not support Hands Free Profile or even Headset Profile on my XDAII.. This is important so people can use Caller ID on a BT device and OR a Car Kit with the Hands Free Profile....
Switching stacks is a pain in the but...
Even so, the only OS that even slightly works with Hands Free on the Himalaya, is 2.20 translated but even that has bugs that makes it very frustrating. The 2005 did have a fully functional BT, even having separate serial ports for each BT device, (like GPS), but the other bugs and the limited memory left over from the useless and unerasable Extended ROM from the other OS made it no good..
With this new ROM, I may be tempted to buy the HP again.. When I first bought one, it was DAM slow and the BT SUCKED!!!
Maybe now it is usable.
I love my Himalaya and it's 128 of built in..
http://www.expansys.com/product.asp?code=PDA2&asource=IMATE
http://www.expansys-usa.com/product.asp?code=PDA2&asource=IMATE
I will just have to keep waiting for one of the above unless someone finds a fix for the BT Hands Free.

Wi-Fi Direct for already released models

Today morning I got a mail from developerATbadaDOTcom(i can't post e-mail address due to low post count ) for bada 2.0.0 b1 sdk release. Ya I got the access to the sdk , many others also might have got the mail. In that they had mentioned new features of the sdk followed by notes. One thing which they had mentioned in the notes was a bit questionable. It said : You cannot use NFC and Wi-Fi direct features in previously released bada devices due to hardware limitations. Upcoming devices with full support are required.
Does this mean users of S8500, S8530 and other WAVE models won't have Wi-Fi direct or does it seems to be a mistake from their side to mention it like that?
Sorry to post in this section, I couldn't post in Bada Software Development, again due to lack of posts.

no
Wifi-direct is not the same as NFC
Wave I & II doesn't have NFC chip so they can't use NFC apps
it is so normal to get this
Best Regards

I know that working of NFC requires some hardware. Just wanted to know the same about Wi-Fi direct.

wifi direct will not be available on all 'old' wave models, wifi-direct technology needs different hardware (like 802.11N do not work on old 802.11G chip..)

I was under impression that it can be supported through software if the device is Wi-Fi capable. Thanks for clarifying it.

guari said:
wifi direct will not be available on all 'old' wave models, wifi-direct technology needs different hardware (like 802.11N do not work on old 802.11G chip..)
Click to expand...
Click to collapse
As I know, Wifi direct don´t need new hardware because is only a protocol over Wifi.
802.11N vs 802.11G is different, because it operates in different frequences, so it needs different hardware.

The galaxy S has wifi direct feature(as mentioned in wikipedia).... So probably the wave and wave 2 has it too... I think the devices that support wifi hotspot feature can use wifi direct.....

Wifi Direct & Bluetooth 3.0:
1.Transfer speed : almost similar to Bluetooth 3.0(7.28 mb in 27 sec @ 2.15mbps video:http://www.youtube.com/watch?v=A7UhqLu4hKg from 1:00)
2.Other possibilities: In gaming wifi direct could make multiplayer connection, etc......
Anyways most of us use Bluetooth & wifi direct mostly for file transfer, we would not be losing any great feature from our waves but those who need wifi direct for other purposes which is not available in Bluetooth 3.0 would be a bit unhappy in-case we don't get Wifi direct.

wave s8500 and s8530
both have 802.11 b/g/n
that means it can operate wifi direct
but not NFC because it needs extra hardware

I correct myself, wifi-direct needs particoular hardware but probably wave s8500/8530 have it. (wikipedia says galaxy S is certified for wifi-direct and the hardware is probably the same)

jake792 said:
Wifi Direct & Bluetooth 3.0:
1.Transfer speed : almost similar to Bluetooth 3.0
Click to expand...
Click to collapse
I read at various places that Wi-Fi direct can achieve max speed of the standard the device supports, means a 802.11n compatible device can achieve a speed of 300Mbps (theoretical) when connected via WiFi direct. So it might be a plus over Bluetooth 3.0.

mayank7_d said:
I read at various places that Wi-Fi direct can achieve max speed of the standard the device supports, means a 802.11n compatible device can achieve a speed of 300Mbps (theoretical) when connected via WiFi direct. So it might be a plus over Bluetooth 3.0.
Click to expand...
Click to collapse
Oops.. Sorry for a misguiding video... here is the one which shows the real capability of Wifi direct:http://thehandheldblog.com/2011/06/20/wifi-direct-galaxy-s2/
Theoretically Wave should have wifi direct because:
1. Galaxy s is wifi direct certified device
2. Wave & Galaxy s have same wifi chip Broadcomm bmc4329.
source: Galaxy s:http://www.ubmtechinsights.com/reports-and-subscriptions/investigative-analysis/samsung-galaxy-s/
Wave:http://www.ubmtechinsights.com/reports-and-subscriptions/investigative-analysis/samsung-galaxy-s/
Hoping for wifi direct on wave........

I asked @samsungbada on twitter regarding this. Now awaiting their reply. In the meanwhile can anyone who has upgraded to leaked bada 2.0 confirm that Wi-Fi direct is there or not?

I can confirm that it is not there

wave supports wifi direct
read its data sheet!
the firmware has wifi direct named as all share!!!!!!...........lol

It is not the same
look at this video to understand what we mean
http://www.youtube.com/watch?v=gCEawDprnOQ

mylove90 said:
It is not the same
look at this video to understand what we mean
http://www.youtube.com/watch?v=gCEawDprnOQ
Click to expand...
Click to collapse
It's just like quick setup or PBS feature. The speeds are nothing special. Standard Wan Speeds. Should be possible on Wave.

Are you sure about Wave don't supporting NFC? I read somewhere that Wave has this chip. What about gold pins next to case opening button?

NFC is definitely not there, still unclear about Wi-Fi direct.

Bluetooth 4.0 ??

I am looking to purchase one of those new Fitbit Flex bands and i saw that it only does android devices that support bluetooth 4.0. On there website it seems like the only phones they have is galaxy 3 and note 2. Is there anyway for us galaxy nexus owners to get bluetooth 4.0??

Adding Bluetooth 4.0 support into the Galaxy Nexus would require an hardware change. There's no way to add support as a software/firmware update.
It would be like asking to transform a USB mouse into a wireless mouse. The required hardware just isn't present in the wired mouse to easily do it.
Bluetooth 4.0 can be made backward-compatible, as it can contain classic bluetooth connectivity and offers two additional operation modes: Bluetooth High Speed and Bluetooth Low Energy.
If your host device isn't Bluetooth 4.0 compliant and the device that is connecting is compliant with dual mode implementation, it will attempt to make a classic Bluetooth connection (obviously without the new features like either High Speed or Low Energy modes).
I would suggest finding out which Bluetooth 4.0 implementation mode the Fitbit Flex was used (single mode or dual-mode). If it is made with Bluetooth 4.0 dual-mode, you'll be able to use it with your Galaxy Nexus. If not, you'll have to wait until you upgrade your device to a Bluetooth 4.0-compliant model.

m-p{3} said:
Adding Bluetooth 4.0 support into the Galaxy Nexus would require an hardware change. There's no way to add support as a software/firmware update.
It would be like asking to transform a USB mouse into a wireless mouse. The required hardware just isn't present in the wired mouse to easily do it.
Click to expand...
Click to collapse
After doing some searching it seems to be because google is too lazy to help us out at the moment. IT IS POSSIBLE and doesnt require hardware change, just drivers. Which then makes me think..Im surprised all these guys on XDA cant make a driver, but im not exactly sure what that entails so im sure its harder than it sounds.
http://code.google.com/p/android/is...rs&colspec=ID Type Status Owner Summary Stars

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Bump...Any news?

Samsung Watch Active Bluetooth & connectivity questions

I just purchased the Galaxy Watch Active and have a few questions about Bluetooth & wireless connectivity. I hope someone can share their experience with me.
1. Should the watch always be connected to Bluetooth on my phone? Or, only connected when I want to sync to S-Health, install a new watch face, et. al.?
2. If I desire to connect my phone to another Bluetooth device (Ticpods, speaker), must I disconnect from the watch?
Q: Is this standard practice?
--- Yes, I can connect 2 devices to my Note9 but curious if there are any connectivity implications with both devices connected.
(I am thinking in terms of Fitbit Versa where phone Bluetooth is not connected(from what I could tell) even though FB Versa shows as choice in Bluetooth devices.)
3. I have not set up wireless yet and will do so this evening when home.
Q: What are the different use cases for Wireless vs. Bluetooth on the SWA?
FYI - I am an XDA old-timer but a newbie to this watch. Your feedback is appreciated.
Thanks in advance.
~j

johninsf said:
I just purchased the Galaxy Watch Active and have a few questions about Bluetooth & wireless connectivity. I hope someone can share their experience with me.
1. Should the watch always be connected to Bluetooth on my phone? Or, only connected when I want to sync to S-Health, install a new watch face, et. al.?
2. If I desire to connect my phone to another Bluetooth device (Ticpods, speaker), must I disconnect from the watch?
Q: Is this standard practice?
--- Yes, I can connect 2 devices to my Note9 but curious if there are any connectivity implications with both devices connected.
(I am thinking in terms of Fitbit Versa where phone Bluetooth is not connected(from what I could tell) even though FB Versa shows as choice in Bluetooth devices.)
3. I have not set up wireless yet and will do so this evening when home.
Q: What are the different use cases for Wireless vs. Bluetooth on the SWA?
FYI - I am an XDA old-timer but a newbie to this watch. Your feedback is appreciated.
Thanks in advance.
~j
Click to expand...
Click to collapse
1 Always connected to BT so you get notifications etc. 24/7
2 No need to disconnect when using other devices.
3 A lot ppl don't seem to like WiFi and call it useless. I am not too sure. IDK Can't do much without BT.

Dixon Butz said:
1 Always connected to BT so you get notifications etc. 24/7
2 No need to disconnect when using other devices.
3 A lot ppl don't seem to like WiFi and call it useless. I am not too sure. IDK Can't do much without BT.
Click to expand...
Click to collapse
Thank you for the feedback!