Database Users

[ROM] Sero 7 Pro (US/UK/AU/DE) - AOSP 4.4.4_r2 DoPa v2.7

** DoPa6 (AOSP - Marshmallow) ** is now available - see this post for details and downloads
Click to expand...
Click to collapse
** DoPa5 (AOSP - Kitkat) ** is now available - see this post for details and downloads
Click to expand...
Click to collapse
DoPa v2.7 is a ROM for Sero 7 Pro owners everywhere. Whether bought in the US, Britain, Australia, Germany, or elsewhere, your tablet is supported.
The ROM starts with well-tested AOSP code and adds core functions where needed but skips the frills that are easy to add on - and remove when they cause problems. It's aimed at people who want to choose their own features and not have them imposed by the developer.
New / Improved
International Support - a single ROM for all Sero 7 Pros sold worldwide
New in v2.7 - support for the German model of the Sero 7 Pro (m470bsg)
Speed Control - a unified kernel provides speed when you need it and stock performance when you don't.
Use the new Performance page in the Settings app to control it
exFAT - support has been moved into the kernel for improved performance
Boot Animation - a handsome new DoPa animation thanks to @mikembley, our first-ever UK user
To get you started customizing your ROM, v2.7 offers these add-ons:
built-in: SuperSU, Xposed Installer GravityBox, Phab7
optional: have your tablet claim it's a Nexus7 to get more apps in PlayStore
The package does not include any Google apps (e.g. Playstore). See this thread for links to the latest GApps packages.
Installation
UK / AU / DE / First-time Users
If you're upgrading from a stock ROM (any variety), please click the "show content" button and read the instructions very carefully - they're long but your tablet's continued good health may depend on it!
STEP 1: Install Philz Touch Recovery
Users outside the US must use this version of Philz to install the ROM - neither the stock recovery nor other versions of CWM or Philz will work. Users in the US should use it just to avoid problems.
Stock Recovery
If you still have the stock recovery program you'll have to use the 'fastboot' program to install Philz. On Windows, this requires installation of the 'ADB' USB drivers while in fastboot mode (see below). A package containing the drivers, fastboot, adb and other files can be found in the 2nd posting on the DoPa Stock ROM thread. Note: there are several batch files (*.bat) in the package - do NOT run them.
put fastboot.exe in a convenient directory, then unzip sero7pro-philz6.58.0-dopa-v2.7.zip and put the file philz.img in the same directory (you won't need the other files)
unplug any USB cable, then press and hold Power+VolumeUp; the word "fastboot" should appear on the screen (nothing further will appear)
plug the USB cable from your PC into the tablet, then install the driver (open Device Manager, right click on "Other Devices->Fastboot", then select "Update Driver Software")
after installing the driver, open a command prompt ("DOS window") and change to the directory containing the files
enter fastboot flash recovery philz.img
when done, force the tablet off, remove the USB cable, then reboot into recovery: Power+VolumeDown - you should see the word "recovery", then the Philz menu
CWM
If you have CWM installed, copy sero7pro-philz6.58.0-dopa-v2.7.zip to an SD card, insert it in the tablet, then:
remove any USB cable, then boot into recovery: Power+VolumeDown
select "Install Zip", then "Choose zip from /storage/sdcard1"
select the file, then OK the selection
when done, back out to the main menu, select "Advanced options", then "Reboot recovery"
after the initial "recovery" screen, you should see the Philz menu
Regardless of how you install Philz, the result should be the same. If it boots OK, compatibility is assured
STEP 2: Backup
I can't emphasize this enough: you must make a backup of your existing ROM. If something goes wrong, there's no way to get your device working again other than to restore it using the backup you've made. There's also another reason to do a backup: before installing the new ROM, you will have to reformat your /data partition. This will wipe out your apps, your settings, and most importantly, all the music/photos/etc stored on your "internal SDcard". These last items can be restored if you follow the instructions below:
ROM
You must do your backup onto a real SD card that you can remove because your "internal SDcard" will be erased in the next step. In fact, it wouldn't be a bad idea to do two backups (preferably to different cards) just in case one is faulty.
on Philz main menu, select "Backup and Restore"
next, select "Backup to /storage/sdcard1" (the 6th item on that menu)
if there's enough space on the card, the backup will start without any further prompt; it could take anywhere from 3 to 15+ minutes depending on the amount of data and the speed of your card
if needed, you can enable compression to create a smaller backup: select "Misc Nandroid Settings -> Default Backup Format -> tar + gzip", then on the previous menu, tap on "Compression" to set the appropriate level
Internal SD card
This is optional but worthwhile if you have files you value stored on the tablet:
on Philz main menu, select "Backup and Restore"
next, select "Custom Backup to /storage/sdcard1" (the 9th item on that menu)
on the next screen, deselect everything, then select "Backup /data/media" (the next-to-last item)
finally, select "Start Custom Backup Job"
STEP 3: Install the DoPa ROM
Before you begin, you may want to download a Google Apps ("Gapps") package that you can install after the ROM. See this thread for a selection of packages. To avoid complications, I'd suggest choosing the "Nano Modular Package" to get just the basics - you can always upgrade later. Put your Gapps package along with the ROM zip on an SD card and insert it into the tablet - you can use the same card you're using for your backups.
on Philz main menu, select "Wipe and Format Options", then "Custom Format Options"
select "format /data and /data/media (/sdcard)" (the 8th item), then OK your choice
back on the main menu, select "Install Zip -> Choose zip from /storage/sdcard1"
select sero7pro-aosp444-dopa-v2.7.zip, then OK your choice - the install process should take about 40 seconds
next, install your Gapps package
return to the main menu, select "Reboot System Now", then hold your breath for the next 3-4 minutes
the Hisense screen should be up for less than a minute, followed by the DoPa boot animation for another 2-3 minutes
when the Google setup screen appears, you'll probably get a warning that "Bluetooth Sharing" has stopped - after you clear it, you'll never see it again
If the boot animation is still running after 5+ minutes, force the tablet off, then reboot. If that doesn't fix it, try formatting /data again. If it still doesn't work, restore your tablet from your backup ("Backup and Restore -> Restore from /storage/sdcard1"), then post a message here. If everything works out as hoped for, re-read the first posting in this thread for details on some of the features (and problems) of this ROM.
Upgrades
While any SELinux-enabled version of CWM or TWRP can be used to install the ROM, the companion Philz Touch CWM-based recovery is highly recommended if you use exFAT-formatted SD cards.
from DoPa AOSP Kitkat ROMs (v1.0-v2.6) - no need to wipe or format anything!
from pre-Kitkat (v4.4.x) or any CM-based ROMs - wipe your /data partition before installing to avoid unnecessary problems.
install sero7pro-aosp444-dopa-v2.7.zip
- the installer will wipe (but NOT format) /cache and dalvik-cache for you
install your preferred Gapps package
- upgraders: this is required to prevent your downloaded Google apps from crashing
optionally, install the Nexus7 spoof (sero7pro-nexus7spoof-dopa-v2.7.zip)
reboot (ignore any "fix root" prompt - it's incorrect)
f2fs / ext4 Migration
This DoPa ROM gives you the flexibility to format any of your built-in partitions using either the f2fs or ext4 file systems.
As part of your install - or at any time - you can switch formats without losing any data. Click "show content" for instructions.
If you haven't already installed Philz Touch Recovery, please do so first. Philz has gotten complicated, so read this carefully!
make a nandroid backup to your external SD card
select Wipe and Format Options, then Custom Format Options
select toggle f2fs <-> ext4 migration
- be sure there's a confirmation message at the bottom of the screen
select each partition you want to convert or wipe, then select the format and OK your choice
Important: to convert your /data partition, you must select format /data and /data/media (/sdcard)!!!
use Custom Restore from /storage/sdcard1 to restore the contents of the partitions you reformatted
Notes
Speed Control - this version uses a redesigned kernel that caps processor speeds at stock levels during start-up, then adjusts them once the tablet is up and running. Go to Settings->Performance to enable this feature, and to set the top speeds for the CPU (1.0-1.5ghz) and GPU (448-520mhz). When disabled,the processor will remain at stock speeds (1.2ghz/448mhz) unless changed by a 3rd-party app.
Encryption - the first time you formatted your /data partition, you lost the ability to encrypt your tablet's data. Using the companion Philz Touch Recovery to reformat /data (using either filesystem) will restore that ability. To preserve your existing data, do a backup first, then restore just /data when done. Note: you must select "format /data and /data/media (/sdcard)" when reformatting.
OTG Charging Support - this kernel supports charging the tablet while an external device (flash drive, keyboard, etc.) is attached to the USB port. This feature requires either an OTG 'Y' cable or an OTG USB hub, and the AC adapter that came with the tablet. For this to work, power must be connected to the cable or hub before plugging it into your tablet. The OTG device(s) can be attached/detached at any time.
WiFi Display (a.k.a. Miracast) - video works but its performance may depend upon your TV; audio does not work.
Bluetooth Sharing - on the initial boot, this service will FC due to a timing issue. The system will restart it and you should never see this error again.
Added/Changed in v2.6
International Support - added support to the kernel for the British and Australian models of the Sero 7 Pro
Overclocking - replaced separate standard and overclocked kernels with a unified kernel that uses less power when overclocked; added a new Performance page to the Settings app to control it
exFAT Support - moved exFAT support to the kernel for improved performance
Boot Animation - added a custom boot animation created by @mikembley
Added/Changed in v2.51
Flexible Formatting - added F2FS support for the /thirdparty and /mnt/modem partitions
Bug Fix - enabled Philz Touch Recovery to format the /thirdparty and /mnt/modem partitions using EXT4
Added/Changed in v2.5
Flexible Formatting - enabled use of either F2FS or EXT4 for any of the built-in partitions
External Storage - added support for F2FS, and for devices formatted without a partition table (i.e. Windows-style "super-floppies")
Android version - upgraded from AOSP 4.4.4_r2 to AOSP 4.4.4_r2.0.1
Recovery - added a DoPa version of Philz Touch Recovery
Added/Changed in v2.1
SD Cards - added support for SD cards formatted with the NTFS or exFAT filesystems
Android version - upgraded from AOSP 4.4.4_r1 to AOSP 4.4.4_r2
Added/Changed in v2.0
Google Now - voice activation (i.e "OK Google") now works in the Google Now launcher
kernel - added OTG charging support.
Credits
ziddey
randomblame
davepmer
the CM team
Downloads
sero7pro-aosp444-dopa-v2.7.zip the full ROM
sero7pro-nexus7spoof-dopa-v2.7.zip identify tablet as a Nexus7 to (possibly) show more apps in PlayStore
sero7pro-philz6.58.0-dopa-v2.7.zip a customized version of Philz Touch CWM-based Recovery v6.58.0
sero7pro-format-thirdparty.zip - only needed if you are downgrading from DoPa6 (Marshmallow) to previous versions (i.e. this one)
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.

Thanks man been running it since day one no problems and very stable.

Can We call these the Semi OFFICIAL ROM ?

I installed v1 after it booted up play store wasn't installed. Did any one else experience this? I did a dirty flash and a full wipe.
Sent from my Sero 7 Pro using xda app-developers app

How much free space should there be on a system after a fresh install?

datboy143 said:
I installed v1 after it booted up play store wasn't installed. Did any one else experience this? I did a dirty flash and a full wipe.
Sent from my Sero 7 Pro using xda app-developers app
Click to expand...
Click to collapse
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that. I still have some testing to do and will report back later.

Gazoo119 said:
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that. I still have some testing to do and will report back later.
Click to expand...
Click to collapse
Ok will do thanks
Sent from my SGH-I777 using xda app-developers app

GPS and Google music
I noticed on version 0 that GPS could take awhile to lock on, and if you turned it off and back on that sometimes it wouldn't lock on at all. I also noticed an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build? Otherwise, this is one of the cleanest KitKat builds I've used

gotshores said:
I noticed on version 0 that GPS could take awhile to lock on, and if you turned it off and back on that sometimes it wouldn't lock on at all. I also noticed an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build? Otherwise, this is one of the cleanest KitKat builds I've used
Click to expand...
Click to collapse
Don't use Google music but I do use scanner radio and whenever I switched streams the tablet would freeze and I would have to hold the power button to turn the tablet off.
Now its working like it should. So this latest build might fix Google music.
Another issue I was having is when I opened the calendar it would not close hitting the back button. Its closes fine now.
The GPS doesn't seem to load any slower for me than it did with the stock ROM but I don't use it much.
Anyway I would recommend trying this latest build. Just make sure you wipe cache and dalvik cache and flash the latest gapps. Everything should still be the same as before when you boot with the new ROM and hopefully you will notice some improvements.
---------- Post added at 07:31 PM ---------- Previous post was at 07:22 PM ----------
dolorespark said:
This is a plain-vanilla build of KitKat for those who prefer their enhancements added on rather than built in.
Click to expand...
Click to collapse
Just want to thank you for fixing the sound bug. V4A is working perfectly and as far as I can tell so is everything else. I will keep testing and if I run across anything strange I will post here. Your work on this is very much appreciated

dolorespark said:
This is a plain-vanilla build of KitKat for those who prefer their enhancements added on rather than built in. The only changes to the AOSP and kernel code are those needed to ensure compatibility or to enable standard features Hisense omitted (e.g. USB-OTG support). Because it relies on well-tested AOSP code, it is likely the most stable KitKat ROM available for this tablet. For the same reasons, it is almost certainly not the fastest KitKat ROM either.
To make it more functional, the package includes a handful of apps most people find useful: SuperSU, ES File Explorer, Xposed Installer, GravityBox, and my Phab7 UI switcher. To avoid the wrath of Google, it does not include any GApps; see this thread for links to the latest packages.
Installation
Having an SELinux-enabled version of CWM or TWRP installed is a prerequisite. You can find versions built by randomblame here or by davepmer here.
If you're upgrading from v0 of this ROM, clearing cache and dalvik-cache should suffice. Otherwise, do a full wipe of both your data and cache partitions. As always, a backup of your existing setup is recommended.
Notes
All features should be present and work as expected with these exceptions:
WiFi Display (a.k.a. Miracast) - video is enabled but very slow; audio is disabled because it doesn't work and generates 45 error messages per second when enabled
SELinux - the kernel runs in permissive mode due to missing entries in its configuration.
As these issues are resolved, the ROM will be updated accordingly.
Credits
randomblame
davepmer
the CM team
Download
sero7pro-aosp442-dopa-v1.zip
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
DoPa
Click to expand...
Click to collapse
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)

chopin_k said:
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)
Click to expand...
Click to collapse
This is normal..
Sent from my Sero 7 Pro using XDA Premium 4 mobile app

