yashsingh1/xdaforums huggingface dataset:
[Samsung Gear S] 3kgt:
Thanks to the ugly digital standard always on watchface im only using the first 2 Stock watch faces to get the much better looking always on WF on regular dayily usage. I have bought and own several other WF but almost uses none cause of this.

I once again googled and tried to find if there is anything else to do and i found many devolopers asking the same question, most of them in 2014. But sadly it dose not seem to be possible!

See more info here

https://developer.tizen.org/ko/design/wearable/watch-face?langredirect=1

https://developer.tizen.org/ko/search/menu/always%20on%20watch%20face?page=2

https://developer.tizen.org/ko/development/tutorials/web-application/w3chtml5supplementary-features/watch-application?langredirect=1

Didnt go thru all the seach results for sure. But once i saw those i gave upp.!

But you can read the explanation by Samsung why it dosent work. Thow still dont get why u cant get to chose to analog always watch faces on 3d part WF!!!
[Samsung Gear S] Latrell567:
There's no 3rd party always-on watch faces for a reason...

Watch face developers (like me) use Gear Watch Designer to make our watch faces. And the Samsung Gear S is the only Gear S watch that has the option to edit the always-on watch face grayed out. Samsung won't allow us to edit the watch face for always-on, only for the Gear S2 and S3. I know I'm late, but I hope I helped.
[Samsung Gear S] Latrell567:
Great news!

Finally after all of this time, Samsung is adding support for always-on display. Developers are likely to update their watchface with always-on (like I will) on their watchface. So they are adding support now. Here's part of the changelog on their watchface designing app...

[Known issue]

* Mac OS Command + Q hotkey makes program exit without asking to save current job.

* The following features are not yet supported on Gear S :

1) Launch after install

2) Always on mode

3) Steps % source

4) Change language of Digitalclock component

5) Timezone, Calendar property

6) Connection over Bluetooth.
[Samsung Gear S] Akram.:
Always on is supported? Did u create any watch face?
[Samsung Gear S] Latrell567:
Yeah I did create a watchface, but I don't know if always-on is available yet. Actually I made multiple watchface's I'm trying to push to the store...

Lookup Centic Modern Classic. It's on the Gear S, S2, and S3 (Fit2 coming soon)
[Samsung Gear S] Akram.:
Can u check if always on is working for the faces u created
[Samsung Gear S] Latrell567:
This is the changelog... A screenshot should be attached. I don't know the XDA replying system that well.View attachment 4208925
[Samsung Gear S] Gear_S:
Always On

Hi all,

So I just got the Gear S and love it and like most people here I love the analogue always on feature. Especially since I have the same thing on my Galaxy S8.

So I found this thread and seen that they finally added support for the always on clocks so wanted to know if anyone has any update OR if anyone has updated any existing watch faces to use the analogue always on feature.

Thanks
[8525, TyTN, MDA Vario II, JasJam General] pcyoung:
I am new to BT audio, but I have come across something very strange. I have a new Motorola S9 BT headset and a Cingular 8525. I have been able to make and receive calls, pause and skip songs in Media Player 10, but I had an awful time trying to make stereo play on the headset. It delivers system beeps, alerts, and ActiveSync tones to the headset. After some hard-resets, and some troubleshooting, I found this combination does indeed deliver very nice sound quality (without the A2DPfix). The problem is that it doesn't send AAC (.m4a) songs to the BT headset. I realize that there is only limited support for AAC, (WMP doesn't recognize the META data from them) but it does play them thru the phone speaker.

Why would WMP play some formats thru the BT headset and others thru the speaker?
[8525, TyTN, MDA Vario II, JasJam General] donsaxena:
not sure but you can use tcpmp with aac plugin
[G 2014 Q&A, Help & Troubleshooting] jmangan:
I recently bought the phone specifically to install mods and to understand more about the hardware. So I'm an absolute noob but hopefully not too dumb to follow simple instructions.

I installed the cm-12-20150304-UNOFFICIAL-titan image and things were (mostly) good.

Today I saw for the first time that the phone had detected an UPDATE. It was marked NIGHTLY but I had seen other new images on the web site that didn't appear as updates so I decided to try it. The update was downloaded and then I booted into TWRP (2.8.4) to install it.

On reboot I discovered that the touchscreen didn't work any more - no response to any contact.

I booted into TWRP and found that was affected in the same way.

I attempted to use 'fastboot' to flash a clean copy of TWRP:

--> fastboot flash recovery openrecovery-twrp-2.8.4.0-titan.img

as the start of escaping from this but I keep getting a 'Mismatched partition size (recovery)'

Then I tried just booting the recovery image:

--> fastboot boot openrecovery-twrp-2.8.4.0-titan.img

But when TWRP starts up the screen still doesn't respond.

I've tried wiping the device:

--> fastboot -w

Erase successful, but not automatically formatting.

File system type raw not supported.

Erase successful, but not automatically formatting.

File system type raw not supported.

erasing 'userdata'...

OKAY [ 0.268s]

erasing 'cache'...

OKAY [ 0.082s]

finished. total time: 0.352s

and I've tried flashing a stock firmware.

--> fastboot update RETDEALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC.xml.zip

4.4.4_KXB21.85-14_cid7_CFC.xml.zip

archive does not contain 'android-info.txt'

archive does not contain 'android-product.txt'

error: update package has no android-info.txt or android-product.txt

And now I am at a loss. I've exhausted my knowledge and creativity (for now) but I don't want to make things worse (if possible) through ignorance.

Is the phone 'dead'?
[G 2014 Q&A, Help & Troubleshooting] tostado3:
i have the same issue with my moto g, i've ran out of ideas for a while but im still looking for an answer so if you happen to find out whats wrong let me know!
[G 2014 Q&A, Help & Troubleshooting] jmangan:
If I find anything I will but I suspect we both have dead phones - spares rather than repair :(.

I tried resolving the 'Mismatch partition size' by formatting the 'recovery' partition but I just get 'cannot format partition of type raw'. My suspicion is that the partitioning/formatting of the internal memory is completely corrupted but it doesn't show up as a storage device when I connect it to my computer anymore and I can't get ADB running so I can't get any more information or anyway to zap it back to base settings so I think it may be a lost cause.

On the other hand even if the partitioning/formatting is all gone to pot the phone is, somehow, finding enough of TWRP to get the initial screen loaded - where is it finding that? :confused:

I also don't understand why 'fastboot boot TWRP.img' doesn't work because that should bypass the internal storage and go straight to RAM. That makes me worry that 'somehow' the update has screwed the screen hardware even though I find that hard to believe.

Well, as I said I bought the phone for a learning experience and I've certainly had that.
[G 2014 Q&A, Help & Troubleshooting] modules:
Same here (XT1068). After bootloader update and nightly installation touchscreen is dead. Its also dead after rebooting to recobery.
[G 2014 Q&A, Help & Troubleshooting] modules:
Ended up by restoring to factory: http://xdaforums.com/moto-g-2014/development/windows-tool-moto-g-2014-xt1064-restore-t2957167

Everything is working again after several boots.

:)
[G 2014 Q&A, Help & Troubleshooting] jmangan:
How?

Exactly how did you do this? Every attempt I have made to flash the phone has failed.

Never mind, I thought you were just pointing me at firmware files. I followed the link and tried the tool but same problem.

It really doesn't like writing the partition information

Thanks for the brief hope though..
[G 2014 Q&A, Help & Troubleshooting] pranshubatra707:
I read your first post.. You did not install the stock firmware correctly! You have to extract the stock firmware zip file and flash each and every file with separate commands!

Sent from my Moto G 2014
[G 2014 Q&A, Help & Troubleshooting] jmangan:
Not really the problem

