Update the README.md

Colors:

• gray? when not connected to RPI over Bluetooth
• green when RPI is having a working Inet connection
• red when RPI is offline

Big question is ...
how often would update this signal?

We should bea ble to run pirateship commands

we should add a way to lint before commit

generally wonder if there is a Android Studio something
or we have to add something else

Description:
Whenever you try to use the "ping" command to test for the pi network connection. By the time the command is executed, there is no way to stop it. For the computer, you can use "Ctrl + C" to stop the command. But for the pi, since we cannot do "Ctrl + C", there is no way to stop the pinging process.

Solution:

1. We can add more command as an option to stop the ping. For example, kill the process after 5 seconds. Ex: "ping -w 5 8.8.8.8"
2. Create a manual for the user, telling them some commands are not supported.

Conclusion:
With that being said, please be careful when using some other commands that have the similar effect until we come up with a solution.

We should find a way to refactor this file, you can see some of the issues here.

https://codeclimate.com/github/treehouses/remote/app/src/main/java/io/treehouses/remote/BluetoothChatFragment.java?strict=false&to_sha=54c0622af77f9220c493ef6be1f1b8f3919c0e74

User interface (Make Hotspot dialog) needs to show an error for 8 characters or less (greater than 0) when typing in a password.

Using https://crowdin.com/project/take-home

the current regex that validate the command on the raspberry pi side is somewhat "strict". It might limit the commands we could send on the remote side.

Related to #22
Same as ole-vi/bluetooth-server#1

I don't know how the script work. But when I try to send this string "pirateship wifi nameHere passwordHere", it said that the command is not supported. On the other hand, this command will work "{"SSID":"namehere","PWD":"passwordhere"}". Does any vi here have any idea? Please feel free to share your opinion.

Add a small icon in the app header so that it displays the icon in the header or as a watermark in the xml file

• but we would like to be detected as computer
• multiple Androids to be able to connect

Currently only have it in the cmd screen, but do we want to have it in the home screen, or rather every screen(layout)?

Preparation:

• Pi is not connected to the Internet via Ethernet cable.
• Pi doesn't have WiFi already config.
• Initial "/etc/wpa_supplicant/wpa_supplicant.conf":

network={
      ssid=""
      #psk=""
      psk=(unknown)
}

• Initial "ifconfig":

=> Notice that there isn't any "WLan0"

• Phone is not connected to WiFi.

Scenario/Steps:

1. Connect your app with the Pi.
2. Click on the "Laptop" icon.
   
3. A pop-up will appear. You should fill in your "SSID" and "Password"
4. When the Pi is successfully with WiFi config. It will disconnect with the app.
   

Cause

A theory made by Dogi, he said that because the WiFi and the Bluetooth is using the same antenna. When we finished configuration the WiFi; since it is borrowing the WiFi antenna, we got disconnected with the Bluetooth. With that being said, what do other vi think of this issue?

When the device's display setting font is set to large, the title clips and isn't very readable.

Polaroid 7" Tablet
Model Number: P7100
Height: 7-1/4 inch
Width: 5 inch
Android Version: 7.1.2

Automatically deploy apk in travis to github release

Provide a screen shot / skeleton of current app for graphic designers to design / redesign the effort using required color coding.

Whenever you change from portrait view to landscapes view, the app disconnected with the RPi. I don't know if this issue occur to everybody else, but this issue happened to me.

As the title suggest, we need to remove and refactor some of our newest code.

Update: Here are some of the problems that this branch is facing:

• ProgressDialog is running indefinitely (Problem 1)
• Crash when using PirateshipActivity (Problem 2)
• ProgressDialog showing up when you click connect to a device -> the space outside of choosing a device (Problem 3)

User story

As a user, I would like to be able to expand the partition on the RPI image to the maximum of the SDcard

Acceptance criteria

• Click the "Expand Filesystem" button
• Sends the "expandfs" command