enfermo said:
Can We call these the Semi OFFICIAL ROM ?
Click to expand...
Click to collapse
Generic, yes - (semi-)Official, no.
datboy143 said:
I installed v1 after it booted up play store wasn't installed.
Click to expand...
Click to collapse
Gazoo119 said:
I followed the instructions and noticed the same thing and gmail kept crashing. Flashing the latest gapps will fix all of that.
Click to expand...
Click to collapse
As noted in the OP, none of the GApps (e.g. Playstore) were included in this ROM. I have updated its verbiage to be even more explicit. As to GMail crashing, I'm a little puzzled how that could happen if it wasn't included - did you mean the generic Email app?
gotshores said:
I noticed on version 0 [...] an issue when running Google music where it would freeze and cause the tablet to reboot. Anyone having these issues on the new build?
Click to expand...
Click to collapse
I hope not: v1 wouldn't have been released if that bug were still present. The problems you encountered were caused by enabling sound effects, either built-in or 3rd-party - the notes for v0 said as much. Perhaps Google Music enabled them automatically.
chopin_k said:
Thanks for the rom. After flashing the rom I rebooted, powered down and installed gapps. On reboot I got a message about root access possibly being lost and offering to fix it, I said yes. First time I get that, is it ok? (It seems to be working ok)
Click to expand...
Click to collapse
I ran into that too - and something even odder. SuperSU's su and daemonsu program files should have a flag that marks them as authorized to give root access. That flag is now missing but I can still get root whenever needed. I don't know if this is to be expected with SELinux in place or just something specific to SuperSU. I'll investigate...
tinybeetle said:
How much free space should there be on a system after a fresh install?
Click to expand...
Click to collapse
After installing the ROM, the "Gapps Standard" package, and Antutu, Settings->Storage says I have 5.48gb available. This is the free space on your /data partition and includes the space used by your emulated SD Card (which is actually just a subdirectory of /data).

"Smart ass alert"
Not only was playstore not installed, it doesn't give me the winning lottery numbers for next week! What gives?
Ok, being serious, Thank you for your time and effort. This weekend I am going to finally give this a try.

Dolorespark,
I haven't messed with any sound effect settings, so it must be Google Music messing with things. Have you noticed any issues with GPS? I can run any of the other rom's, including CM11, and it locks on immediately, but it seems random with AOSP. Sometimes I'll wait a coupled of minutes and it'll get a lock, and other times it won't lock on at all. Anyway, thanks for all you do. I'll keep testing, and keep my trusty backup of DOPA v2.

Working brilliantly so far. V0 to V1 smooth after adding gapps back to the mix. Sounds like time to reinstall V4A and sync some commute podcasts!
Thanks Dolorespark!

envygreen said:
Working brilliantly so far. V0 to V1 smooth after adding gapps back to the mix. Sounds like time to reinstall V4A and sync some commute podcasts!
Thanks Dolorespark!
Click to expand...
Click to collapse
intermittently get google services has stopped.... only that but everything looks good so far.... anything to fix google services stopping? also had a root fix need after rebooting, did yes and everything is ok... thanks DOPA....

dolorespark said:
I hope not: v1 wouldn't have been released if that bug were still present. The problems you encountered were caused by enabling sound effects, either built-in or 3rd-party - the notes for v0 said as much. Perhaps Google Music enabled them automatically.
Click to expand...
Click to collapse
I had this issue on v0 as well and it seems that it's not gone yet. I only wiped dalvik & cache coming from v0 so I'm not sure if that's part of the problem, but I'm still experiencing the Google Play Music crash. It only seems to crash when playing content that hasn't already been cached locally. Attached is a logcat.

dolorespark said:
As noted in the OP, none of the GApps (e.g. Playstore) were included in this ROM. I have updated its verbiage to be even more explicit. As to GMail crashing, I'm a little puzzled how that could happen if it wasn't included - did you mean the generic Email app?
Click to expand...
Click to collapse
No it was gmail. It would close followed by the message "unfortunately this application has closed" or something like that. It wasn't really crashing but rather would not stay open. Anyway flashing the latest gapps fixed that and all is good for me so far.
I played with the tablet extensively last night and did not experience any problems. Even movies, streaming or local using XBMC play using a bluetooth headset. There is no stuttering as there was in all of the previous Jelly Bean roms, stock....DoPa1 and DoPa2. I don't know if that was a KitKat fix or what but I am very happy with the stability of this rom and the fact the XBMC bluetooth bug was fixed is icing on the cake. Of course V4A makes it even better.
I will continue to run the rom and will post if I find any bugs. Thanks again.:good:

Been running since v1 was posted. Have to say the music bug is no more! Listening to lucky mixes all day today and email, g+, and everything my wife and kids have done on it. No problems! Thanks You have really taken your time to make this rom perfect!!!!

Gazoo119 said:
[gmail] would close followed by the message "unfortunately this application has closed" or something like that. It wasn't really crashing but rather would not stay open. Anyway flashing the latest gapps fixed that and all is good for me so far.
Click to expand...
Click to collapse
nccruz said:
intermittently get google services has stopped.... only that but everything looks good so far.... anything to fix google services stopping?
Click to expand...
Click to collapse
Did you use the latest GApps package? As Gazoo119 noted, that fixed a problem with another app that uses Google Play Services. If the problem persists, you may want to go to Apps->Google Play Services, then tap the "Manage space" button. On the next screen it lets you clear all data.
gotshores said:
Have you noticed any issues with GPS? I can run any of the other rom's, including CM11, and it locks on immediately, but it seems random with AOSP. Sometimes I'll wait a coupled of minutes and it'll get a lock, and other times it won't lock on at all.
Click to expand...
Click to collapse
I hadn't tried GPS at all until you mentioned it. I installed Google Maps but couldn't get a lock at all. It's raining here, so I couldn't get fully in the clear. Instead I sat in my car and it still did nothing. Finally, I forced-stopped the app, cleared data and cache, then retried. This time it only took a few seconds to find me. I then turned off GPS, rebooted, and moved to my semi-covered patio. After getting everything going again, it took 10-15 seconds to get a rough fix (off about 70 feet) and it continued to hold it even after I went inside. You may want to try clearing Maps' data (if that's what you're using) to see if that helps.
unomar said:
I had this issue on v0 as well and it seems that it's not gone yet. I only wiped dalvik & cache coming from v0 so I'm not sure if that's part of the problem, but I'm still experiencing the Google Play Music crash. It only seems to crash when playing content that hasn't already been cached locally. Attached is a logcat.
Click to expand...
Click to collapse
Whatever crash you're seeing isn't the one that I fixed. That one was produced a full-blown hardware crash with a register dump. Your logcat doesn't show a register dump or even a Java runtime exception dump. There were two errors that caught my eye but I don't know if either would cause an "Unfortunately..." popup.
Code:
04-08 09:40:24.213 E/DownloadTaskImpl( 3156): Download failed because of IO Error: Socket closed
04-08 09:40:24.213 W/DownloadTaskImpl( 3156): Experienced error when trying to download: [mId=[7871, DEFAULT] mTrackTitle="Le onde" mRemoteId=9ea5817b-9753-348e-af52-ea7c0947c6cb mSourceAccount=1954430662 mPriority=3 mOwner=MUSIC_PLAYBACK mSeekMs=0 mRetryAllowed=true mFileLocation=[mFullPath=/data/data/com.google.android.music/files/music/mplayback_7871.tmp mStorageType=INTERNAL mCacheType=2] mExplicit=false]
Here, the (software) communication link being used to download "Le onde" was broken. Later on, you got this error:
Code:
04-08 09:40:57.133 I/wpa_supplicant( 618): wlan0: CTRL-EVENT-DISCONNECTED bssid=00:1a:30:e4:64:00 reason=0
[...]
04-08 09:40:59.803 E/DownloadTaskImpl( 3156): Download failed because of IO Error: recvfrom failed: ETIMEDOUT (Connection timed out)
04-08 09:40:59.803 W/DownloadTaskImpl( 3156): Experienced error when trying to download: [mId=[363, DEFAULT] mTrackTitle="Black Hole Sun" mRemoteId=8076a782-8454-3fd8-899d-213bb23836ac mSourceAccount=1954430662 mPriority=0 mOwner=MUSIC_PLAYBACK mSeekMs=0 mRetryAllowed=true mFileLocation=[mFullPath=/data/data/com.google.android.music/files/music/mplayback_363.tmp mStorageType=INTERNAL mCacheType=2] mExplicit=true]
This download failure is a lot easier to understand: your WiFi connection had dropped. I don't know that either of these is something I can fix. As above, you may want to try the obvious fixes if you haven't done so already: use the most recent GApps package, clear the app's cache and data, and play with the app's caching options.

