AbelTong / funf-open-sensing-framework

Automatically exported from code.google.com/p/funf-open-sensing-framework
0 stars 0 forks source link

Bluetooth and wifi on phone devices stopped working #109

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. On the create app web page, http://inabox.funf.org/create/, check the check 
box next to Bluetooth in the Positioning section. Also input "60" for both 
fields next to Bluetooth. Create the app and install on phone.

2. Manually go to the wifi settings in the phone and turn on wifi then connect 
to a network. Keep the wifi on.

What is the expected output? What do you see instead?
The expected output: the bluetooth icon in the upper right corner of the phone 
would appear and disappear every 60 seconds. Also the wifi icon would stay on.

Actual output: the bluetooth icon does not appear and disappear. Also the wifi 
icon doesn't appear. 

When the created app first launch, it does what its suppose to do and the wifi 
connects to a network. But after about 4-8 hours, the bluetooth and wifi 
failed. I went to the phones settings to try to turn on the bluetooth and wifi, 
but the phone just wouldn't turn them on. They both stay on the off state.

What version of the product are you using? On what operating system?
Version: I created the app a few days ago from the create website.
Operating system: Android 4.2.2

Please provide any additional information below.
These are the phones I installed the app on:

Cubot C11 Android 4.2 Smartphone 
(http://www.gadgetsdealer.com/product557047.html)

H3038 Android 4.2 Smartphone (http://www.gadgetsdealer.com/product552772.html)

S20i Android 4.2 3G Phablet (http://www.gadgetsdealer.com/product557055.html)

DOOGEE DG120 Android 4.2 3G Smartphone 
(http://www.gadgetsdealer.com/product570533.html)

I just want to know why the bluetooth and wifi failed. Is it because of the app 
or the phone's hardware?

Any sugguestion or comment is welcome. Thanks.

Original issue reported on code.google.com by andy.pen...@gmail.com on 1 Dec 2013 at 2:26