Noticed some inconsistency on the style of code in the repo. if (, if( seems to be used at different places.

Tbutton, Dbutton, Vbutton etc. also does not look like easy to understand names.

every treehouses image has a version (e.g. release number) which gets stored in
cat /boot/version.txt

I recently started the process of getting myself connected to the RBi3. From my adventures, I have done a lot of different things to try and get our remote app working with the RBi, and I thought I should document the things that need to be done to get it working. We should try and finds ways to avoid this process to simplify the connection steps.

Img: treehouse-44.img
Android Device: Galaxy s7
Pi: RBi3

My Bluetooth connection was not stable. I would be able to pair my device with the RBi but it would never stay connected.

Is there something i am missing? what steps have you used to get your Android device connected and stable to treehouse .img RBi?

Sometimes we have to manually go into bluetoothctl and use discoverable on pairable on

timeout issue?

Same as treehouses/builder#239

Automatically deploy apk in travis to github release

11-15 18:15:08.779 W/BroadcastQueue(773): Permission Denial: receiving Intent { act=android.bluetooth.device.action.FOUND flg=0x10 (has extras) } to ProcessRecord{9fc1db4 13809:com.example.yubo.bluepi/u0a328} (pid=13809, uid=10328) requires android.permission.ACCESS_COARSE_LOCATION due to sender com.android.bluetooth (uid 1002)

Some googling shows that with targetSdkVersion 23 or higher, the app needs to request ACCESS_COARSE_LOCATION permission from user on Android 6.0+.

Workaround is to pair with raspberry pi on the phone's Bluetooth settings, then come back and pick the already paired raspberry pi in the popup.

Problem

"Start Configuration" is not disabled under certain circumstances

Steps to reproduce

1. Type in more than one characters in SSID field
2. Type in less than 9 characters in password field
3. remove one character in SSID field

Displaying the hardware version in the header of the app beside "Connected to raspberry pi" so that it shows like "Connected to raspberry pi 3 Model B Rev 1.2"

Make it so when design issues gets merged, app doesn't crash when running on a tablet.

For example, when someone runs the app on a tablet, it crashes. However, it works fine on a phone.

I am getting this error box when I try to connect my android galaxy s7 device to my RBpi 3.

treehouses password <password> change the password for `pi` user

User story

As a user, I would like to be able to change the password of the Raspberry Pi's pi user

Acceptance criteria

• click on the Change pi user password button, a dialog appears.
• the dialog asks for the new password
  • The dialog would look something similar to this
  • in the lower right corner of dialog, Submit should be grayed out if there's nothing in the new password filed
• after the user click on submit, the command treehouses password <newpassword> should be sent to Raspberry Pi.

More...

• should we use chpasswd directly instead of through treehouses/pirateship?

Perhaps adding a login / checking the app

I think we need to start adding some testing. A lot of different functions and methods are getting implemented without testing. I would like to compile a list of test we can do in this issue:

• Wifi Password format:
• Wifi name format
• etc.

The app gets crashed when trying to run on a Virtual Device.

02-08 17:59:11.263 2383-2383/? E/AndroidRuntime: FATAL EXCEPTION: main
   Process: io.treehouses.remote, PID: 2383
   java.lang.RuntimeException: Unable to start activity ComponentInfo{io.treehouses.remote/io.treehouses.remote.MainActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.bluetooth.BluetoothAdapter.isEnabled()' on a null object reference
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2416)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2476)
       at android.app.ActivityThread.-wrap11(ActivityThread.java)
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1344)
       at android.os.Handler.dispatchMessage(Handler.java:102)
       at android.os.Looper.loop(Looper.java:148)
       at android.app.ActivityThread.main(ActivityThread.java:5417)
       at java.lang.reflect.Method.invoke(Native Method)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
    Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.bluetooth.BluetoothAdapter.isEnabled()' on a null object reference
       at io.treehouses.remote.BluetoothChatFragment.onStart(BluetoothChatFragment.java:136)
       at android.support.v4.app.Fragment.performStart(Fragment.java:2369)
       at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1458)
       at android.support.v4.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1740)
       at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1809)
       at android.support.v4.app.FragmentManagerImpl.dispatchStateChange(FragmentManager.java:3217)
       at android.support.v4.app.FragmentManagerImpl.dispatchStart(FragmentManager.java:3176)
       at android.support.v4.app.FragmentController.dispatchStart(FragmentController.java:203)
       at android.support.v4.app.FragmentActivity.onStart(FragmentActivity.java:562)
       at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1237)
       at android.app.Activity.performStart(Activity.java:6253)
       at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2379)
       at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2476) 
       at android.app.ActivityThread.-wrap11(ActivityThread.java) 
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1344) 
       at android.os.Handler.dispatchMessage(Handler.java:102) 
       at android.os.Looper.loop(Looper.java:148) 
       at android.app.ActivityThread.main(ActivityThread.java:5417) 
       at java.lang.reflect.Method.invoke(Native Method) 
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726) 
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

Sometime we send a command and get "returns nothing", then the actual result show up after we send the next command.

In extreme case it's postponed by two commands.
screenshot 0
screenshot 1
screenshot 2

Duplicate of ole-vi/bluetooth-server#2

I noticed that we don't have a disconnect button for the user to use. Because at some point the user will want to disconnect the pi. With that being said, what do other vi think of this implementation? Do we really need to have a disconnect button?

pirateship staticwifi <ip> <mask> <gateway> <dns>

https://developer.android.com/training/material/index.html

Both Dashboard.java and pirateship.java will use this class to handle messages.