(click to expand) Build your own docker image:
- -> Note: this approach is only necessary if you would like to build an older or very custom version of al-folio. - -Build and run a new docker image using: - -```bash -$ docker-compose -f docker-local.yml up -``` - -> If you want to update jekyll, install new ruby packages, etc., all you have to do is build the image again using `--force-recreate` argument at the end of previous command! It will download ruby and jekyll and install all ruby packages again from scratch. - -(click to expand) Manual deployment to GitHub Pages:
- -If you need to manually re-deploy your website to GitHub pages, go to Actions, click "Deploy" in the left sidebar, then "Run workflow." - -(click to expand) Deployment to another hosting server (non GitHub Pages):
- -If you decide to not use GitHub Pages and host your page elsewhere, simply run: - -```bash -$ bundle exec jekyll build --lsi -``` - -which will (re-)generate the static webpage in the `_site/` folder. -Then simply copy the contents of the `_site/` directory to your hosting server. - -**Note:** Make sure to correctly set the `url` and `baseurl` fields in `_config.yml` before building the webpage. If you are deploying your webpage to `your-domain.com/your-project/`, you must set `url: your-domain.com` and `baseurl: /your-project/`. If you are deploying directly to `your-domain.com`, leave `baseurl` blank. - -(click to expand) Deployment to a separate repository (advanced users only):
- -**Note:** Do not try using this method unless you know what you are doing (make sure you are familiar with [publishing sources](https://help.github.com/en/github/working-with-github-pages/about-github-pages#publishing-sources-for-github-pages-sites)). This approach allows to have the website's source code in one repository and the deployment version in a different repository. - -Let's assume that your website's publishing source is a `publishing-source` subdirectory of a git-versioned repository cloned under `$HOME/repo/`. -For a user site this could well be something like `$HOME/- **A:** Yes, if you are using release `v0.3.5` or later, the website will automatically and correctly re-deploy right after your first commit. - Please make some changes (e.g., change your website info in `_config.yml`), commit, and push. - Make sure to follow [deployment instructions](https://github.com/alshedivat/al-folio#deployment) in the previous section. - (Relevant issue: [209](https://github.com/alshedivat/al-folio/issues/209#issuecomment-798849211).) - -2. **Q:** I am using a custom domain (e.g., `foo.com`). - My custom domain becomes blank in the repository settings after each deployment. - How do I fix that?
- **A:** You need to add `CNAME` file to the `master` or `source` branch of your repository. - The file should contain your custom domain name. - (Relevant issue: [130](https://github.com/alshedivat/al-folio/issues/130).) - -3. **Q:** My webpage works locally. - But after deploying, it is not displayed correctly (CSS and JS is not loaded properly). - How do I fix that?
- **A:** Make sure to correctly specify the `url` and `baseurl` paths in `_config.yml`. - Set `url` to `https://
- **A:** Make sure to correctly specify the `url` and `baseurl` paths in `_config.yml`. - RSS Feed plugin works with these correctly set up fields: `title`, `url`, `description` and `author`. - Make sure to fill them in an appropriate way and try again. - -5. **Q:** My site doesn't work when I enable `related_blog_posts`. Why?
- **A:** This is probably due to the [classifier reborn](https://github.com/jekyll/classifier-reborn) plugin, which is used to calculate - related posts. If the error states `Liquid Exception: Zero vectors can not be normalized...`, it means that it could not calculate related - posts for a specific post. This is usually caused by [empty or minimal blog posts](https://github.com/jekyll/classifier-reborn/issues/64) - without meaningful words (i.e. only [stop words](https://en.wikipedia.org/wiki/Stop_words)) or even - [specific characters](https://github.com/jekyll/classifier-reborn/issues/194) you used in your posts. Also, the calculus for similar posts are - made for every `post`, which means every page that uses `layout: post`, including the announcements. To change this behavior, simply add - `related_posts: false` to the front matter of the page you don't want to display related posts on. - -## Features - -### Publications - -Your publications' page is generated automatically from your BibTex bibliography. -Simply edit `_bibliography/papers.bib`. -You can also add new `*.bib` files and customize the look of your publications however you like by editing `_pages/publications.md`. - -
(click to expand) Author annotation:
- -In publications, the author entry for yourself is identified by string array `scholar:last_name` and string array `scholar:first_name` in `_config.yml`: - -```yaml -scholar: - last_name: [Einstein] - first_name: [Albert, A.] -``` - -If the entry matches one form of the last names and the first names, it will be underlined. -Keep meta-information about your co-authors in `_data/coauthors.yml` and Jekyll will insert links to their webpages automatically. -The co-author data format in `_data/coauthors.yml` is as follows, - -```yaml -"Adams": - - firstname: ["Edwin", "E.", "E. P.", "Edwin Plimpton"] - url: https://en.wikipedia.org/wiki/Edwin_Plimpton_Adams - -"Podolsky": - - firstname: ["Boris", "B.", "B. Y.", "Boris Yakovlevich"] - url: https://en.wikipedia.org/wiki/Boris_Podolsky - -"Rosen": - - firstname: ["Nathan", "N."] - url: https://en.wikipedia.org/wiki/Nathan_Rosen - -"Bach": - - firstname: ["Johann Sebastian", "J. S."] - url: https://en.wikipedia.org/wiki/Johann_Sebastian_Bach - - - firstname: ["Carl Philipp Emanuel", "C. P. E."] - url: https://en.wikipedia.org/wiki/Carl_Philipp_Emanuel_Bach -``` - -If the entry matches one of the combinations of the last names and the first names, it will be highlighted and linked to the url provided. - -(click to expand) Buttons (through custom bibtex keywords):
- -There are several custom bibtex keywords that you can use to affect how the entries are displayed on the webpage: - -- `abbr`: Adds an abbreviation to the left of the entry. You can add links to these by creating a venue.yaml-file in the _data folder and adding entries that match. -- `abstract`: Adds an "Abs" button that expands a hidden text field when clicked to show the abstract text -- `arxiv`: Adds a link to the Arxiv website (Note: only add the arxiv identifier here - the link is generated automatically) -- `bibtex_show`: Adds a "Bib" button that expands a hidden text field with the full bibliography entry -- `html`: Inserts an "HTML" button redirecting to the user-specified link -- `pdf`: Adds a "PDF" button redirecting to a specified file (if a full link is not specified, the file will be assumed to be placed in the /assets/pdf/ directory) -- `supp`: Adds a "Supp" button to a specified file (if a full link is not specified, the file will be assumed to be placed in the /assets/pdf/ directory) -- `blog`: Adds a "Blog" button redirecting to the specified link -- `code`: Adds a "Code" button redirecting to the specified link -- `poster`: Adds a "Poster" button redirecting to a specified file (if a full link is not specified, the file will be assumed to be placed in the /assets/pdf/ directory) -- `slides`: Adds a "Slides" button redirecting to a specified file (if a full link is not specified, the file will be assumed to be placed in the /assets/pdf/ directory) -- `website`: Adds a "Website" button redirecting to the specified link -- `altmetric`: Adds an [Altmetric](https://www.altmetric.com/) badge (Note: if DOI is provided just use `true`, otherwise only add the altmetric identifier here - the link is generated automatically) -- `dimensions`: Adds a [Dimensions](https://www.dimensions.ai/) badge (Note: if DOI or PMID is provided just use `true`, otherwise only add the Dimensions' identifier here - the link is generated automatically) - -You can implement your own buttons by editing the bib.html file. - -
-
-
-
-
- 
-
-
- {% for user in site.data.repositories.github_users %}
- {% include repository/repo_user.html username=user %}
- {% endfor %}
-
-{% endif %}
-
-
-{% if site.repo_trophies.enabled %}
-{% for user in site.data.repositories.github_users %}
- {% if site.data.repositories.github_users.size > 1 %}
- {{ user }}
- {% endif %} -
- {% include repository/repo_trophies.html username=user %}
-
-{% endfor %}
-{% endif %}
-
-
-{% if site.data.repositories.github_repos %}
-
- {% for repo in site.data.repositories.github_repos %}
- {% include repository/repo.html repository=repo %}
- {% endfor %}
-
-{% endif %}
-```
-
-#### Theming
-
-A variety of beautiful theme colors have been selected for you to choose from.
-The default is purple, but you can quickly change it by editing the
-`--global-theme-color` variable in the `_sass/_themes.scss` file.
-Other color variables are listed there as well.
-The stock theme color options available can be found at `_sass/variables.scss`.
-You can also add your own colors to this file assigning each a name for ease of
-use across the template.
-
-#### Social media previews
-
-**al-folio** supports preview images on social media.
-To enable this functionality you will need to set `serve_og_meta` to `true` in your `_config.yml`.
-Once you have done so, all your site's pages will include Open Graph data in the HTML head element.
-
-You will then need to configure what image to display in your site's social media previews.
-This can be configured on a per-page basis, by setting the `og_image` page variable.
-If for an individual page this variable is not set, then the theme will fall back to a site-wide `og_image` variable, configurable in your `_config.yml`.
-In both the page-specific and site-wide cases, the `og_image` variable needs to hold the URL for the image you wish to display in social media previews.
-
-#### Atom (RSS-like) Feed
-
-It generates an Atom (RSS-like) feed of your posts, useful for Atom and RSS readers.
-The feed is reachable simply by typing after your homepage `/feed.xml`.
-E.g. assuming your website mountpoint is the main folder, you can type `yourusername.github.io/feed.xml`
-
-#### Related posts
-
-By default, there will be a related posts section on the bottom of the blog posts.
-These are generated by selecting the `max_related` most recent posts that share at least `min_common_tags` tags with the current post.
-If you do not want to display related posts on a specific post, simply add `related_posts: false` to the front matter of the post.
-If you want to disable it for all posts, simply set `enabled` to false in the `related_blog_posts` section in `_config.yml`.
-
-## Contributing
-
-Contributions to al-folio are very welcome!
-Before you get started, please take a look at [the guidelines](CONTRIBUTING.md).
-
-If you would like to improve documentation, add your webpage to the list below, or fix a minor inconsistency or bug, please feel free to send a PR directly to `master`.
-For more complex issues/bugs or feature requests, please open an issue using the appropriate template.
-
-### Maintainers
-
-Our most active contributors are welcome to join the maintainers team.
-If you are interested, please reach out!
-
-
-
-
- Maruan |
-  Rohan Deb Sarkar |
-  Amir Pourmand |
-  George |
-
Because recent Google Play system update (June 1, 2024) blocks the network requests to the virtual IP address through personal hotspot. We have to adapt more complicate solution to mirror phone screen to Tesla. This page will show the best solutions we can find out so far.
+ +### Check app version first +The version of Tesla Display app must newer than 5.26
+ +### Solution A (only effective to a subset of users) +If the internal IP address your mobile phone obtains from the mobile carrier happens to be outside the range prohibited by the Tesla browser, the solution is easy.
+1. Check the "Disable SSL" option on the setting tab
+2. Tap the "start" button, choose "Phone screen"
+3. If you see an address that is NOT http://7.7.7.7:7000, it means Tesla browser can access that address after Tesla is connected to the personal hotspot of your phone.
+ +### Solution B (require two Android phones) +If Solution A cannot work for you, you can try Solution B.
+Solution B requires two Android phones.
+One phone is the phone we want to mirror its screen to Tesla, which has installed the latest Google Play system update. We call it the new phone.
+The other phone must not install the Google Play system update after June 1, 2024. We call it the old phone. If the old phone can enable personal hotspot without SIM card, you only need one SIM card on your new phone to access internet.
+Network connection:
+The new phone turns on cellular data, and enables the personal hotspot "WIFI N".
+The old phone is connected to "WIFI N", and enables the personal hotspot "WIFI O".
+Your Tesla vehicle is connected to "WIFI O".
+App operations:
+1. On the new phone, launch Tesla Display app, check the "Disable SSL" option on the setting tab, tap the "start" button, choose "Phone screen"
+2. On the old phone, launch Tesla Display app, tap the "start" button, choose "Forward another phone screen"
+3. On Tesla browser, access https://td7.cc to see the screen of the new phone
+Hints:
+a. The new phone must launch Tesla Display before the old phone
+b. To control directly on Tesla's touchscreen, you should enable "Control on touchscreen" on the new phone.
+c. The URL on Tesla browser should be URL shown in Tesla Display on the old phone.
+d. You must disable automatically system update of the old phone
+ +### Solution C (require a rooted Android phone) +Still on the way...
+ +## Technical support + + diff --git a/_pages/solution-for-new-update-en.md b/_pages/solution-for-new-update-en.md new file mode 100644 index 00000000..428d66d0 --- /dev/null +++ b/_pages/solution-for-new-update-en.md @@ -0,0 +1,48 @@ +--- +layout: page +permalink: /solution-for-new-update/ +title: Solutions for Android phones with recent Google Play system update? +description: If the date of Google Play system update on your phone is later than June 1, 2024, it will be more difficult to mirror your phone screen to Tesla with the Tesla Display app. +nav: false +nav_order: 1 +categories: tutorial +--- + + +## The problem +Because recent Google Play system update (June 1, 2024) blocks the network requests to the virtual IP address through personal hotspot. We have to adapt more complicate solution to mirror phone screen to Tesla. This page will show the best solutions we can find out so far.
+ +### Check app version first +The version of Tesla Display app must newer than 5.26
+ +### Solution A (only effective to a subset of users) +If the internal IP address your mobile phone obtains from the mobile carrier happens to be outside the range prohibited by the Tesla browser, the solution is easy.
+1. Check the "Disable SSL" option on the setting tab
+2. Tap the "start" button, choose "Phone screen"
+3. If you see an address that is NOT http://7.7.7.7:7000, it means Tesla browser can access that address after Tesla is connected to the personal hotspot of your phone.
+ +### Solution B (require two Android phones) +If Solution A cannot work for you, you can try Solution B.
+Solution B requires two Android phones.
+One phone is the phone we want to mirror its screen to Tesla, which has installed the latest Google Play system update. We call it the new phone.
+The other phone must not install the Google Play system update after June 1, 2024. We call it the old phone. If the old phone can enable personal hotspot without SIM card, you only need one SIM card on your new phone to access internet.
+Network connection:
+The new phone turns on cellular data, and enables the personal hotspot "WIFI N".
+The old phone is connected to "WIFI N", and enables the personal hotspot "WIFI O".
+Your Tesla vehicle is connected to "WIFI O".
+App operations:
+1. On the new phone, launch Tesla Display app, check the "Disable SSL" option on the setting tab, tap the "start" button, choose "Phone screen"
+2. On the old phone, launch Tesla Display app, tap the "start" button, choose "Forward another phone screen"
+3. On Tesla browser, access https://td7.cc to see the screen of the new phone
+Hints:
+a. The new phone must launch Tesla Display before the old phone
+b. To control directly on Tesla's touchscreen, you should enable "Control on touchscreen" on the new phone.
+c. The URL on Tesla browser should be URL shown in Tesla Display on the old phone.
+d. You must disable automatically system update of the old phone
+ +### Solution C (require a rooted Android phone) +Still on the way...
+ +## Technical support + +