Related
hello i have upgraded s health and s finder. s health is working with build prop modified..but s finder doesnt work..it has stopped.. there is a line to modify?
Try clearing the system cache from recovery mode and the app's cache and data from the application manager in the settings menu. There are dozens and dozens of threads about this if you need any elaboration.
Failing that, you need to provide a lot more information if you want good answers. At a minimum tell us exactly what changes you made to build.prop, what S5 model you have and what your firmware version you are using. And anything else that is even remotely pertinent e.g. verbatim error messages. It would also be in your best interests to do a search to take advantage of the wealth of information in existing threads and enable you to pose more informed questions.
.
Ok thanks. The wipes failed..I have followed this type: ro.securestorage.support=true” line.
Now change the line to “ro.securestorage.support=false . I have s5 gm900f and the firmware is ane2. The errore message is s finder unfortunately has stopped. I hope i have been Clear!
The purpose of this thread is to have all information regarding the Weloop Tommy, gathered, fresh and to the point.
(i am not affiliated with Weloop)
Please read both post number 1, 2 and search thread before asking questions thank you.
FAQ
Q:What is the latest firmware?
[Release] black watch v3.19 firmware update notifications [Copy link]
This update to the firmware update, the client does not update the current firmware version v3.18 firmware watches friends can try to use the old client detects the firmware update.
Update:
Solve watches restart, restore factory settings watches language will change.
Download Link:
iOS client 2.079: http://fir.im/iosobt
Android client 1.29.3702b: http://fir.im/andobt
Unofficial file archive of WeLoop Tommy. APK-Files with ending "b" are BETA http://www.wtf.li/
Q: When is the next app update
A: Weloop v. 3.0 will be released as closed beta 7the of March 2015 we don't know when there will be an open english release....
the extensive update 3.0 have,
better health monitoring
profiles
sleep monitoring
more alarms weekdays/weekend
and more.
(see attached pictures for app version 3.0 UI improvements
Q: What does the settings do?
- Backlight
24H: Backligth always turns on when button is pressed
Nite: Backligth turns on when button is pressed at night time (from 17–8)
Off: Backligth Always Off
- Motion
24H: Motion detection always on (backlight turns on when motion is detected)
Nite: Motion detection on at night time (from 17-8)
Off: Motion detection Off
- Night
On: Notification vibration disabled at night (from 23–8)
Off: Notification enabled at night
- O Clock
On: every whole hour the watch will vibrate. 12'O'clock etc.
Off: Off
- Fitness
On: Fitness functionality on
Off: Off
- Language
Chinese
English
- Anti Loss
On: Alarm when Phone is out of BT range
Off: Off
Q: Is there Cyrillic support
A: Yes
Q: The GoClever Ecos Chronos is the same watch right?
A: Yes it is on the hardware side, and you can with a "hack" install the firmware from the ECOS on the Tommy. (see next post for How to.!)
Awesome Weloop Review by VECTRON
http://forum.xda-developers.com/smartwatch/other-smartwatches/weloop-tommy-smartwatch-looks-best-t2864444
Troubleshooting
Q: i can not update my watch/its stuck/acting weird
Have you tried to reset the watch? there are 3 ways to do it
Restart watch from app. under update there is a restart button (it says reset but it restarts and keeps all your settings)
Reset from watch (Last menu point, this resets everything)
Hard reset (connect charge cable and press up and down button to reset)
Force OTA update:
Connect your watch to the charger. (watch must be charging)
Press all 3 buttons on the side simultaneously
Release the 2 side buttons, and keep the middle button pressed until you get the upgrade connecting display. (this might take some seconds)
Delete connection from phone
Connect and pair from app and upgrade
If you are on an Android device and it cannot connect, try an ios device, and vice versa
Q: The watch keeps switching back to chinese
More people have experienced that if the language is non english the watch will reset to chinese. Changing the phone OS to english stops the watch from switching to Chinese.
"Hacks"
How to make your own watchfaces:
user fcsabika has created a cool tool to create your own watchfaces
WeLoop Tommy Watchface Creator
attached are also some watchfaces made by user ruicoel filename "project rui.zip"
How To install GoClever Chronos ECO firmware on Weloop tommy (android only)
Download latest ECO firmware to phone
Disconnect Watch from phone, install ECO app
Go to “Check For Upgrade”
Tap on the middle circle six times
“Select a firmware file___ [Browse]”
Watch must be in forced OTA
Update watch.
You can flash between weloop and Goclever firmware (always be careful and follow instructions when flashing, i take no responsibility for bricked or exploding watches...)
To install weloop firnware, follow same instructions but use weloop app instead.
PROJECT OPEN FIRMWARE (please make sure you understand what this is and what it does before you attemtp to flash your watch)
Make a Weloop Tommy an open source sport watch that can be used without a mobile phone. Want to see a heart rate when running, cycling speed and cadence when cycling or number of laps while swimming? Help to make it possible! LINK
This project is divided into six phases:
Phase 1: find out and document watch pinout so it will be possible to communicate with screen, accelerometer and a flash memory from a custom firmware. DONE
Phase 2: write a custom firmware that will print sample text on a screen and expose a BLE service. Firmware will be flashed using SWD connector. DONE
Phase 3: make it possible to upload a custom firmware using OTA. This will save the waterproof case from destruction. DONE
Phase 4: update softdevice to the newest version (S110 8.0.0). Add possibility to switch to other softdevice (S120/S130) DONE
Phase 5: create a "terminal" firmware that allows to control what is displayed on a watch from an android/iOS app. IN PROGRESS
Phase 6: create a "standalone" firmware using S130 softdevice that can connect to external sensors (HRS, CSCS etc) without a phone. TODO
Go support developer Krzysiek
Goclever APK & FW file is attached to this post.
Latest Chronos ECO firmware 3.18
http://www.chronos.goclever.com:8080/fileServer/firmware/CHRONOSECO_V3.18_1.bin
Chronos ECO app (android)
https://play.google.com/store/apps/details?id=com.yf.foreign.goclever
Chronos ECO IOS app
https://itunes.apple.com/th/app/goclever-chronos-eco/id955306578?mt=8
BUGS & Annoyances
Notification not always deleted from phone when deleted on watch
Watch freezes sometimes
Being able to set the night time manually would be great (This can be done with the Goclever fw)
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
skiiermike said:
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
Click to expand...
Click to collapse
Thanks was this working on ios or android?,
will add to FAQ
taleboblen said:
Thanks was this working on ios or android?,
will add to FAQ
Click to expand...
Click to collapse
Android.
Thx
Thnx for the information, all working ok on my samsung s4, get the last version v3.18.
thx again
backlight
first of all thanks for this thread :good:
the nite backlight on my tommy watch actually comes on after 5PM (17:00)
i am from Slovakia, phone language is English, time zone CET (GMT+1)
interesting to see that yours turns on after 23:00
chsustik said:
first of all thanks for this thread :good:
the nite backlight on my tommy watch actually comes on after 5PM (17:00)
i am from Slovakia, phone language is English, time zone CET (GMT+1)
interesting to see that yours turns on after 23:00
Click to expand...
Click to collapse
Thanks for the update. i decrypted some of the information from the official Weloop FAQ. and yes i can now confirm that you are right. it turns on from 17-8 thanks again. I have now updated the FAQ with the correct time for all Night settings. :good:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
k0ra said:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
Click to expand...
Click to collapse
Hi , the chronos eco app is not compatible with the Weloop Tommy.
Brand new Tommy, it was paired with my phone but the connection was unstable, so I tried and forced an OTA update, watch is "Updating... 0 pct" but now the phone cannot detect the watch any more
Resetting the watch will restart it in ota update mode again!
Any help appreciated...
l.capriotti said:
Brand new Tommy, it was paired with my phone but the connection was unstable, so I tried and forced an OTA update, watch is "Updating... 0 pct" but now the phone cannot detect the watch any more
Resetting the watch will restart it in ota update mode again!
Any help appreciated...
Click to expand...
Click to collapse
Happened to me also, try to delete connection under bluetooth settings on device. now connect to to weloop and pair from Weloop app. keep trying and then go to update. again persistence is key. keep trying to update suddenly it will connect and update.
Whas the watch on latest firmware when you tried the force OTA?
are you on android or ios see if there is an updated App for you phone. see link on OP for beta APK.
let me know if it works.
watch was not on latest firmware, cant' remember which version it had.
I'm on android, also v1.24 does not help as check for updates does not go beyond "Checking version...".
k0ra said:
Hello! Can someone make last CHRONOS ECO apk link to download? I cant download it from google play.
Click to expand...
Click to collapse
l.capriotti said:
watch was not on latest firmware, cant' remember which version it had.
I'm on android, also v1.24 does not help as check for updates does not go beyond "Checking version...".
Click to expand...
Click to collapse
Try to update the Weloop app, latest is 1.27.
kill weloop app
delete bt connection from phone.
Open weloop app
conmect and update. Keep trying it can take a couple of times.
If all fails if possible try with other device and or ios device
update: I used an iphone and after a few retries I got it on v3.18.
back to android, but the pairing and the sync is problematic, to say the least, on my Huawei P7...
skiiermike said:
I'm no Dev so I'm not sure if this is of any help. While updating the watch I wanted to ensure my screen stayed on so I was tapping the screen.
If you tap the center of the percentage 6 times a pop up appears for you to select your update file. If you select browse it gives you access to a bunch of folders that appear to be inside the app or maybe the watch itself. I tried it several times and 6 is the magic number to make the option appear or disappear. It doesn't work if the watch isn't upgrading it's firmware.
Hope it can be of some use
Click to expand...
Click to collapse
If it's allowing you to select an update file, surely it is showing you the file system of the phone? Otherwise, you'd have no way to put a firmware update file there to select. My understanding would be this allows you to install a firmware update file stored on your phone, although I can't test this for sure as my Android phone is currently being repaired. There's some discussion about this here and that thread also contains a very small amount of analysis on the firmware file (VERY small amount, basically just analysing the name of the binary file), and another app that is apparently in some way related (link).
For what I can glean from the description of that app (seemingly made by the manufacturer of the SoC [System on a Chip] used in the WeLoop Tommy), it would appear that devices using the SoC (including the Tommy) have three firmwares: "bootloader", "soft device" and "application". The one embedded within the WeLoop app apk has the name "ble_app_ancs.bin"; ble stands for bluetooth low energy and ancs apparently stands for apple notification centre services. That leaves "app" - my guess would be this is the "application firmware". I'm not entirely sure the roles of the "bootloader" and "soft device" firmwares, but my guess is the one or other allows the device to get into "DFU mode" (or "OTA mode" as it seems to be referred to also), meaning in theory it should perhaps be possible to recover from any bricks arising from flashing dodgy application firmwares.
So potentially there is the option of reverse engineering the firmware (easily obtained from here: http://wtf.li/ - mirror of the APKs of the app [each of which contain a version of the firmware], and also one version of the firmware (the .bin file) separately), and creating a custom/modified one, while still being able to recover (because bootloader & soft device should be untouched). However, I have neither the expertise nor the time to look into that.
Without an Android phone with which to run either of the apps right now, I can't poke about too much (I only received my Tommy today), but once I get my phone back I'll maybe try and see if I can find anything else interesting. I'd like to see if I can figure out any way to get access to the watch faces, and see if they can be reverse engineered in any way, for example.
EDIT: Here is the output of strings run on the firmware binary from the latest version of the app on http://wtf.li : http://pastebin.com/X7TQXTb3 - nothing particularly interesting, a few filenames of the source files and a few other strings seen in the watch interface and stuff.
EDIT: A couple of URLs accessed by the app (seemingly related to updating):
http://au.umeng.com/api/check_app_update
http://www.yfsmart.com/weloopInterface/getFirmware.do
I can't see anything on these sites, my guess would be they need query strings parameters or something (not really sure what, some way of identifying that the app is accessing the site) to actually do anything.
EDIT: Hmm... http://www.yfsmart.com/weloopInterface/firmware_Upload.jsp - this site seems to allow you to upload a firmware. I wonder if it allows anyone to upload a firmware, which would then be downloaded by everyone when they check for updates? Certainly seems rather insecure...There's a bunch of other pages at http://www.yfsmart.com/weloopInterface/ haven't looked through them all yet.
EDIT: From what I can glean from this page ("SoftDevices" section under the "Development Tools and Software" tab), it seems like the "soft device" firmware is essentially a bit like a library, it's a precompiled binary supplied by Nordic (company that makes chip inside Tommy) which provides all the networking functions etc. which the "application" firmware uses. So:
Code:
application = front end UI (basically, the part WeLoop made)
soft device = "library" via which application can access hardware etc.
bootloader = initial part of firmware that loads SD + app firmwares
So the only really interesting part is probably the application firmware, the part that is in the WeLoop app. That's the code that actually "matters", the rest is just low level stuff. For actually changing the interface or whatever, modifying the app firmware would be all that's needed (for example, to increase the font size or the back light duration etc.).
SifJar said:
If it's allowing you to select an update file, surely it is showing you the file system of the phone? Otherwise, you'd have no way to put a firmware update file there to select. My understanding would be this allows you to install a firmware update file stored on your phone, although I can't test this for sure as my Android phone is currently being repaired. There's some discussion about this here and that thread also contains a very small amount of analysis on the firmware file (VERY small amount, basically just analysing the name of the binary file), and another app that is apparently in some way related (link).
For what I can glean from the description of that app (seemingly made by the manufacturer of the SoC [System on a Chip] used in the WeLoop Tommy), it would appear that devices using the SoC (including the Tommy) have three firmwares: "bootloader", "soft device" and "application". The one embedded within the WeLoop app apk has the name "ble_app_ancs.bin"; ble stands for bluetooth low energy and ancs apparently stands for apple notification centre services. That leaves "app" - my guess would be this is the "application firmware". I'm not entirely sure the roles of the "bootloader" and "soft device" firmwares, but my guess is the one or other allows the device to get into "DFU mode" (or "OTA mode" as it seems to be referred to also), meaning in theory it should perhaps be possible to recover from any bricks arising from flashing dodgy application firmwares.
So potentially there is the option of reverse engineering the firmware (easily obtained from here: http://wtf.li/ - mirror of the APKs of the app [each of which contain a version of the firmware], and also one version of the firmware (the .bin file) separately), and creating a custom/modified one, while still being able to recover (because bootloader & soft device should be untouched). However, I have neither the expertise nor the time to look into that.
Without an Android phone with which to run either of the apps right now, I can't poke about too much (I only received my Tommy today), but once I get my phone back I'll maybe try and see if I can find anything else interesting. I'd like to see if I can figure out any way to get access to the watch faces, and see if they can be reverse engineered in any way, for example.
EDIT: Here is the output of strings run on the firmware binary from the latest version of the app on http://wtf.li : http://pastebin.com/X7TQXTb3 - nothing particularly interesting, a few filenames of the source files and a few other strings seen in the watch interface and stuff.
EDIT: A couple of URLs accessed by the app (seemingly related to updating):
http://au.umeng.com/api/check_app_update
http://www.yfsmart.com/weloopInterface/getFirmware.do
I can't see anything on these sites, my guess would be they need query strings parameters or something (not really sure what, some way of identifying that the app is accessing the site) to actually do anything.
EDIT: Hmm... http://www.yfsmart.com/weloopInterface/firmware_Upload.jsp - this site seems to allow you to upload a firmware. I wonder if it allows anyone to upload a firmware, which would then be downloaded by everyone when they check for updates? Certainly seems rather insecure...There's a bunch of other pages at http://www.yfsmart.com/weloopInterface/ haven't looked through them all yet.
EDIT: From what I can glean from this page ("SoftDevices" section under the "Development Tools and Software" tab), it seems like the "soft device" firmware is essentially a bit like a library, it's a precompiled binary supplied by Nordic (company that makes chip inside Tommy) which provides all the networking functions etc. which the "application" firmware uses. So:
Code:
application = front end UI (basically, the part WeLoop made)
soft device = "library" via which application can access hardware etc.
bootloader = initial part of firmware that loads SD + app firmwares
So the only really interesting part is probably the application firmware, the part that is in the WeLoop app. That's the code that actually "matters", the rest is just low level stuff. For actually changing the interface or whatever, modifying the app firmware would be all that's needed (for example, to increase the font size or the back light duration etc.).
Click to expand...
Click to collapse
Thank you for the insights and findings its all very promising. :good:
On a sidenote:
I talked to one of my colleagues who is an engineer (i'm not a dev but a Designer), it seems like we in the office are playing around with the exact same SOC from NordicSemiconducter. we tried one of the apps from the google play store and it connects to the weloop(see attached pic). The app was called "nRF Master Control Panel", tried the other apps from NordicSC but no luck.
Hopefully there will be some sort of SDK with the v3.0 release on the 30th...
I got my Android phone back today, and haven't tinkered too much with Tommy just yet, but I can confirm that the file system you are browsing when you tap the percentage 5 times during an update is just the phone file system. It browses from root (i.e. /), rather than /sdcard or whatever, which is the standard, user accessible partition, hence there are some folders etc. you may not recognise, but amongst them will be "sdcard" which will take you to your regular storage (note: this is the case on phones without a micro SD card as well), where you could easily place an update file.
SifJar said:
I got my Android phone back today, and haven't tinkered too much with Tommy just yet, but I can confirm that the file system you are browsing when you tap the percentage 5 times during an update is just the phone file system. It browses from root (i.e. /), rather than /sdcard or whatever, which is the standard, user accessible partition, hence there are some folders etc. you may not recognise, but amongst them will be "sdcard" which will take you to your regular storage (note: this is the case on phones without a micro SD card as well), where you could easily place an update file.
Click to expand...
Click to collapse
Thanks for the confirmation. :good:
taleboblen said:
Troubleshooting
Force OTA update:
Connect your watch to the charger.
Press all 3 buttons on the side simultaneously
Release the 2 side buttons, and keep the middle button pressed until you get the upgrade connecting display. (this might take some seconds)
Delete connection from phone
Connect and pair from app and upgrade
If you are on an Android device try an ios device, and vice versa
Click to expand...
Click to collapse
I tried to use the OTA update to go from 3.17 to 3.18 (on Android) but Tommy stuck on screen "WeLoop ... Udating 0%", my smartphone (HTC M8) with its APP (latest version) dont find the Tommy and it remains bricked, how do I restart it? I tried all combinations, but remains on the screen, help me!
Hi ! Gentlemen
I found this rom by chance on one of my favorite websites. I wanted to share that with you.
Hello everyone!
For those who think that their smartphone is already a computer, our small team proposes to use your smartphone as the central unit of any screen: monitor, TV or video projector
Like MS Windows Continuum but better
We are developing a new window manager for Android for a new user experience. You can now use multitasking / multi-windows, resizing, folders and shortcuts on the desktop. You will find a "start" menu, application dock, notifications management, etc.
You can display this interface directly on the screen of your phone / tablet but the most interesting is to use it on a second screen connected with or wireless (respectively MHL / DisplayPort / DisplayLink or Miracast or even Chromecast).
The cherry on the cake, you keep the use of your smartphone since we dissociate the displays of the 2 screens and their uses.
Our code is based on CyanogenMod 13.0. We will shortly pass our development branches on LineageOS 14.1. The goal is to maximize compatibility based on this distribution.
After installation you will find 4 pre-installed applications:
OXI: Launches OXI on the main screen of the device
OXI Remote: Launches OXI on the secondary screen (Android must already be connected to another screen in "mirror" mode, in MHL, DisplayPort, Miracast ...)
We strongly recommend using a Microsoft Wireless Display v2 (available on Amazon, FNAC, etc.) or ActionTech branded adapter, which is fully compatible with OXI and eliminates mouse latency. Feel free to try with your material and give us your feedback.
OXI Control: A small utility if you do not have a Bluetooth keyboard or mouse. Two modes are possible, "Keypad" mode is a simple touchpad and keyboard on the phone, "pad" mode allows to play games requiring tactile use
In some cases, mainly on televisions, the image may not be fully displayed and trimmed. Adjust using this utility until you see the red rectangle around the blue
Youtube video :
https://www.youtube.com/watch?list=PLAnO2gXcwt07ZVIfV_kgfdMUtgxGFSDr6&v=eLM_7da1W0E
View Original French Source Frandroid :
http://forum.frandroid.com/topic/254306-alpha-oxi-sur-nexus-5x/
Installation
If your smartphone is already on CyanogenMod13, you will be able to install the OXI ROM without having to reset your smartphone, just install the zip file "on top". If you have a problem with Google Apps, reinstall them via Open GApps immediately after installing OXI.
OXI installs itself as CyanogenMod 13. If you have another favorite tutorial, do not hesitate to follow it, the procedure being similar to all phones.
If you have not already done so, you need a phone with TWRP or another custom recovery to install zip files. To do this, you will have to unlock the bootloader (with consequences on what it implies), flasher via fastboot or another proprietary tool (Odin, spflashtool ...) to set up the recovery custom partition.
Once in recovery, enjoy to backup your system partitions (including EFS).
Perform a complete wipe the phone (you can try if you are on a CM13 compatible rom to not perform wipe)
Install OXI via adb sideload or by dropping and selecting the .zip file.
If necessary, install the Google apps in the same way (download the corresponding .zip from http://opengapps.org/, select Android 6.0.
Restart the phone and you should be ready to test OXI
For more details I invite you to follow for example this tutorialImportant! Instead of applying root, apply OXI and then Google Apps via OpenGApps
Http://forum.frandroid.com/topic/234137-tuto-installation-recovery-custom-et-root-nexus-5x/
DownloadOXI 0.1.4 (26/01/2017) - md5 0304ee4f69fc6894ae1c42b3501ab670Need Vendor MTC20K 6.0 MM
Via mega.nz: https://mega.nz/#!jt91FI4K!oLeUd3mGWvErpz-96cPl0wqEjK5xPHyP_9laMxf-S0M
Via androidfilehost: https://www.androidfilehost.com/?fid=529152257862698698
Warning:
You install this ROM of your own volition and we are not responsible for any direct or indirect damage to your phone, your data or any consequence related to the OXI test. Back up your data before installing as well as the partitions (Golden Rule).
Oxi is in alpha version, stable enough but still small bugs / crash OXI (not Android) and possibly flaws - do not use in production environment.
We are still developing and we will certainly offer here updates according to the returns obtained
The downgrade since CyanogenMod / LineageOS 14.0 / 14.1 is likely to fail without wipe data / system
Below is a list of the current limitations of OXI. We strive to remove these limitations as we develop.
If you find others, it will feed our todo!
Chromecast is supported but will not work with mouse latency optimizations. Same comment on some Miracast implementations in TV.
If you have problems installing new applications or launching them (for permissions), try launching the application first on the phone in the usual way.
There may be minor problems not related to OXI, these are probably related to CyanogenMod 13
Shortcuts on the desktop are only saved when you exit the application
The bluetooth management from OXI does not work (yet)
Some applications (especially some games) do not resize correctly. Some Unity games can even crash when resized, we work on it.
The optimal configuration is full HD (1920x1080) on an external monitor (PC monitor or TV)
Some TVs unfortunately do not indicate their actual size, in this case the applications will potentially be displayed "bigger" than necessary (similar problem with DisplayLink). We are also working on that.
A single instance of an application can be launched in OXI
An application can only be launched in OXI or on the phone but never both.
The ROM does NOT include any Google apps, but you can install them manually (in the same way as CyanogenMod after installing the .zip - do not do it again if you update from CyanogenMod 13)
The overscan tool may need to be forcibly closed (via reboot, recent apps or any other means) if the setting display persists.
SourcesOur code is based on CyanogenMod 13 (Apache 2): https://github.com/CyanogenMod and http://cyanogenmod.org (down ...)
Nexus 5X kernel sources (GPL): https://github.com/cyanogenmod/android_kernel_lge_bullhead
Websites : https://www.auxens.com/
View Original French Source Frandroid :
http://forum.frandroid.com/topic/254306-alpha-oxi-sur-nexus-5x/
I have try this Rom and it's a simple Cyanogenmod 13 6.0 Marshmallow with Oxi system you can switch to cyanogenmod into Oxi Os and invert. I have try with simple chromecast and it's work like a charm
Tell me what you think of this rom in the comments in advance thank you and beg you to believe in my sincere greetings
Screenshot :
[url=http://www.hostingpics.net/viewer.php?id=592168Screenshot20170204173617.png]
[/URL]
[url=http://www.hostingpics.net/viewer.php?id=795672IMG20170204183846.jpg]
[/URL]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For Moderators :
I don't know if I have the right or not to share this work that is not mine. I apologize in advance if I have done wrong
sorry
Seems nice, but instead of repeating and saying basic things like "You need to install TWRP first" or "Don't forget to backup" you could introduce the project to us.
I don't know French, thus I have absolutely no idea what is this about. Few of my questions:
1. What is that? Given you wrote "Turn your Nexus 5x in computer", I suppose it's smth like Continuum. But there's not enough details.
2. How does it work? AFAIK Nexus 5X's USB Type-C port doesn't support HDMI out.
3. Which vendor to use with it?
4. Which build of CM13?
5. Is it standalone/different OS, or just skin/modification for CM13 to work better on larger screens?
6. Is there difference between this and app Taskbar combined with Nougat (Freeform mode)?
neth15 said:
Seems nice, but instead of repeating and saying basic things like "You need to install TWRP first" or "Don't forget to backup" you could introduce the project to us.
I don't know French, thus I have absolutely no idea what is this about. Few of my questions:
1. What is that? Given you wrote "Turn your Nexus 5x in computer", I suppose it's smth like Continuum. But there's not enough details.
2. How does it work? AFAIK Nexus 5X's USB Type-C port doesn't support HDMI out.
3. Which vendor to use with it?
4. Which build of CM13?
5. Is it standalone/different OS, or just skin/modification for CM13 to work better on larger screens?
6. Is there difference between this and app Taskbar combined with Nougat (Freeform mode)?
Click to expand...
Click to collapse
Like MS Windows Continuum but better
It work with miracast or chromecast for share the screen
it's based on Cyanogenmod 13 but modified
i haven't test this rom but for the vendor i think it's the latest 6.0 Marshmallow
you can go to see the github and website for more info
OP Refresh for more info
Renaf2 said:
OP Refresh for more info
Click to expand...
Click to collapse
Much, much better Thanks bro
Don't get me wrong, I just wanted you to put all the functions, screens etc. together. It's easy to just link to the other website, but less effective than describing it
Btw. I guess I'll try it, but first I'll buy the adapter.
neth15 said:
Much, much better Thanks bro
Don't get me wrong, I just wanted you to put all the functions, screens etc. together. It's easy to just link to the other website, but less effective than describing it
Btw. I guess I'll try it, but first I'll buy the adapter.
Click to expand...
Click to collapse
If you have a chromecast you can try
Renaf2 said:
If you have a chromecast you can try
Click to expand...
Click to collapse
I don't have one. But this app seems pretty good (I have spare computer). Did you try it?
neth15 said:
I don't have one. But this app seems pretty good (I have spare computer). Did you try it?
Click to expand...
Click to collapse
No try it at this moment sorry and i have the honor 6x now
I try it in few minutes
The Vendor.img is MTC20K
it's a simple Cyanogenmod Rom with Oxi system into it
Excellent
[url=http://www.hostingpics.net/viewer.php?id=592168Screenshot20170204173617.png]
[/URL]
i have try that with my chromecast and work like a charm no problem here just cast your screen in quick settings in notification and run oxi remote if you haven't mouse and keyboard you can use oxi control for that you have the keypad for mouse and keyboard and if you want to play you have the pad for that
[url=http://www.hostingpics.net/viewer.php?id=795672IMG20170204183846.jpg]
[/URL]
Hi everyone! Lead dev here!
I'm really surprised and happy to see that our work traveled to XDA without me posting it Thank you renaf2, no problem to share it here.
I'm not able to write a long message tonight (Murphy's Law, I'm in the country side with low network and no physical keyboard) but don't worry I'm gonna be more present here next week.
First of all I know there is a quite huge bug (and my fault sorry!) with Google Apps in this version. I'm gonna publish a new version around Monday or Tuesday.
Beth15, to answer shortly:
1. (This is the long to answer question! I guess Renaf2 clarifications are really helpful but we have so much more to tell!)
2. With nexus 5x we tried DisplayLink (wired), Chromecast (working but not optimal for latency), Miracast (with Microsoft adapters) and what I call "local mode" (directly on the smartphone screen).
3/4. That's a good question... My focus is more on OXI itself than the system so I can't tell from memory which build is used (I would say MOB31K for the build and last rebase from cm repositories was from early December)
Btw thanks Renaf2 for the clarification on the vendor versions. I will be more precise (including in the French topics) next time, I promise
5. It's a modified Android system working with the OXI app. We don't want to disrupt the "classic" Android behavior and we are really in a "adding something missing" than "transforming it" state of mind. Not just screen display tweaking also.
6. It's different for multiple reasons: remote display, session conservation, no requirement for apps developers, enhanced latency in wireless, better window management... And we're working on a lot of other features
I will write more soon!
If you have any question feel free to ask, I'll be glad to answer!
0x4A4A said:
Hi everyone! Lead dev here!
I'm really surprised and happy to see that our work traveled to XDA without me posting it Thank you renaf2, no problem to share it here.
I'm not able to write a long message tonight (Murphy's Law, I'm in the country side with low network and no physical keyboard) but don't worry I'm gonna be more present here next week.
First of all I know there is a quite huge bug (and my fault sorry!) with Google Apps in this version. I'm gonna publish a new version around Monday or Tuesday.
Beth15, to answer shortly:
1. (This is the long to answer question! I guess Renaf2 clarifications are really helpful but we have so much more to tell!)
2. With nexus 5x we tried DisplayLink (wired), Chromecast (working but not optimal for latency), Miracast (with Microsoft adapters) and what I call "local mode" (directly on the smartphone screen).
3/4. That's a good question... My focus is more on OXI itself than the system so I can't tell from memory which build is used (I would say MOB31K for the build and last rebase from cm repositories was from early December)
Btw thanks Renaf2 for the clarification on the vendor versions. I will be more precise (including in the French topics) next time, I promise
5. It's a modified Android system working with the OXI app. We don't want to disrupt the "classic" Android behavior and we are really in a "adding something missing" than "transforming it" state of mind. Not just screen display tweaking also.
6. It's different for multiple reasons: remote display, session conservation, no requirement for apps developers, enhanced latency in wireless, better window management... And we're working on a lot of other features
I will write more soon!
If you have any question feel free to ask, I'll be glad to answer!
Click to expand...
Click to collapse
You can open a new theard in apropriate section and i ask to delete this theard if you want no problem i just want to share your interesting and great work
I'm happy to meet you
Sinon je suis aussi sur frandroid meme pseudo mais je n'y vais plus je suis a la source maintenant sur xda c'est mieux pour apprendre
Hi everyone !
Sorry, I was really busy those days to be able to post around here (and right now I can't post in the proper forums sections), and trying to port it to Nougat (not so easy )
You can find an update for Nexus 5X on the main topic, with a bit more info : https://forum.xda-developers.com/android/general/rom-oxi-smartphone-computer-oneplus3-t3558293
0x4A4A said:
Hi everyone !
Sorry, I was really busy those days to be able to post around here (and right now I can't post in the proper forums sections), and trying to port it to Nougat (not so easy )
You can find an update for Nexus 5X on the main topic, with a bit more info : https://forum.xda-developers.com/android/general/rom-oxi-smartphone-computer-oneplus3-t3558293
Click to expand...
Click to collapse
Oh yeah thank you so much for your hard work bro
Renaf2 said:
Hi ! Gentlemen
I found this rom by chance on one of my favorite websites. I wanted to share that with you.
Hello everyone!
For those who think that their smartphone is already a computer, our small team proposes to use your smartphone as the central unit of any screen: monitor, TV or video projector
Like MS Windows Continuum but better
We are developing a new window manager for Android for a new user experience. You can now use multitasking / multi-windows, resizing, folders and shortcuts on the desktop. You will find a "start" menu, application dock, notifications management, etc.
You can display this interface directly on the screen of your phone / tablet but the most interesting is to use it on a second screen connected with or wireless (respectively MHL / DisplayPort / DisplayLink or Miracast or even Chromecast).
The cherry on the cake, you keep the use of your smartphone since we dissociate the displays of the 2 screens and their uses.
Our code is based on CyanogenMod 13.0. We will shortly pass our development branches on LineageOS 14.1. The goal is to maximize compatibility based on this distribution.
After installation you will find 4 pre-installed applications:
OXI: Launches OXI on the main screen of the device
OXI Remote: Launches OXI on the secondary screen (Android must already be connected to another screen in "mirror" mode, in MHL, DisplayPort, Miracast ...)
We strongly recommend using a Microsoft Wireless Display v2 (available on Amazon, FNAC, etc.) or ActionTech branded adapter, which is fully compatible with OXI and eliminates mouse latency. Feel free to try with your material and give us your feedback.
OXI Control: A small utility if you do not have a Bluetooth keyboard or mouse. Two modes are possible, "Keypad" mode is a simple touchpad and keyboard on the phone, "pad" mode allows to play games requiring tactile use
In some cases, mainly on televisions, the image may not be fully displayed and trimmed. Adjust using this utility until you see the red rectangle around the blue
Youtube video :
https://www.youtube.com/watch?list=PLAnO2gXcwt07ZVIfV_kgfdMUtgxGFSDr6&v=eLM_7da1W0E
View Original French Source Frandroid :
http://forum.frandroid.com/topic/254306-alpha-oxi-sur-nexus-5x/
Installation
If your smartphone is already on CyanogenMod13, you will be able to install the OXI ROM without having to reset your smartphone, just install the zip file "on top". If you have a problem with Google Apps, reinstall them via Open GApps immediately after installing OXI.
OXI installs itself as CyanogenMod 13. If you have another favorite tutorial, do not hesitate to follow it, the procedure being similar to all phones.
If you have not already done so, you need a phone with TWRP or another custom recovery to install zip files. To do this, you will have to unlock the bootloader (with consequences on what it implies), flasher via fastboot or another proprietary tool (Odin, spflashtool ...) to set up the recovery custom partition.
Once in recovery, enjoy to backup your system partitions (including EFS).
Perform a complete wipe the phone (you can try if you are on a CM13 compatible rom to not perform wipe)
Install OXI via adb sideload or by dropping and selecting the .zip file.
If necessary, install the Google apps in the same way (download the corresponding .zip from http://opengapps.org/, select Android 6.0.
Restart the phone and you should be ready to test OXI
For more details I invite you to follow for example this tutorialImportant! Instead of applying root, apply OXI and then Google Apps via OpenGApps
Http://forum.frandroid.com/topic/234137-tuto-installation-recovery-custom-et-root-nexus-5x/
DownloadOXI 0.1.4 (26/01/2017) - md5 0304ee4f69fc6894ae1c42b3501ab670Need Vendor MTC20K 6.0 MM
Via mega.nz: https://mega.nz/#!jt91FI4K!oLeUd3mGWvErpz-96cPl0wqEjK5xPHyP_9laMxf-S0M
Via androidfilehost: https://www.androidfilehost.com/?fid=529152257862698698
Warning:
You install this ROM of your own volition and we are not responsible for any direct or indirect damage to your phone, your data or any consequence related to the OXI test. Back up your data before installing as well as the partitions (Golden Rule).
Oxi is in alpha version, stable enough but still small bugs / crash OXI (not Android) and possibly flaws - do not use in production environment.
We are still developing and we will certainly offer here updates according to the returns obtained
The downgrade since CyanogenMod / LineageOS 14.0 / 14.1 is likely to fail without wipe data / system
Below is a list of the current limitations of OXI. We strive to remove these limitations as we develop.
If you find others, it will feed our todo!
Chromecast is supported but will not work with mouse latency optimizations. Same comment on some Miracast implementations in TV.
If you have problems installing new applications or launching them (for permissions), try launching the application first on the phone in the usual way.
There may be minor problems not related to OXI, these are probably related to CyanogenMod 13
Shortcuts on the desktop are only saved when you exit the application
The bluetooth management from OXI does not work (yet)
Some applications (especially some games) do not resize correctly. Some Unity games can even crash when resized, we work on it.
The optimal configuration is full HD (1920x1080) on an external monitor (PC monitor or TV)
Some TVs unfortunately do not indicate their actual size, in this case the applications will potentially be displayed "bigger" than necessary (similar problem with DisplayLink). We are also working on that.
A single instance of an application can be launched in OXI
An application can only be launched in OXI or on the phone but never both.
The ROM does NOT include any Google apps, but you can install them manually (in the same way as CyanogenMod after installing the .zip - do not do it again if you update from CyanogenMod 13)
The overscan tool may need to be forcibly closed (via reboot, recent apps or any other means) if the setting display persists.
SourcesOur code is based on CyanogenMod 13 (Apache 2): https://github.com/CyanogenMod and http://cyanogenmod.org (down ...)
Nexus 5X kernel sources (GPL): https://github.com/cyanogenmod/android_kernel_lge_bullhead
Websites : https://www.auxens.com/
View Original French Source Frandroid :
http://forum.frandroid.com/topic/254306-alpha-oxi-sur-nexus-5x/
I have try this Rom and it's a simple Cyanogenmod 13 6.0 Marshmallow with Oxi system you can switch to cyanogenmod into Oxi Os and invert. I have try with simple chromecast and it's work like a charm
Tell me what you think of this rom in the comments in advance thank you and beg you to believe in my sincere greetings
Screenshot :
[url=http://www.hostingpics.net/viewer.php?id=592168Screenshot20170204173617.png]
[/URL]
[url=http://www.hostingpics.net/viewer.php?id=795672IMG20170204183846.jpg]
[/URL]
For Moderators :
I don't know if I have the right or not to share this work that is not mine. I apologize in advance if I have done wrong
sorry
Click to expand...
Click to collapse
Love the idea but the UI looks awful, i don't dig it, not one bit... I like the idea that you want to bring this to other devices, because so far the only ones that have this feature are all lumias, samsung s8 and the new huawei. I offer to help with the UI, to make it prettier.
Since device is so new and not too much details around I decided to make a small guide which is good for international users.
Before we start make sure that there is no WearOS or MiWatch apk on your device. If they exist please remove them now.
Factory Reset Your Watch
You need to restart from beginning so Factory Reset for clear start.
Install those files to your phone
Wear OS Chinese Version
MiWatch APK
Open MiWatch App
Choose + sign and choose Xiaomi Mi Watch from list. Just wait a little and you will see on down a button which lets you to directly go to Wear Os App.
Open WearOS App
Make SYNC and finish setup via WearOS app.
Change System Language to English
If your system default language is in any other language please change to English and let MiWatch app to finish sync.
Thx you
Because Xiaomi is TERRIBLE at naming their devices, can you please confirm for me:
1) These instructions are for this watch?
https://www.aliexpress.com/item/1005001667989923.html?spm=a2g0o.productlist.0.0.6edf47e1YoOrgS&algo_pvid=56f796de-f704-4ac0-9635-e86a26a44f41&algo_expid=56f796de-f704-4ac0-9635-e86a26a44f41-8&btsid=0b0a555916101603640801515edaf6&ws_ab_test=searchweb0_0,searchweb201602_,searchweb201603_
2) This still works for all of you who have done it?
I'm wondering why there's only 2 ppl commenting on this. I would have thought that 1000's of ppl have been waiting to make this work in English.
Hello - I have a very specific remote access requirement, however I’m a total novice with regards to Android. I wanted to provide the instructions I have been given to see if anyone in the know could simply summarise or advice how I can achieve this please?
I need remote access of my Android 8.1 Xtrons HU however am finding that all Android Apps fail to allow ‘clicking’ when accessing the device remotely (ie. TeamViewer/ VNC install and allow a connection, however ‘clicking’ can not be done remotely). I believe this could be a security and/or accessibility issue/function, however the closest solution I have found has been advised by both the App publisher and the Xtrons support team below.
Although technical, I don’t know what the exact steps are, or if this approach will even work, however I wanted to post it here to see if anyone could make sense of it please?
Advise from Xtrons (HU Manufactuer):
"After entering "adbon "in the factory set and opening ADB ,you can apply on the machine by yourself directly."
Advice from AnyDesk Development Team:
"For the manufacturer of the Android's ROM there is a process to get the APK signed, so that remote control for that ROM is possible.
This is our Control Plugin Creation Process:
1. Run AnyDesk on the destination device and send the trace file to [email protected]<mailto:[email protected]> or as reply to this mail.
- Open Anydesk on Android
- Open the menu
- Open about panel
- Click on: Send Support Information
2. Please tell us the name you would like for your plugin and whether you want it to be available in the app store.
3. We can extract the system signature hash from the trace files and will build a plugin for this system.
4. We will send you this plugin APK file.
5. You have to sign the plugin with the platform key of your ROM.
apksigner sign --ks YOUR_PLATFORM_KEY_STORE --out YOUR_ANYDESK_PLUGIN-signed.apk YOUR_ANYDESK_PLUGIN-unsigned.apk
6. Send us the signed plugin back.
7. If possible provide us with one of your devices for testing.
8. We will send you the updated anydesk.apk for testing, you will have to install the updated anydesk.apk as well as the signed plugin manually on the test device.
9. After your ok we will publish it with our next android release.
10. Once the plugin and the updated AnyDesk app are released, your devices can be remote-controlled by AnyDesk."