Weloop Tommy Smartwatch (FAQ/Updates/Hacks)

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!

[ROM] Htc Desire 816 Marshmallow Unofficial Rom

Upgrade/Update HTC Desire 816 to 6.0 Marshmallow
I rewrite this tutorial from forum.xda-developers.com :
The users of HTC Desire 816 can now update their handsets to Android 6.0 Marshmallow using custom ROM. The new Android 6.0 Marshmallow comes with many new features :
- Mobile payments (Android Pay) feature.
- Better RAM Management.
- Fingerprint support.
- A battery saver feature which extends device use by up to 90 mins.
- It has a faster, smoother and more powerful computing experience.
- Support for 64-bit SoCs using ARM, x86, and MIPS-based cores.
- OpenGL ES 3.1 and Android extension pack brings Android to the forefront of mobile graphics putting it on par with desktop and console class performance.
- Responsive, natural motion, realistic lighting and shadows, and familiar visual elements make it easier to navigate your device.
- More intelligent ranking of notifications based on who they’re from and the type of communication. See all your notifications in one place by tapping the top of the screen.
- New devices come with encryption automatically turned on to help protect data on lost or stolen devices.
- SELinux enforcing for all applications means even better protection against vulnerabilities and malware.
- State of the art video technology with support for HEVC main profile to allow for UHD 4K 10-bit video playback, tunneled hardware video decoding to save power and improved HLS support for streaming.
- and other cool features.
Here are some more aspects that users should know before trying out the custom ROM :
- Users need to have proper back-up for their personal data on the device.
- The handset should have at least 80 percent of battery power.
- The users also need to ensure that USB Debugging is enabled on the device.
- During the installation, if the device gets stuck on booting, users can perform wipe cache partition and wipe dalvik before rebooting the device.
Tutorial
1. Download Android 6.0 Marshmallow ROM for HTC Desire 816 from link below :
The ROM File size is big, so I split the file into 3 parts :
ROM Part 1 : Mod edit: download link removed
ROM Part 2 : Mod edit: download link removed
ROM Part 3 : Mod edit: download link removed
Tutorial Video : Mod edit: download link removed
To combine 3 parts files : put all the parts into the same folder, then double click on ROM-Part1.rar, all the other parts will unpack and combine automatically. If any problem with the ROM, maybe because the ROM have corrupted during the download process, you can try to re-download the ROM.
2. Install the ROM Manager on your HTC Desire 816 . Get it from Google Play Store, then install the clockwork mod recovery. You also can use ROM Installer application from JRummy Apps Inc.(Get it from Google Play Store).
3. Connect your HTC Desire 816 to your PC employing the USB information cable. Copy the “ROM.zip” file you downloaded to the SD memory card.
4. Restart your device in the recovery mode using ROM Manager. As soon as in Recovery Mode, go to ROM Manager and select backup/restore to back-up your information.
5. From the Recovery Menu do a total data erase (including Delvik Cache). When completed, go back to Recovery Principal Menu and choose Flash ROM from SD Card. Navigate the location you copied the ”ROM.zip” file and follow the directions for installing Android 6.0 Marshmallow on your HTC Desire 816 . As soon as the installation is over, just reboot your HTC Desire 816 device, and here you go, you’ve just upgraded it to the new Android 6.0 Marshmallow.
For any help you can Contact me on fb here
:- www.fb.com/xdamembermihirsheth

