i read some post about platform-difference
but i can't solve my problem
i made network-program in bold9000 using 3G &wifi
in my bb9000
os version:5.0.0.509
platform 5.2.0.50
branding 1.0.114.308o
it works very well
but when my customer tested it in bold9000
os v5.0.0.681
platform 5.2.0.64
branding version 1.0.1180.265t.
at that situation
wifi works but 3G doesn't work
what's wrong with my phone ?
Every suggestion is appreciated
plz warm-answer ㅠ ㅠ
Software/App Version - Indicates the version of your applications (Address book, browser, calendar, also WiFi config wizard, etc.)
Platform/OS Version - Indicates your version of system software (Java base/core software, radio codes, etc.)
In what way doesn't the 3G not work? You can use 3G in calls? Is the .681 phone in the same infrastructure like the .509 phone? Possibly the one connects through BIS, one through BES?
Related
I use app tethering with Delphi between Android and Windows since Seattle and now with Tokyo 10.2.2 and it works quite well across WLAN. The only problems arise from customers that sometime delete custom rules in the Windows firewall so that the devices cannot find each other anymore.
Because of that support effort I would like to additionally offer bluetooth between the two devices but I cannot get it up and running. The Embarcadero documentation is not very helpful either.
What I tried so far (based on the solution working with WLAN):
Bluetooth Pair the phone with the PC
Switch both sides from "Network" Protocol (what ist UDP Broadcast) to "Bluetooth"
Added a Bluetooth component on both sides and activated it (it has no more settings). Also doesnt work without it.
When closing the PC application I get an EBluetoothException saying "cannot establish connection" that's all.
The devices do not discover each other. Perhaps I am missing one important step. So if anyone has bluetooth app tethering up and running I would be grateful if he shared his experiences here!
Thanks!
I recently developed an application for a client, an app iOS, Android and windows, the mobile app acts as a controller and launches certain events on the windows application. The Windows application also shares data at random (not known to the mobile app) moments. The communication was done by TCP. And works great.
The client now wants it for bluetooth. Between Android and Windows, it's not been a problem and has been done, and works well. But iOS is sadly not the same story... The use of Bluetooth low energy seems to complicate things.
I've hunted high and low on google to find anything on communication between a .net application and a Swift application, to no avail. This surprises me that no one talks of a bluetooth communication between Windows and iOS.
My question is, very simply. Is it possible? I know very little about bluetooth and I've tried researching devices and all I find is a BeeWi device that's in our office, not my computer (I maybe need to launch something on computer first? The devices are paired)
My computer has a Bluetooth 4.0 dongle and the BLE emulator is present in the Device manager.
If this isn' possible, tell me know and put me out of my misery, otherwise give me hope!
Any additional advice is warmly welcome - Thank you all !
Beau Carrel
Windows has support for being a BLE client. Just Google it and you'll find many examples, such as https://developer.microsoft.com/en-us/windows/iot/Samples/BLEGatt2.
You need to set up iOS to be an advertising peripheral.
I updated iOS on my phone to 8.3 and I saw this message popup on first boot, but I have not seen it since:
I have been searching all day for information and I can't find a single reference to this message or to Xcode supporting wifi debug.
I am using a macbook pro 2009 model, and I have read that this is not compatible with the new continuity features (as well as airdrop etc). I am wondering if this is part of the wifi debug (and also if BTLE is involved at all). Of course it is all speculation since I cannot find any documentation about this.
Has anybody used wifi debug, or can point me to any documentation?
No, the feature was disabled as it causes serious security flows, for example when debugging you can fake location for any app, access confidential data like your number, udid etc. WiFi can be used now only to sync using iTunes.
It's restricted to USB only. You would need to write a bridge between USB and WiFi. You could in theory connect iPhone to Raspberry Pi, use open source crossplatform libMobileDevice. And mirror all USB requests from your XCode to this device USB.
I have an iPad that worked perfectly with my iPads with WiFi only environment. But It was rejected due to one of the function that I suspected that the cellular network has something to do with it. Currently, without the necessary resources to test in that environment, I want to target this app only for WiFi version of iPad. Does anyone know if we can submit a WiFi only version app for iPad?
Of course it's not possible, and it's not really reasonable. As a developer you want to have as large userbase as possible, so targeting only wifi iPad version would not serve you at all. Just test it thorougly on different device configurations, fix the bugs and submit again. If you have Mac OS X Lion, you could use Network Link Conditioner Utility for simulating lousy internet connection (3G/Edge). Don't underestimate the importance of testing on the real device though.
I develop and test applications for BlackBerry 4.5, 4.6, 4.7 and 5.0, but have done testing only with the respective simulators. Now I am about to buy a new BlackBerry device to test my applications better in a real scenario.
Can anyone suggest which device suits my needs?
Hi
I'm not sure about this model but i do know that in other cellphones you need to change the software version every time. Because you mentioned that you want to build apps for different OS versions.
You should try to locate a device that is the easiest one to change OS version and be able to downgrade and upgrade without any errors.
thanks
The current BB devices on the market are generally 5.x and up. You have to define a minimum version you'll support. As long as your app doesn't do too much hackery JDE versions are upwardly compatible.
Simulators generally model real devices well except for the networking. You see some differences especially GSM vs. CDMA devices. Ex. if you ask for the device's phone number (in the NAMP) it may or may not start with a 1.
If you're on a budget or decide to buy multiple devices you might want to try Curve 8520 - it's one of the cheaper new models, comes with BlackBerry OS 4.6 upgradable to 5.0, but still has most of the functionality you might need, except for the GPS.
Additionally it has one of the lower resolutions RIM has to offer (320x240), so if your apps are UI intensive you can see if they work well with entry level models.
Hope it's of any help.