yashsingh1/xdaforums huggingface dataset:
[X 2014 Q&A, Help & Troubleshooting] songs354:
yeah i know what you mean, i think wave and pick up gesture is turned off that's why its not working, when you enable moto display automatically wave gesture and pick up gesture gets turned off, so turn on your wave and pick up gesture under settings/gesture shortcuts then it will work when you wave your hand :) but moto display doesn't seems to work for me either :( and you need to install moto and moto actions from playstore to see moto display feature when you install moto and moto actions then an app 'moto' will appear in your app drawer, so install moto and moto actions from playstore. So you need 3 things moto and moto actions from google playstore and moto display zip and copy those lib files give root permission to those files and yeah enable the wave gestures under settings but moto display does not works even if its enabled....only ambient display works even if moto display is turned on
[X 2014 Q&A, Help & Troubleshooting] songs354:
oh and i suggest you to flash 5.6.9 since 5.6.1 has a few bugs and its quite old now...so flash 5.6.9 and then head to twrp recovery flash the moto zip and wipe cache/dalvik reboot and then copy those files to system/lib and paste there give root permission to those files reboot and then install moto and moto actions from google playstore then moto app will appear in your app drawer and then enable hand wave gesture and pick up gesture under settings :)
[X 2014 Q&A, Help & Troubleshooting] songs354:
i got a link while i was searching for moto display to work on custom roms., it contains all the the moto apps (moto voice, moto display, moto, moto actions) its a flashable zip but do not flash it or you'll end up in a bootloop, i've tested it i ended up in a bootloop then again i dirty flashed RR once again and after wiping cache/dalvik and rebooting brought to its normal state as it was, its fine now. But don't try this you'll get bootloops, the bootloop is casuing just for one file, its this 'com.motorola.moto.xml' if you exclude this file while flashing its okay you won't get booloops but this file has to be flashed as well to get permission for moto display that's the problem, i wish there were some dev to fix this :(

this is the link but don't try it, https://docs.google.com/file/d/0B5XNxZ2OcfKteUhFYTB4aU5yanc/edit?pageId=110058636999360137761

rather than trying i think its a better idea to tell a dev
[X 2014 Q&A, Help & Troubleshooting] Sanokko:
Oh Thank you ! I saw this post earlyer but didn't tried !

Yes, i agree, we've to find a dev to port this app on CM based rom !!
[X 2014 Q&A, Help & Troubleshooting] songs354:
yeah we need a dev to port it...but what about megatron007, i thought he would look into this
[X 2014 Q&A, Help & Troubleshooting] Sanokko:
I don't really know .. Maybe he is busy. But nobody posted on the RR thread since your quoted me about Moto Display ..

Next time he will come to XDA, i think he will see our "requests" Maybe we can find a CyanogenMod dev to port it to CM based rom ?
[X 2014 Q&A, Help & Troubleshooting] songs354:
yeah probably he could be busy, yeah if a CyanogenMod dev could port it to cm based rom then its all done, maybe taking this topic to cyanogenMod forum would help too
[X 2014 Q&A, Help & Troubleshooting] mastarifla:
I looked at the applications, and it has the KitKat version of the Motorola Apps and the structure of the zip file is for the KitKat operating system... that's probably why it is messing up, or the permissions are not being set during the updater script...

You would need to be on a KitKat Rom and then flashing that zip file and see if it works... but you could try updating the zip file with the latest Marshmallow APK's and files, then see if it works... Here is an updated edify script file that adds permissions, but you will also need to edit the zip file to add the folder structure for the apps...

ui_print("**************************************************");
ui_print(" Standalone Moto Apps Suite ");
ui_print("**************************************************");
ui_print(" Mastarifla(SocraticBliss) ");
ui_print("**************************************************");
ui_print("");

ui_print("Verifying supported devices...");
assert(getprop("ro.product.device") == "victara" || getprop("ro.build.product") == "victara" || abort("This package is for \"victara\" devices; this is a \"" + getprop("ro.product.device") + "\"!");
show_progress(1.000000, 0);

ui_print("Mounting the system partition...");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
set_progress(0.100000);
ui_print("");

ui_print("Deleting audiomonitor files...");
delete_recursive("/system/vendor/moto/audiomonitor");
set_progress(0.300000);
ui_print("");

ui_print("Extracting system files...");
package_extract_dir("system", "/system");
set_progress(0.600000);
ui_print("");

ui_print("Setting permissions...");
set_perm_recursive(0, 0, 0755, 0644, "/system");
set_progress(0.900000);

ui_print("Unmounting the system partition...");
unmount("/system");
set_progress(1.000000);
ui_print("");

ui_print("Update Completed!");
ui_print("Please consider donating if you find this valuable or useful!");
[X 2014 Q&A, Help & Troubleshooting] songs354:
i think you can make it work but this flashable zip has the updated moto display but the "Motodisplay .odex" file i've included in the flashable zip is from kitkat, do not flash it if you flash it you need to remove the motodisplay.odex to prevent bootloops or any issues, first remove the motodisplay.odex file and then you can flash

it would be nice if this works on custom roms :)

can you make it work to support this on marshmallow roms ? i can test it if it works

and do i have to remove the whole code from the script and add only the codes which you wrote ? ?

but Moto.zip and MotoActions.zip are not flashable zip, these two moto and motoactions are also the latest apk and also the moto display is the latest apk for android 6.0 i just made a zip cause it contains some files that's why i made Moto and MotoActions a zip file but this file "MotoDisplay.zip" is a flashable zip
[X 2014 Q&A, Help & Troubleshooting] mastarifla:
You just need to edit the flashable zip file that you have...

Extract the zip file to a folder on your desktop, then in the system folder, add the following folders...

app/MotoDisplay_FWProxy_3.0
priv-app/Moto
priv-app/MotoActions
priv-app/MotoDisplay_3.0

Place the stock zips from a stock Marshmallow image into those folders, replace the updater script with the text from above, oh and be sure to grab those same permissions files from a stock Marshmallow image... then give it a shot!
[X 2014 Q&A, Help & Troubleshooting] songs354:
i appreciate your help :) but i don't have the stock marshmallow image for x 2014 :(

