Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minimal viable Android app #2231

Closed
12 of 14 tasks
brussee opened this issue May 24, 2016 · 21 comments
Closed
12 of 14 tasks

Minimal viable Android app #2231

brussee opened this issue May 24, 2016 · 21 comments
Assignees
Milestone

Comments

@brussee
Copy link
Member

brussee commented May 24, 2016

  • Search results
  • Click to stream
  • Record video
  • Extract thumbnail
  • Create My Channel
  • Add to My Channel

Performance experiments:

  • Startup time
  • Cpu usage during idle, tunnels, download, streaming (HD)
  • Search results response time
  • REST API benchmark
  • Multichain record creation cost
  • Code coverage
  • CProfiler 10 min. run
  • Publish content 1 to 10 devices
@synctext
Copy link
Member

synctext commented Sep 9, 2016

  • Coming 3 weeks: finish 3 thesis chapters...
  • Then minimal viable product: VLC playback.
  • Launch Beta
  • Measure & experiment

@synctext
Copy link
Member

synctext commented Oct 20, 2016

Progress with app, now VLC integration is complete. Search results are fast and responsive. Plus: channel subscribe via phone pairing (NFC) is operational and tested.

Shown above are the sub-second search results from Tribler network (if you have a premium phone).
screenshot_20161020-164140
Great progress is the bundeling of VLC. Not as a hard to maintain library, but simply a bundled .APK within the overall Tribler.apk

@synctext
Copy link
Member

synctext commented Oct 20, 2016

Key experiment: content dissemination experiment with a several phones.

Graph: time on X-axes, Y-axes number of phones which received the content. Timepoint 0: file added at source.

  • 1 phone has channel.
  • 10 phones get subscribed to the same channel
  • continuously add file to source phone (10+ swarms in seconds)
  • see them appear at the various screens with a refresh

Todo next week:

  • describe experiment above with content dissemination. 1 photo of the phones "experimental setup".
  • Graph with fake data.
  • Startup time of Tribler also briefly Youtube (same hardware clean slate). Include log snippits in thesis (code quote style). Real data + graph + text of experiment: what you did and results. Repeat 10-ish time or so for accuracy; on 2 phone models. Graph bar chart with certainty intervals (1 bar Nexus 5, 1 bar Nexus 6).
    Split: Java GUI, Core started (known variance).
  • describe multichain experiment !

@synctext
Copy link
Member

Please focus on .tex for existing Multichain experiment results.

@synctext
Copy link
Member

synctext commented Nov 1, 2016

@informusica
Copy link

Reference on social media and the news: http:https://www.digitalnewsreport.org/

@informusica
Copy link

informusica commented Nov 2, 2016

  • placeholders for each new shadow chapter
  • 10 times power on of devices => logs
  • multichain graphs => 3 graphs
  • migrate only those results that are concretely there
  • make new design chapter in terms of functionality. No bullets but text!
  • for chapters with unstructured content, reshuffle content WITHOUT REWRITING OR ADDING CONTENT.
  • if all this is done, refer back to your draft scratch pad and migrate non-covered content to appropriate chapters

@brussee
Copy link
Member Author

brussee commented Nov 3, 2016

  • placeholders for each new shadow chapter
  • 10 times power on of devices => logs
  • multichain graphs => 3 graphs
  • migrate only those results that are concretely there
  • make new design chapter in terms of functionality. No bullets but text
  • for chapters with unstructured content, reshuffle content WITHOUT REWRITING OR ADDING CONTENT.
  • if all this is done, refer back to your draft scratch pad and migrate non-covered content to appropriate chapters

@informusica
Copy link

@synctext some now-backlog items that may ultimately be expanded, but only if time allows, and not before halfway November:

  • power on / power off timings: script is available to assess more than 10 runs
  • power on / power off timings: currently using time.time() rather than device time. That would need some programming (parsing) to resolve though. Only touch if time and supervisor allow. :)

@informusica
Copy link

informusica commented Nov 3, 2016

For this weekend: do not delete anything you typed and write blindly

  • new design chapter: no bullets but text. Sync with very first post in this issue thread w.r.t. functionality.
  • migrate non-covered content from draft.tex to appropriate chapters. Note that content in draft.tex may implicitly indicate your thoughts on relevant highlights of the work. Use that ultimately as a filter.
  • migrate non-bullets from old thesis
  • results: put figures in the *.tex. Explain rationale of test, used metrics, setup, results, again not in bullets but in text.
  • fill in further details in chapters but not in bullets.
  • for chapters with unstructured content, reshuffle content WITHOUT REWRITING OR ADDING CONTENT.

@synctext
Copy link
Member

@synctext
Copy link
Member

Final experiment:

  • Finished video recording, time is 0
  • Create torrent latency
  • Add torrent to channel
  • Arrived at phone 1 to 4

@synctext
Copy link
Member

synctext commented Nov 15, 2016

Title brainstorm: "attack-resilient media using phone-to-phone networking"

To Add: The implementation consists of 12,125 lines of code. Table X shows the 25 largest source file contributions for this thesis work. ... X lines (55 %) consists of unit testing code, Y lines (15%) is made up of Android specific libraries, and the remainder is..

279  android/TriblerApp/app/build.gradle  
166  android/TriblerApp/app/src/main/AndroidManifest.xml
141  android/TriblerApp/app/src/main/java/org/kamranzafar/jtar/Octal.java

Possible additional experiment: measure transfer time between various phones of 25MB clips or show power consumption during phone-to-phone exchange (max 1 day experiment).

@brussee brussee mentioned this issue Nov 19, 2016
4 tasks
@synctext
Copy link
Member

synctext commented Nov 19, 2016

Latest results of weekend work by hard working student. Scenario is manual transfer between phones + fast spreading if there is some networking:
phone-to-phone_networking

Here you can see how fast a video spreads between a bunch of Internet-connected phones. This is just our initial run, without any optimizations. Likely potential is that it can reach a worldwide audience of millions within 1 minute, without any servers or video support infrastructure. Purely a phone-to-phone overlay network.

performance_of_phone-to-phone_networking

@synctext
Copy link
Member

@qstokkink qstokkink added this to the Backlog milestone Nov 27, 2018
@qstokkink
Copy link
Contributor

This thesis has long since been completed.

@ProphetZarquon
Copy link

It looks like the Android version hasn't been updated in five years. Is an Android app no longer in active development? Android has more devices active than Windows 10, & recent Android versions constitute a significant percentage of active devices overall. Considering the sizable resources & connectivity available on many Android devices, I would expect development of an Android version to be a high priority for any software project hoping to improve global connectivity & freedom of communication.

Is there some Tribler package for Android that I'm not seeing, or has that branch been abandoned for some reason? If so, why?

@synctext
Copy link
Member

synctext commented Feb 1, 2019

True, Android app would reach a massive audience.

Sadly we are a non-profit project without the resources needed to do a good app currently. Our focus is on the desktop and build a thriving community there first.

@qstokkink
Copy link
Contributor

Is there some Tribler package for Android that I'm not seeing,

Yes, we have expanded upon this PR and are still working on several apps. However these are for specialized use cases such as just the passport logic or just the market logic. Now that we have trimmed the fat off Tribler a bit, we can start looking at running the full Tribler stack on Android again.

@synctext
Copy link
Member

All activity now moved here #4827.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants