OSCAR [mobile devices & cellular modem use]

[SarcasticDave94]

There ya go, Osi. That ought to help.

Sparky over n out.

[17WRX]

I understand the issues on cell networks but what about phones and tablets running off of a home wifi network? The same network macs and PC work on. Or is the issue with Andriod and IOS itself and not just the network?

[Osiris357]

I understand the issues on cell networks but what about phones and tablets running off of a home wifi network? The same network macs and PC work on. Or is the issue with Andriod and IOS itself and not just the network?

It’s Android and iOS, OSCAR isn’t compatible. Otherwise that would work with a WiFi SD card I would think

[Crimson Nape]

It sounds like you are confusing the ability to connect to the internet and executing machine code on a computer. All devices you mentioned connect to the internet or wireless signal, but to execute the OSCAR code doesn't require any external sources. The OSCAR code has to be specifically setup (compiled) for a particular operating system and processor. The later is currently not done for Android and iOS devices.

[Gideon]

Let's see if we can cover this.
Target, OSCAR running on a phone.

1. Communications, How to get data from xPAP to Phone.
   A. Cellular Data
       a. Legal issues.
       b. Wait for Vendors to include.
       c. Hack communications.
       d. Hack Data
   B. WIFI. 
       a. Wait for Vendors to include.
       b. Hack communications.
       c. Hack Data
   C. Bluetooth (as above)
2. Data design.
    How do we store data, where do we store it
3. Functional design.  
    What do we want it to do functionally?  
3. Design UI
    OSCAR has some pretty complicated graphics, How do we present it.
    Overall UI, we are working on improving OSCARs UI for a PC screen, how do we scale it and present it on a phone with its significantly less foot print.  

None of the above is trivial, and none of the OSCAR code can be used, though the concepts can.
While we know how to parse the data on the SD card, we do not know the form the data takes on various wireless forms of communication, many of which do not exist.

It may be possible to get data with a WiFi SD Card targeting a Phone directory.   Any takers to work on this.
Regardless, this is years away and is not being currently worked on.

[Osiris357]

Let's see if we can cover this.
Target, OSCAR running on a phone.

1. Communications, How to get data from xPAP to Phone.
   A. Cellular Data
       a. Legal issues.
       b. Wait for Vendors to include.
       c. Hack communications.
       d. Hack Data
   B. WIFI. 
       a. Wait for Vendors to include.
       b. Hack communications.
       c. Hack Data
   C. Bluetooth (as above)
2. Data design.
    How do we store data, where do we store it
3. Functional design.  
    What do we want it to do functionally?  
3. Design UI
    OSCAR has some pretty complicated graphics, How do we present it.
    Overall UI, we are working on improving OSCARs UI for a PC screen, how do we scale it and present it on a phone with its significantly less foot print.  

None of the above is trivial, and none of the OSCAR code can be used, though the concepts can.
While we know how to parse the data on the SD card, we do not know the form the data takes on various wireless forms of communication, many of which do not exist.

It may be possible to get data with a WiFi SD Card targeting a Phone directory.   Any takers to work on this.
Regardless, this is years away and is not being currently worked on.

I just saw this. I wish I had the knowledge to do all the above since we as a society are becoming more mobile based year after year. I should've stayed in school for networking and programming. I was too busy being a welder at that point. 

After seeing ResScan, OSCAR looks incredible! Other than a few of the functions needing to be more apparent for the technophobic , its ease of use and graphics are excellent! Keep up the good work guys!

[Finsternis]

I'm sorry to sound like a smartass, but y'all are missing the obvious solution. You need to think outside the box.

So, getting the data onto a tablet wirelessly would be a major pain. But that doesn't need to prevent you. Just remove one word from what you are trying to do. That word is "wirelessly."

Think about it carefully: How do you currently get your data to OSCAR on a PC? Do you do it wirelessly? No. You do it by removing the SD card from the CPAP and sticking it into your PC. Can you see where this is going? You need to add item 1D) to your online: "SD Card"

Hint: you can get a teeny USB SD card reader for $20 that will happily plug into your phone or tablet and transfer the exact same data files as you put on your PC.

Or, if you want to do it the long way: 1) copy files from SD Card to your PC as you do right now. Then 2) transfer them however you want (wifi, Bluetooth, magic pixie, tin can and string,, whatever) over to your tablet.

Data transfer problem = solved!

[pholynyk]

I think you missed Gideon's post - #15 above. Getting the data into the mobile device is only one of the items on his list. The other three items currently involve roughly 80,000 lines of code and headers, which would require rewriting to adapt to the mobile platform (which one?). The User Interface requires a completely new design to fit the comparatively small screen of a tablet, let alone a phone.

Considering the work (and eye strain) involved and the fact that OSCAR runs on a cheap Raspberry Pi, a Chromebook,or a laptop, the current team is unlikely to pursue a mobile implementation.

[Finsternis]

I think you missed Gideon's post - #15 above. Getting the data into the mobile device is only one of the items on his list. 

In a previous message Gideon said "The big issue is communications from the device. " It's all anyone talked about in the thread.  Iwas pointing out that it is not an issue, not saying that a port would be quick or easy. Just that the roadblock everyone was focused on is not a roadblock.

Of the 4 issues he raised, 3 of them have easy answers:

1) Use an SD Card reader on your tablet
2) Just do it the same way as the PC version
3) Just do it the same way as the PC version.

#4 is where the real work would be.  And as you say it probably will never happen beause porting UIs is hard. But 3/4 of the listed issues are not issues.

[Crimson Nape]

The post you reference was made 2 years ago. A lot of OSCAR development has transpired since then.