but do you mean this ?? well i have these xml doc
[X 2014 Q&A, Help & Troubleshooting] songs354:
Error flashing :confused: i don't know why, maybe cause the files of permissions were for kitkat ? probably i'll need the Marshmallow permission files ?

I'll have to download a stock rom 6.0 i guess for those permission files
[X 2014 Q&A, Help & Troubleshooting] mastarifla:
Well you're lucky, I managed to have a few of the files and took the time to create a zip for you, no guarantees that this will work, but it may get you a step closer...
[X 2014 Q&A, Help & Troubleshooting] songs354:
oh thank you, okay i'll let you know if this works :)

but i have a question btw doesn't it requires motorola framework as well ??
[X 2014 Q&A, Help & Troubleshooting] songs354:
I flashed the zip file that you gave but still the same error :confused:
[X 2014 Q&A, Help & Troubleshooting] mastarifla:
Ok, after a quick google search of the error code... looks like there is a syntax error, go into the updater-script and remove the device check line at the beginning, should look like this...

assert(getprop("ro.product.device") == "victara" || getprop("ro.build.product") == "victara" || abort("This package is for "victara" devices; this is a "" + getprop("ro.product.device") + ""!");

Remove that, then give it a shot, if that doesn't work, check the script and see what else needs to be removed/fixed with a edify syntax checker

Edit: Again, you are lucky I have time! Attached is an updated script, just remove the .txt extension before zipping...
[X 2014 Q&A, Help & Troubleshooting] songs354:
okay thank you i'll give it a shot and let you know :)
[X 2014 Q&A, Help & Troubleshooting] songs354:
Okay i've edited the script and flashed but same error updater process ended with error 6
[X 2014 Q&A, Help & Troubleshooting] mastarifla:
Ok, I simplified the script as much as humanely possible now, here is the entire zip, try that, if this doesn't flash then I am out of ideas :/
[X 2014 Q&A, Help & Troubleshooting] songs354:
i know you are trying your best i'm glad that you helped so much :) and its okay atleast you helped

but i dont know if it also requires the motorola framework ?

do you think so ? and okay i'll see if this works

and also if i flash this moto display zip, it flashes wihtout any issues but the thing is, custom roms has ambient display and when i flash this zip (found it on a different thread) its here http://xdaforums.com/showpost.php?p=63574299&postcount=2 there is said that this zip works on stock android for moto x 2015 but i flashed it on my moto x 2014 and it gets installed but for that i need to install moto and moto actions from google play store and then the moto app is visible on app drawer and i tap on the moto app in my app drawer i can see there moto display but when i enable moto display my ambient display also turns on as well and so when i wave hand only the ambient display triggers but not the moto display.

And for the IR sensors to work with moto display i extracted the libactions_irservice & MotoActions.odex.rar and paste those to files into system/lib and gave root permission and rebooted and those files in rar are for Motoactions but i already installed Motoactions from playstore so i just copied those files and gave root permission

i did and still it didn't worked, you can check once
[X 2014 Q&A, Help & Troubleshooting] mastarifla:
The 2015 ROM is a stock Motorola based ROM, meaning it's not AOSP based like NX ROM, so it has the Moto framework, all the underlying libraries and private binaries, so getting the Moto Apps to function on AOSP would be an extremely time intensive task...

There is much more baked into the system image that allows Moto Display to work like it does, it's not as simple as just pasting in a few files and it magically works...

You could try disabling Ambient Display, and seeing if it would then only trigger the Moto Display, Settings -> Display -> Ambient Display (Off)

Honestly, your best bet is to grab a stock Motorola based ROM and de-bloat it if you want the Moto features...

Go into TWRP and see if all the files that were copied have the right permissions, I took out the setting the permissions step when I made it as barebones as possible, you would need to add the line for the permissions, also make sure you are editing the file with Notepad++ with your EOL being UNIX based, Windows based end of line characters are not supported

Edit: Bah, here is one more attempt, I don't have any additional time today but hopefully this one will not give a bootloop...
[X 2014 Q&A, Help & Troubleshooting] songs354:
okay so you mean i have to add the permission line this time and then flash it ?? and i don't know why i got bootloop this time and now its back to normal like it was i flashed the rom again, it brought to its normal state :p

I believe if you and the cyanogenMod team teams up then it would be easy i guess it will work for sure :p
[X 2014 Q&A, Help & Troubleshooting] songs354:
Oh okay then, and thank you so much for this :) i've not even seen a dev trying to make moto apps work with custom roms but you tried and i'm glad that you did, well okay then, i'm not gonna buy your time now, it seems you're a little busy, its okay we'll deal about this tomorrow and i'll let you know what happens
[X 2014 Q&A, Help & Troubleshooting] songs354:
okay this time i guess i ended up in soft bricking :p initial logo was showing and then it returned to twrp itself lol but now its fine again, flashed the rom once again :p