Yeah, that was my earliest efforts. I corrected that and I got the same result doing it manually as I got using the automated tool above:

Restore to Stock Android 5.0.2 for Motorola Moto G 2014 (XT1068)

target max-sparse-size: 256MB

sending 'partition' (32 KB)...

OKAY [ 0.022s]

writing 'partition'...

(bootloader) Battery Low!!

FAILED (remote failure)

finished. total time: 0.054s

target max-sparse-size: 256MB

sending 'motoboot' (2184 KB)...

OKAY [ 0.116s]

writing 'motoboot'...

(bootloader) Battery Low!!

FAILED (remote failure)

finished. total time: 0.154s

target max-sparse-size: 256MB

sending 'logo' (697 KB)...

OKAY [ 0.060s]

writing 'logo'...

(bootloader) Battery Low!!

FAILED (remote failure)

finished. total time: 0.101s

target max-sparse-size: 256MB

sending 'boot' (10200 KB)...

OKAY [ 0.445s]

writing 'boot'...

(bootloader) Battery Low!!

FAILED (remote failure)

finished. total time: 0.494s

target max-sparse-size: 256MB

sending 'recovery' (10280 KB)...

OKAY [ 0.454s]

writing 'recovery'...

(bootloader) Battery Low!!

FAILED (remote failure)

finished. total time: 0.476s

target max-sparse-size: 256MB

sending 'system' (257587 KB)...

OKAY [ 10.393s]

writing 'system'...

(bootloader) Battery Low!!

FAILED (remote failure)

finished. total time: 10.420s

target max-sparse-size: 256MB

sending 'system' (256626 KB)...

OKAY [ 10.623s]

writing 'system'...

(bootloader) Battery Low!!

FAILED (remote failure)

finished. total time: 10.742s

target max-sparse-size: 256MB

sending 'system' (257136 KB)...

OKAY [ 10.549s]

writing 'system'...

(bootloader) Battery Low!!

FAILED (remote failure)

finished. total time: 10.596s

target max-sparse-size: 256MB

sending 'system' (230052 KB)...

OKAY [ 9.315s]

writing 'system'...

(bootloader) Battery Low!!

FAILED (remote failure)

finished. total time: 9.375s

target max-sparse-size: 256MB

sending 'modem' (49356 KB)...

OKAY [ 2.494s]

writing 'modem'...

(bootloader) Battery Low!!

FAILED (remote failure)

finished. total time: 2.594s

erasing 'modemst1'...

OKAY [ 0.023s]

finished. total time: 0.024s

erasing 'modemst2'...

OKAY [ 0.078s]

finished. total time: 0.079s

target max-sparse-size: 256MB

sending 'fsg' (651 KB)...

OKAY [ 0.117s]

writing 'fsg'...

(bootloader) Battery Low!!

FAILED (remote failure)

finished. total time: 0.174s

erasing 'cache'...

OKAY [ 0.104s]

finished. total time: 0.109s

erasing 'userdata'...

OKAY [ 0.246s]

finished. total time: 0.248s

rebooting...

finished. total time: 0.002s

Press any key to exitÔÇª

There is a definite problem with the formatting/partitioning of the built in storage. I can't load ADB because the screen doesn't respond and normal flashing produces the results above. (Ignore the battery low message; it's been on charge for four hours but isn't updating the values although it shows as charging).

Thanks for contributing though.
[G 2014 Q&A, Help & Troubleshooting] pranshubatra707:
You are trying to restore to stock android lollipop? Did you receive the official android update or not? If not then your bootloader isn't updated to lollipop bootloader.. Try downloading factory image of kitkat for your device and then try restoring it maybe?

Try this

http://xdaforums.com/showthread.php?p=55373304
[G 2014 Q&A, Help & Troubleshooting] ggunzio:
are you kidding? look at your log dude!

its saying failed because of low battery. just charge it up full and try again
[G 2014 Q&A, Help & Troubleshooting] pranshubatra707:
He stated already that the device has been on charge for 4hrs.