Thread closed.

Walton vx android 6.0 marshmallow rom

Good news for everybody owning the Walton prmo VX There’s a recent post coming from xda-developer forum giving hints on how to Update and install Android 6.0 Marshmallow using custom ROM on Walton VX .
The Android 6.0 Marshmallow comes with various advantages and features, but the obvious one is the performance improvement. The new OS offer up to 4 times of performance improvements, along with faster and more powerful computing. Google also claimed that the Android 6.0 Marshmallow can extend your device’s battery life by up to 90 minutes. It’s a must-have upgrade for every Walton primo VX owners!
The new Android 6.0 Marshmallow comes with many new features :
Mobile payments (Android Pay) feature.
Better RAM Management.
Fingerprint support.
A battery saver feature which extends device use by up to 90 mins.
It has a faster, smoother and more powerful computing experience.
Support for 64-bit SoCs using ARM, x86, and MIPS-based cores.
OpenGL ES 3.1 and Android extension pack brings Android to the forefront of mobile graphics putting it on par with desktop and console class performance.
Responsive, natural motion, realistic lighting and shadows, and familiar visual elements make it easier to navigate your device.
New devices come with encryption automatically turned on to help protect data on lost or stolen devices.
SELinux enforcing for all applications means even better protection against vulnerabilities and malware.
State of the art video technology with support for HEVC main profile to allow for UHD 4K 10-bit video playback, tunneled hardware video decoding to save power and improved HLS support for streaming.
and other cool features.
Before you upgrade your device, there are some things you need to consider. First is you should back up all of your personal data on your smartphone. You also have to enable the USB Debugging is enabled. Last but not least, it is highly recommended to have the WALTON PRIMO VX fully charged. Therefore, you can be sure that the phone can stay on during the whole process.
How to Install Android 6.0 Marshmallow ROM on Walton VX
1. Download the ROM from the source below. Note that there are three parts of it. Please download all of them. After you download all of the files, put them all under the same folder. Then all you have to do is to double click the first part and the rest will combine automatically (you have to have WinRar program in order to do so)
The ROM File size is big, so I split the file into 3 parts :
ROM Part 1 : Rom link update soon or Mirror
ROM Part 2 : Rom link update soon or Mirror
ROM Part 3 : Rom link update soon or Mirror
2. Visit Google Play Store and then download and install the ROM Manager on your Walton primo VX . Alternatively, you can try using alternative application such as Jrummy Apps Inc.(Get it from Google Play Store).
3. Next, download and install the Clockwork Mod Recovery on your Walton VX
4. Connect the phone to your PC via USB cable. Copy the Rom.zip file to your phone’s memory card.
5. Restart the phone in Recovery Mode using the ROM Manager. After the restart is completed, open the ROM Manager again and backup your personal information.
6. Go to Recovery Menu and perform the total data erase. After that, go back to Recovery Main Menu and choose the Flash ROM from SD Card. Navigate to the folder in which your Rom.zip is located, an Walton VX d follow the directions for installing Android 6.0 Marshmallow on your Walton VX . As soon as the installation is over, just reboot your Walton VX device, and here you go, you’ve just upgraded it to the new Android 6.0 Marshmallow.
7. Done
There you go. It’s very easy to install Android 6.0 Marshmallow ROM on Walton VX isn’t it? Below are some pictures of Android 6.0 Marshmallow.
Android 6.0 Marshmallow on WALTON PRIMO VX
GET UPDATES STAY CONNECTED

Thread closed.
1) Do not use XDA to advertise your blog.
2) Wrong forum.

OXI Rom (CM 13 Based Rom) Turn your Nexus 5x in computer

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 tutorial​Important! 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/
Download​OXI 0.1.4 (26/01/2017) - md5 0304ee4f69fc6894ae1c42b3501ab670​Need 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.
Sources​Our 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 tutorial​Important! 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/
Download​OXI 0.1.4 (26/01/2017) - md5 0304ee4f69fc6894ae1c42b3501ab670​Need 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.
Sources​Our 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.