any ideas :confused:

okay i managed to install it the other way, here's what i did, at first i copied moto, moto display and moto actions in the priv-app folder making three folder inside priv-app with the same name and i gave root permission to all three of them and i copied the lib files in system/lib and gave root permission as well and also copied the MotoDisplay_FWPro in system/app and gave root permission as well but the strange thing was that i already have all of the motorola permission files in my system/etc/permission folder, that's strange, okay so i rebooted and then it said unfortunately moto has stopped and then i had uninstalled only the moto and moto actions apk and i installed Moto and MotoActions from google playstore, now the moto app is showing in my app drawer and the moto display but its not working as i have ambient display, so when i turn off ambient display and turn on moto display the ambient display also turns on at the same time automatically and ambient display triggers. I don't know why :confused:
[X 2014 Q&A, Help & Troubleshooting] mastarifla:
So it looks like you are not using NX ROM anymore, and are using Resurrection, Resurrection is a CM based ROM that also bundles in an APK called CMActions, CMActions is what is causing your phone to act strangely (and exactly what I said with my first post!), try removing it (or freezing it) and see what happens after, because I think CMActions is what is actually triggering...
[X 2014 Q&A, Help & Troubleshooting] songs354:
yeah there is CMActions, i've removed CMActions and when i remove CMActions it removes the gesture settings, it doesn't removes the ambient display and i've also removed the CMsettings and removing CMsettings causes bootloops
[X 2014 Q&A, Help & Troubleshooting] mastarifla:
Well don't remove CMSettings, that's your Settings application, so you need that.

It seems like CMActions is what is enabling your gestures and controlling the gestures, not MotoActions, so you would need to edit CMActions to call MotoActions instead of AmbientDisplay, but that may not be possible (see how this gets complicated fast?)
[X 2014 Q&A, Help & Troubleshooting] songs354:
yeah it gets complicated but there are two settings in priv-app one is CMSettings and the other one is just settings but how will i edit CMActions ??

i opened the AndroidManifest.xml and the gesture_panel.xml in notepad and it this
[X 2014 Q&A, Help & Troubleshooting] songs354:
And this is the CMActions apk file
[X 2014 Q&A, Help & Troubleshooting] mastarifla:
I'm talking about the underlying code, its not the XML files, you would need to code the changes, I don't have the time to devote to that...
[X 2014 Q&A, Help & Troubleshooting] songs354:
okay how will i do that ? and how can it be done
[X 2014 Q&A, Help & Troubleshooting] mastarifla:
Go to the CyanogenMod website, check out the source code, then code the changes to it, re-build the apk, then replace it on your phone...
[X 2014 Q&A, Help & Troubleshooting] songs354:
I guess this is the source code for moto x 2014 ?