Sent from my Moto G 2014
[G 2014 Q&A, Help & Troubleshooting] jmangan:
Giving up

Thanks, pranshubatra707, saved me pointing it out.

Well, since I can no longer see the internal storage when the phone is connected in windows, and since I can't format it with fastboot (type of 'raw' not supported) I thought maybe parted might be able to help so I plugged it into a Linux machine but parted doesn't see the storage device either.

It could be that with the various fixes MTP has been turned off/damaged (but when I had an external SD car installed Windows could still see that). But I think that's it, last throw of the dice. The partitions are gone/unrecognised. There appears to be no way to re-create/restore them and without them flashing A:WAYS fails.

I was also tempted to try booting linux on a USB stick but I doubt that the phone will boot off USB so that seems like just a waste of time - unless anyone knows better?

Thanks for the suggestions but I'm facing up to a dead phone.
[G 2014 Q&A, Help & Troubleshooting] pranshubatra707:
My touchscreen just went non responding after installing a cm12 based rom.. I erased userdata, system and cache via bootloader with fastboot commands and restored my phone to stock kitkat.. I even restored recovery.. Then touchscreen went working again!

Sent from my XT1068
[G 2014 Q&A, Help & Troubleshooting] stefan230:
Well i'm facing the same problem after flashing some CM 12 based roms which need lollipop bootloader.

If someone has a solution for the problem please tell us.
[G 2014 Q&A, Help & Troubleshooting] pranshubatra707:
You have to update your bootloader before flashing cm12 roms

Sent from my XT1068
[G 2014 Q&A, Help & Troubleshooting] stefan230:
I flashed lollipop bootloader before of course. The Rom I installed were the latest CM 12 nightly bulid and the latest Team UB build, which both need lollipop bootloader to boot.

My problem is that if the rom is booted the touch screen does not respond any more. Even if I try to restore a backup using TWRP 2.8.6.0 the touch screen does not respomd either.
[G 2014 Q&A, Help & Troubleshooting] Gabboplano:
​

that's BS, I've updated my bootloader and the ROM (CM12 official) didn't even boot, and touchscreen wasn't working in recovery

I just flashed stock KK which is what I'm running now
[G 2014 Q&A, Help & Troubleshooting] MeLlamoPablo:
My friend is having this problem with his XT1068 too. He's stuck in KitKat:

If he flashes CM12, the touchscreen won't work. CM will boot as usual, and TWRP too, but the touchscreen won't work on neither. The ROM was flashed with a Lollipop bootloader so that's not the problem.

He's on stock KitKat by following this tutorial. But when he downloads the Lollipop OTA, it won't install in the stock recovery, giving an error. Thus, he's stuck on KK.

Any ideas? Many thanks in advance!
[G 2014 Q&A, Help & Troubleshooting] gaya4:
Hi,

I posted already on antoher thread (microkat) but was sent away to supposedly here ;)

I've got the same issue, but my history was CM12->wipe+install Titan Z-> wipe+install Microkat-> restore CM12.

Using the link to restore the device

http://xdaforums.com/moto-g-2014/development/windows-tool-moto-g-2014-xt1064-restore-t2957167

you may be able to get it up and running again. This works as well with the Linux fastboot.

What I was able to discover during the troubleshooting was the output of getvar in the error case:

(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um

(bootloader) ro.build.fingerprint[1]: tsds:4.4.4/KXB21.85-14/9:user/rele

(bootloader) ro.build.fingerprint[2]: ase-keys

(bootloader) ro.build.version.full[0]: Blur_Version.21.11.14.titan_retai

(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03

(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1

(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045

(bootloader) version-baseband:

(bootloader) kernel.version[0]: Linux version 3.4.42-pINKman-kk4.4 (sluk

(bootloader) kernel.version[1]: k@titan) (gcc version 4.7 (GCC) ) #15021

(bootloader) kernel.version[2]: 9 SMP PREEMPT Thu Feb 19 15:31:25 CET 20

(bootloader) kernel.version[3]: 15

The pinkman kernel is actually related to microkat. But whatever I flashed, boot, motoboot, recovery, the output remained the same. A friend came to the idea to flash the system as well, as in the link. The output is now:

(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um

(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.99-16/10:user/rel

(bootloader) ro.build.fingerprint[2]: ease-keys

(bootloader) ro.build.version.full[0]: Blur_Version.22.41.16.titan_retai

(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03

(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1

(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045

(bootloader) version-baseband: MSM8626BP_1032.3112.96.00R EMEA_DSDS_CUST

(bootloader) kernel.version[0]: Linux version 3.4.42-ge35b7bb-00001-gf6a

(bootloader) kernel.version[1]: 3942 (hudsoncm@ilclbld28) (gcc version 4

(bootloader) kernel.version[2]: .8 (GCC) ) #1 SMP PREEMPT Wed Feb 25 01:

(bootloader) kernel.version[3]: 09:46 CST 2015

Also the baseband got a value again. I will continue in the next days.
[G 2014 Q&A, Help & Troubleshooting] galaxykeks:
Hi, I know this thread is quite old, but I ran into the same problem.

Actually I bought the phone used and it arrived like this :/

Can any of you guys help?

If I try "mfastboot format motoboot" it tells me that raw filesystem ist not supported.

The firmware restore batchfile gives me this output:

I was also wondering what this means:

"(bootloader) reason: UTAG "flashfail" configured as fastboot"

I appreciate any hint.
[Xperia Z3 Q&A, Help & Troubleshooting] zombiej79:
Anybody know of its possible to add Dolby atmos to our phones?
[Xperia Z3 Q&A, Help & Troubleshooting] rm83855:
Can you not just use Viper4Android and use the atmos irs?

http://xdaforums.com/showthread.php?t=2761895
[Xperia Z3 Compact Q&A, Help & Troubleshooting] pikeylfc:
Is there a working version on lollipop update?
[Xperia Z3 Compact Q&A, Help & Troubleshooting] crxmax:
bump
[Xperia Z3 Compact Q&A, Help & Troubleshooting] hamsup1o:
what is so hard to understand? xposed for lollipop currently needs a custom recovery to install. there is no working custom recovery for the z3c yet.

Sent from my D5803
[Xperia Z3 Compact Q&A, Help & Troubleshooting] davebugyi:
And why not looking around in the XPOSED section. And there is an alpha version out. so Yes, there is.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] epic118:
Well I installed a prerooted version of Lollipop on my Z3 D6603, and installed the Xposed Framework while in recovery. It worked before I tried to install Lolistat, after which I was stuck in a boot loop. So no, it doesn't work right now.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] ayuready1989:
ahh you tried to flash the lollipop zip along with the xposed zip and still no boot? was thinking of trying the same since after rebooting into lollipop recovery is gone
[Xperia Z3 Compact Q&A, Help & Troubleshooting] lamducthien:
Just waitting, I want to resize navigation bar and make it the same color with app when I open app
[Xperia Z3 Compact Q&A, Help & Troubleshooting] mionica:
It has nothing to do with lolistat, I expect. I have a rooted D6633 running stock LP; you flash the .zip, first boot is ok (the art optimizer runs on all app) - but it starts bootlooping once you reboot after that first (successful) boot. The only thing I did was, install a bunch of updates - not even the Xposed apk.

And btw, I did that after the first attempt, during which - on first boot - I installed the apk, appopsexposed and serjar's thing, then enabled those 2 modules, plus the greenify one which already existed (I assumed it was one of those) - but nope, it wasn't, unless the framework somehow enabled the greenify one behind my back and that caused the problem (which I find rather unlikely).
[Xperia Z3 Compact Q&A, Help & Troubleshooting] epic118:
I posted this ages ago...I have Xposed fully working now. If you're still having problems, there are solutions.

You can either install AndroPlus Kernel, which patches the thing that breaks Xposed, or install this fix http://www.theandroidsoul.com/havin...n-your-sony-xperia-device-try-this-fix-76894/
[Xperia Z3 Compact Q&A, Help & Troubleshooting] mionica:
You have to be joking.

I mean, seriously? You're pointing me to my own fix, mirrored by somebody else?! (rofl)

It's here btw, no need for externals links. And 2.1 is pretty old, too :p
[Xperia Z3 Compact Q&A, Help & Troubleshooting] epic118:
Oh god, I wasn't joking... this is embarrassing.

I'd just like to say thanks for the fix, I guess :D
[Xperia Z3 Compact Q&A, Help & Troubleshooting] mionica:
Hey, no worries :) It just felt pretty damn strange - "hey, use your stuff, from over there..." :D
[General Topics] carliquiss:
Well im begging in android development and actually i have done my first app. Its completely free And i would like you could say your opinion about it. It is an app which resolve basic electrical circuits. Im working on the theory to improve it and make easy learn it. It is called Circuity And you can download ir from Google Play here: https://play.google.com/store/apps/details?id=bycarliquiss.circuitosbasicos.com.circuitosbasicos Where can i post it in order to more people see it?
[General Topics] LS.xD:
Your link is dropbox, NOT google play...
[General Topics] carliquiss:
Sorry i put a different link hahaha i have put the correct one
[General Topics] LS.xD:
So, if you need some advertising, you could make a real THREAD (Pictures, features and so on) in here instead of a post with just a text. Is you app also available in english and other languages?
[General Topics] carliquiss:
Well i want some advertising but where can i put it? Thats the correct subforum? After i know where put it i will do the real Thread. Yes the app is in english also but i dont know if the translation its correct at 100%
[Zooper Widget General] newuser22:
hello, i've made my first widget that shows battery level with a progress bar (ram level and cpu frequency with other bars).

Now I want that the color of bar change when value is under a certain number (for example: normally is green, below 60 is yellow, below 40 is orange and below 20 is red).

I've wrote this and working: $#BLEVN#<60?[cf]#fffce109[/cf]

the logic of this is (pseudocode): if(battery.value < 60) { bar.color=yellow}

the logic that i want realize is three "if" concatenate or a "switch" (i refear to programming language).

I've tried to concatenate three of this expression but not working.

Anyone know if it can do?

thanks
[Zooper Widget General] jr67:
Use && (and) to link conditions. Since you have 3 different colors you will need 3 separate conditional statements making sure only 1 statement is true at any time. so it would look something like this:

$#BLEVN#<60&&#BLEVN#>39?yellow$$#BLEVN#<40&&#BLEVN#>19?orange$$#BLEVN#<20?red$
[Zooper Widget General] newuser22:
thanks it working :D, my error was exactly that with certain values more than one condition was true.
[Nexus 6 Q&A, Help & Troubleshooting] Ryjabo:
So, like a dummy I started playing around in *#*#3282#*#* and apparently I've done something that has now prevented an LTE connection. Even outside with a clear view (where I'd normally get good LTE signal), it stays on 3G and H and just goes back and forth. What are the defaults for T-Mobile?

Right now it shows bands 12, 25, 26, and 41 all "Off" -- from what I understand, T-Mobile doesn't use any of those... they use 2, 4, and soon 12 (not yet available where I'm at). I am 100% sure all I did was turn those other ones on, but I've since turned them back off. I've rebooted the phone, gone into airplane mode then back off... nothing I can do right now is getting me my LTE signal back.

I'll do a complete wipe and reflash the factory image if I need to but I'd prefer to avoid it if I can. I haven't changed my APN settings or anything.

Help is appreciated, thanks!
[Nexus 6 Q&A, Help & Troubleshooting] Ryjabo:
I don't know what I did but I reflashed factory 5.1 images (went ahead and rooted, too) and got my LTE back.