what do you mean code the changes to it ? how ? should i have to go inside cmactions ? and then
[X 2014 Q&A, Help & Troubleshooting] mastarifla:
Songs, you are a smart dude, I shouldn't have to hold your hand to figure this out!

You need to use github to download the CMActions folder, then edit the source code in an IDE, the re-compile the CMActions project/APK, then replace it on your phone and see if it works.
[X 2014 Q&A, Help & Troubleshooting] songs354:
haha i don't know, i'm not as smart as you, i'm familiar with hacking stuffs, rooting/recoveries/flashing/Xposed etc all those stuffs lol, i guess i can do this but it would be nice if you can guide me through this, okay i will try it but how will i edit the source code in a n IDE, will i be needing some tools for that and if so, what should i do there or should i have to put codes there, And yes i can get the CMActions apk in no time but it would be nice if there was someone to guide me or atleast show me the way how can it be done.

i know you are a busy person, i understand how valuable your time is but i guess i'll be needing help for this, it would be nice if you could've helped a bit since i'm not pretty familiar with this

and yes replacing and getting the CMActions apk is easy but about the codes and recompiling stuffs and all those, its a bit complicated
[X 2014 Q&A, Help & Troubleshooting] mastarifla:
You would need to learn how to program code, there are many interactive tutorials for programming in Android (it's a lot like Java), you would use an IDE like Android Studio to make the code changes, then you would compile the code in Android Studio and hopefully it will create an APK that you can put on your phone.
[X 2014 Q&A, Help & Troubleshooting] songs354:
this is actually time consuming i guess, you were right. i know coding but not too much, okay then lets see, i will try
[X 2014 Q&A, Help & Troubleshooting] mastarifla:
It's a tough road right? However, trust me, it is totally worth it in the end when you can make the changes that YOU want to see happen, it's pretty cool!

If you have an update let us know, I'm interested in how you are doing :)
[X 2014 Q&A, Help & Troubleshooting] songs354:
it is tough :p but i've looked into moto display and the motorola framework, i think it also has something to do with the motorola framework as well

and yeah will let you know if i have an update
[Other SmartWatches] C4lculated:
OK, bad news: The watch died.

Funny thing is, I didn't do anything to it, it just died on it's own. I haven't flashed any firmware at all.

The watch will not turn on and will not charge the battery. Battery measures 3.3V and does not get charged by an external charger. Trying to turn the watch on by connecting an external (good) battery also fails.

Next I will try to flash a new firmware, probably this one:

https://drive.google.com/file/d/0B_hRh3DjuBoeRHNGNUFlVFF0eVE/view?pref=2&pli=1
[Other SmartWatches] C4lculated:
If anyone is keeping track, I flashed my watch with this ROM:

https://drive.google.com/file/d/0B_hRh3DjuBoeRHNGNUFlVFF0eVE/view?pref=2&pli=1

And it got back to life. I believe this firmware is exactly like the one that my watch had originally (has the same rominfo code).

After the watch worked again, I decided to risk it and try flashing new ROMs. I ended up flashing nearly all the 32Mbit firmwares from Golem's collection. The results can be categorized into five groups (by ROMINFO code):

1. LCD Worked correctly:

ROMINFO:

a. MTK61D_BTDIALER_11C_PCB01_GPRS_MT6261_S00.LD991_RUANAN_GT08S_LCD7789_9304_CAM3A01_LANGB_V1_6

b. MTK61D_BTDIALER_11C_PCB01_GPRS_MT6261_S00.LD991_GRD_GT08S_LCD7789_9304_CAM3A01_LANGA_V1_0

2. Touchscreen matrix was rotated 180° (i.e. to press what's displayed in the bottom-left, you touch your finger to the top-right):

ROMINFO:

a. MTK61D_BTDIALER_11C_PCB01_GPRS_MT6261_S00.JIAQI_61D_YIDITONG_CAM3A01_LCD7789_LANGA_V1_1

b. MTK61D_BTDIALER_11C_PCB01_GPRS_MT6261_S00.LD991_JMX_CAM3A01_LCD7789_9304_LANGA_V1_0

3. Touchscreen does not work (pressing what is displayed doesn't work):

ROMINFO:

a. [all firmwares starting with:] GPLUS61A_11C_NX9_PCB01_GPRS_MT6261_S00.NX9_61D_240

b. MTK61D_BTDIALER_11C_PCB01_GPRS_MT6261_S00.HD_GV18_SW_V1_B

4. Display was all white:

Only one firmware: SH27_PCB01_GPRS_MT6261_S00.MAUI_11C_W13_52_MP_V5

5. Watch would not turn on:

Only one firmware: MTK61D_BTDIALER_11C_PCB01_GPRS_MT6261_S00.MAUI_11C_W13_52_MP_V2_F1

None of the firmwares with the working LCD (even those with 180° flipped lcd) had Hebrew. Some of them did have more languages like Arabic, Hindi, Farsi etc but that doesn't help me :(

So eventually I flashed my original ROM which I backed up beforehand. This brought back my IMEI, which I thought I had lost.
[Other SmartWatches] super leb:
hi bro

so you did not find any thing to do with your watch.

i have similar watch.

we cant do any nice modification for our watches?

did you try to install new watch faces?
[Other SmartWatches] C4lculated:
No, AFAIK the 32Mb models are not modifiable in any way.
[Other SmartWatches] mordor621:
In the specifications i read 64+128. 64 mb Rom + 128 Ram???

Enviado desde mi LG-D855 mediante Tapatalk
[Other SmartWatches] M3AT5O5:
Hi..i have exactly the same watch with the same firmware..how can i restore back my rom dump?? i cant do it :crying: can u help me? if you may share your backup folder would be gratefull....

thanks in advance...
[Other SmartWatches] naorway:
hello

i got the gt08 with no Hebrew , can i add hebrew?
[Other SmartWatches] Snehil_DPS_6l:
Plz help me see this https://xdaforums.com/general/xda-assist/bricked-gt08-t3537318
[Other SmartWatches] coolpixs4:
If you want to add your own language... refer to this thread from mine https://xdaforums.com/showpost.php?p=72063702&postcount=2128
[Other SmartWatches] Cuandur:
Newbie with GT08 MTK61D wanting help

Hi,

Sorry if this or similar has already been posted.

I have just bought a GT08 from wish.com. When it arrived and fully charged, it all worked fine for a few hours.

Then it decided not to accept and retain the time change, it would just go back to default immediately no matter what I tried.

I therefore thought I might try to flash the firmware, but found that this seemed to be very confusing.

From my watch screen I gleaned this info:

GT08 IMEI: 358521458986545

LD991B_V7.0_COB_A_TQHD_GT08_JXD7789_9304_LX9305_A_V8.6

[BRANCH]: 11CW1352MP

MTK61D_BTDIALER_11C

BUILD: BUILD_NO

SERIAL#:

[BUILD TIME] 2017/09/23 12:34

[MRE VERSION] - 266941256

HAL_VERNO:

I determined that my firmware was MTK61D, but I cannot seem to find the correct firmware, also any firmware I chose to run (DZ09 etc) through Mediatek FlashTool_v5.1516.00.00 came up with an error that I cannot correct: "Your BROM DLL version and DA version is not matched! Please check the DA path!"

I tried: SP_Flash_Tool_v5.1744_Win which would not accept any downloaded firmwares as they did not have a ".TXT" file only ".CFG".

So now after two days of searching I am still in the same place as I started with a watch that will not keep changed time.

Any help?????
[Other SmartWatches] oxatools:
try this flashtool version :

https://drive.google.com/open?id=1xd3HyHitBzW0x1fufchU5aFkAoY9slV4

DZ09 Firmware:

https://drive.google.com/open?id=1xJdeyZIe3n0k85e5FjZm9-0bGUrXNVRW

---------- Post added at 08:25 AM ---------- Previous post was at 08:04 AM ----------

GT08 with HEBREW Language added:

https://drive.google.com/open?id=1NNAAHE1jVyPfuS04ZG-8NHs5bfCUYryv
[Other SmartWatches] Cuandur:
Negative colours and no touch response

Thank-you for your response, I have tried your suggestions which worked with some response, unfortunately now my watch screen seems to be showing everything in colour negative and no response to touch, all I can do is remove the battery to turn it off.

Any advice?
[Other SmartWatches] oxatools:
---------- Post added at 01:28 PM ---------- Previous post was at 01:27 PM ----------

[/COLOR]

Can you Upload your Fullflash or Flash Files Backup

i will check version
[Other SmartWatches] Cuandur:
Backup

Ummmm, Noob response...Backup?

I followed the instructions that I could read (ie not Chinese) and it made no mention of Backup that I am aware, so I assume there is no backup (sorry)

I read and followed "Download operation steps.doc" but all the other docs etc are in Chinese, I didn't see which other doc I could use to start the process.
[Other SmartWatches] oxatools:
Thats bad!!!!

Never ever flash your watch or phone if you do not have a backup of original firmware.

There is no way to get it back!!!!!

Try to Download a nother Version, reflash it and hope its working!!!!