Related
You all should know by now I am a active member on the forum answering questions when I and by no means am I stupid when it comes to tweaking my Dash: Black but I am having a tricky question; and yes I did use the search feature but didn't find much to these specific questions.
1]. I remember I once tweaked the brightness of my dash so it wasn't as bright, does anyone know how I did that because I can't remember for the life of me.
2]. I also am wondering if there is a way to keep the back light on when I am using Opera or another app on my phone but when I go to my home screen it only stays on for like 5 seconds [which is the minimum] because I like to save battery power but I also like to read articles on my phone. Any suggestions? Thanks again guys!
have you tired START>SETTINGS>POWER MANAGMENT
bgtvfr said:
have you tired START>SETTINGS>POWER MANAGMENT
Click to expand...
Click to collapse
Yes I have, there is only so much that option will allow you to do. I am thinking there's a registry tweak somewhere that I am forgetting that would allow this to happen, or maybe a 3rd party app.
There was life before Excalibur
Look for "Tornado Lowlight" - this may work.
It has the same chipset (OMAP 850).
http://forum.xda-developers.com/showpost.php?p=4768177&postcount=32
Hi Everyone!
I just picked up a Samsung Continuum last night. Actually returned my Droid X for this phone. The allure of cracking the Ticker was too much for me to handle any longer.
So with that said, has anyone been able to find out any information on developing stuff for the ticker? I know Samsung has not released any official APIs for using it. I'm assuming, however, that the drivers and some source code for using it has been released with the OS source code.
Is this a true assumption? If so has anyone started looking into how we can take advantage of it? I'm not a ROM developer so I'm hoping I can find ways into the API with the stock ROM.
Any advice and or pointers anyone can offer (especially if you've already been looking into it!) would be greatly helpful for me. As I said, the whole reason I got this phone was to hack the ticker. I can see so many incredible uses for it that I must find a way to take advantage of it!
Thanks in advance!
Oh, and this is my first post so Hi
Honestly i have no idea what so ever.
But i really hope we can do something. I bet there is some sweet stuff the right person can do with the ticker.
We currently have one dev (who doesn't have a Continuum) and a handful of testers working on getting Odin, Clockwork Recovery, and a Ported version of CyanogenMod going. No other devs or work that I know of..... Future looks bright though...
Thank you both for the replies!
I've spent a few hours looking into the source and dedexing some files off my Continuum. Made some progress, I think. I've spent my time looking over the TickerHistory service (the activity that gets launched when you click the up/down arrow in the right side of the ticker).
I'm trying to track down what actually happens when you click the Refresh button on that screen. I know when I press it my ticker updates but I'm not sure if that's controlled by the TickerHistory or something else. That's what I'm hoping to find out.
I wish I could see LogCat outputs but the Continuum is not being picked up by this computer. I will have to wait until I'm around my development machine. In the mean time I'm going to start playing with Titanium Backup. Going to freeze a bunch of services and see if any of them cause the ticker to stop working. That should help get me some more focused direction
I'll keep ya'll posted!
Jaylach said:
Thank you both for the replies!
I've spent a few hours looking into the source and dedexing some files off my Continuum. Made some progress, I think. I've spent my time looking over the TickerHistory service (the activity that gets launched when you click the up/down arrow in the right side of the ticker).
I'm trying to track down what actually happens when you click the Refresh button on that screen. I know when I press it my ticker updates but I'm not sure if that's controlled by the TickerHistory or something else. That's what I'm hoping to find out.
I wish I could see LogCat outputs but the Continuum is not being picked up by this computer. I will have to wait until I'm around my development machine. In the mean time I'm going to start playing with Titanium Backup. Going to freeze a bunch of services and see if any of them cause the ticker to stop working. That should help get me some more focused direction
I'll keep ya'll posted!
Click to expand...
Click to collapse
Oh... sounds like we might have a dev on our hands... ....
Jaylach said:
Thank you both for the replies!
I've spent a few hours looking into the source and dedexing some files off my Continuum. Made some progress, I think. I've spent my time looking over the TickerHistory service (the activity that gets launched when you click the up/down arrow in the right side of the ticker).
I'm trying to track down what actually happens when you click the Refresh button on that screen. I know when I press it my ticker updates but I'm not sure if that's controlled by the TickerHistory or something else. That's what I'm hoping to find out.
I wish I could see LogCat outputs but the Continuum is not being picked up by this computer. I will have to wait until I'm around my development machine. In the mean time I'm going to start playing with Titanium Backup. Going to freeze a bunch of services and see if any of them cause the ticker to stop working. That should help get me some more focused direction
I'll keep ya'll posted!
Click to expand...
Click to collapse
Def keep us up to date i would love to see what can come of this!
Weudel said:
Oh... sounds like we might have a dev on our hands... ....
Click to expand...
Click to collapse
People have been known to call me that =)
I only wish I had a better knowledge of C/C++ (Unfortunately I work in a MS/Java/Adobe world) so I could help with the ROM cooking. I figured attempting to crack the ticker would be a good first step into the Android modding world =)
Well, it's nice to see we might have another Dev! Welcome to the forums!
ticker
Hey I been testing the the developers code and he had me dump the file attached. See if it helps.
http://www.megaupload.com/?d=YW8CKXZA
Logan
Thanks for the dump Logan!
I've learned a few things since I've been home. Nothing major but the new information should help point us in the right direction.
No matter what service I freeze in Titanium the ticker continues to get updates. This could mean many things. Maybe the service is hidden, maybe there isn't a service. Who knows right now. This is really what we're looking for.
Disabling some applications makes the ticker not work when clicking an item.
For example, disabling SNS Provider makes it so it can't launch email when clicking on the email icon
TickerRootView is what LogCat displays as a Tag when interacting with the ticker (ie: swiping left to right)
TickerStandbyView is what LogCat displays as a Tag when, well, the ticker goes into StandBy
Disabling a service, sending a test email, re-enabling the service is not a fun process when you have over 100 items to test
As I said, nothing major has been learned yet but this information should help to keep pointing us in the right direction. Will keep playing and will hopefully have more updates by the end of the night
The ticker easily has the most potential for customization as far as development for this phone is concerned. I'm glad you've chosen it as your starting point. Many thanks for your hard work to come.
Sent from my SCH-I400 using XDA App
Editing out my previous message I had here -
Semi-decent break through.
Ticker code lives inside the services.jar file. com.android.server.ticker.*
Now to see where I can go from here =)
Just my little wish list:
Ability to set update interval
Ability to put 4x1 widgets in the ticker
Oh, and, someone else suggested being able to drop the dock down there, to free up screen space.
Sent from my SCH-I400 using XDA App
Changing the update frequency may be fairly simple. Need to test a few things with that.
I'm still looking into how we can get a custom View down there. The neat thing is it's just a ViewFlipper rendering Views, both Java coded and XML declared.
Sent from my SCH-I400 using XDA App
I purchased my Continuum for the very same reasons. I see this baby as being one helluva phone once we wash all of the 'whiz off of it!
As odd as it sounds, I am just as interested in cracking the soft buttons just as much as the ticker. The screen being physically a 480 x 992 display with rationed space for the buttons and ticker, I'd like to go about changing the buttons. Maybe make them bigger or in a different order, or have them change depending on mode or activity. Or rotate with the orientation of the phone! Perhaps a subtle pulsing of a button to indicate a notification while the phone is timed-out.
I feel that when the phone is figured out, we'll have a damn impressive device in our hands. A developer's dream.
-EJDII
I'd like to see the Pandora menu down there when it's opened. Can't believe Samsung didn't already do this.
Sent from my SCH-I400 using XDA App
samuelhadams said:
I'd like to see the Pandora menu down there when it's opened. Can't believe Samsung didn't already do this.
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
That's a fine example of a 4x1 widget we could put down there... I would like to see Tweetdeck as well, but we don't have to agree on which ones if we just get the widget functionality....
Viva la devs!!!
ErikJDurwoodII said:
I purchased my Continuum for the very same reasons. I see this baby as being one helluva phone once we wash all of the 'whiz off of it!
As odd as it sounds, I am just as interested in cracking the soft buttons just as much as the ticker. The screen being physically a 480 x 992 display with rationed space for the buttons and ticker, I'd like to go about changing the buttons. Maybe make them bigger or in a different order, or have them change depending on mode or activity. Or rotate with the orientation of the phone! Perhaps a subtle pulsing of a button to indicate a notification while the phone is timed-out.
I feel that when the phone is figured out, we'll have a damn impressive device in our hands. A developer's dream.
-EJDII
Click to expand...
Click to collapse
The icons for the ticker (like the music player and the weather widget and etc) and the soft keys are in framework-res.apk just in case someone didn't know I just can't find am appropriate way to sign the apk back up once you unpack it so that the phone doesn't reject it xP lol
Sent from my SCH-I400 using XDA App
No progress to speak of today, unfortunately. Still trying to figure out if it's possible to add our own views to the ticker. Quite honestly, I'm not all that optimistic. At least not with having the ability to do it without requiring a custom SOMETHING (services.jar, ROM, etc).
The reason I say this is it looks like all the widgets are hard coded into the Ticker code. That may or may not be a bad thing. If I can find out where those widgets are added we may be able to tap into it.
I've also started looking into changing the update frequency for the facebook/twitter/myspace ticker widget. If I could figure out how to get the /data/data folder off my phone it would be super helpful. I guess I don't know ADB well enough. Even though I'm rooted every time I do an adb pull /data/data /usr/development/continuum/data I get a permission denied error. I know it's possible but for some reason I'm struggling with it, lol.
Will keep ya'll posted! I'll start looking into the "button bar" as well. See if I can come up with anything there.
I've been looking into the services that the ticker depends on for its feeds, and widgets, and it's all very interesting to me. I'm definitely going to be diving into this once I get clockwork up and running for everyone. Stay in touch and maybe we could co-op this one. (;
Just wondering, but is there any way to increase the pulsing speed of the trackpad LED?
A lot of people have suggested LedMe Know but it doesn't have support for Google Voice (which I use for sms) and it flashes the trackpad, rather than pulses.
I've also tried Light Flow and although it pulses the trackpad and supports Voice, it doesn't change the speed of the pulse
Any suggestions?
Have you tried playing with the custom timing settings in Led me know?
If gvoice isn't supported, then perhaps it wont work....sry if it doesn't.
Well, like I said up top, it only flashes the led, instead of the pulses, regardless of any speed settings.
Plus no Google Voice in LedMe Know. Light Flow does support it (so its definately possible ), but it does not alter the pulse frequency so it doesn't add anything that stock didn't already do.
Sent from my T-Mobile G2 via telegram
Maybe you could contact the app developers and get them to add the feature(s)?
Some can be surprisingly responsive.
Good suggestion...but not quite the solution I'm looking for since LedMe flashes rather than pulses and I'd prefer if I didn't have to keep an app in memory just to change the frequency of a stock feature :/
Maybe there's a way to modify the lights.vision.so or something?
EDIT: I doubt the developer would try his hand at pulsing rather than flashing since it seems I'm just a minority who prefers the trackpad led rather than the speaker led. Also this seems like a device specific feature and the dev says in the app description: "only available at the moment for htc desire 2.2" so I doubt he has a DZ to test on... I found
EDIT2: I found exactly what I was looking for (http://forum.xda-developers.com/showpost.php?p=5609688&postcount=25) but sadly its only for Nexus One. I'm messaging the developer to see if maybe he'd port it over...
Sent from my T-Mobile G2 via telegram
Yeah I dont know much about editing those files, but some app devs are helpful. It might actually just be a quick edit for them to gain compatibility with GVoice.
I only use LED me know to flash my trackpad light really fast, upon arrival of sms' through tmobile carrier/handcent tho.
I hope you figure something out. I would like like it to pulse fast rather then just blink.
daaango said:
Good suggestion...but not quite the solution I'm looking for since LedMe flashes rather than pulses and I'd prefer if I didn't have to keep an app in memory just to change the frequency of a stock feature :/
Maybe there's a way to modify the lights.vision.so or something?
EDIT: I doubt the developer would try his hand at pulsing rather than flashing since it seems I'm just a minority who prefers the trackpad led rather than the speaker led. Also this seems like a device specific feature and the dev says in the app description: "only available at the moment for htc desire 2.2" so I doubt he has a DZ to test on... I found
EDIT2: I found exactly what I was looking for (http://forum.xda-developers.com/showpost.php?p=5609688&postcount=25) but sadly its only for Nexus One. I'm messaging the developer to see if maybe he'd port it over...
Sent from my T-Mobile G2 via telegram
Click to expand...
Click to collapse
Switch to an MIUI rom. It has the feature built in.
I appreciate pulsing the trackpad LED as well. However it's too slow a pulse at default speed, to be able to quickly peek at your phone and be able to tell if you have a message or not.
xREVOx: What exactly is this feature called? I want to look around and see if it will be included in the net CyanogenMod version.
Proxin said:
I appreciate pulsing the trackpad LED as well. However it's too slow a pulse at default speed, to be able to quickly peek at your phone and be able to tell if you have a message or not.
xREVOx: What exactly is this feature called? I want to look around and see if it will be included in the net CyanogenMod version.
Click to expand...
Click to collapse
I'm not using the MIUI rom right now, but it was called either Pulse Frequency or Pulse Delay. Default is 9 seconds. You can change it to as little as a 1 second delay.
I might have to flash it just to check it out and see how it works.
Currently I have LED me know flash my trackpad at 100 milisec. on and 100 milisec. off. Flashes fast and I notice it right away when checking for messages.
I just rather have the pulsing close to that speed.
Well I guess its nice to know that there's an actual solution... I wonder how hard it is to extract from miui rom?
I was looking around for the source of miui, but apparently its not released by their dev team...?
Sent from my T-Mobile G2 via Words With Friends for 42 points
daaango said:
Well I guess its nice to know that there's an actual solution... I wonder how hard it is to extract from miui rom?
I was looking around for the source of miui, but apparently its not released by their dev team...?
Sent from my T-Mobile G2 via Words With Friends for 42 points
Click to expand...
Click to collapse
You could try just flashing the exact file that controls it to your phone, from the MIUI rom... not sure exactly what it is though.
Proxin said:
You could try just flashing the exact file that controls it to your phone, from the MIUI rom... not sure exactly what it is though.
Click to expand...
Click to collapse
I believe its in Settings? I saw a video of MIUI running on a G2 and Trackpad Settings was in the Settings menu...not sure if it contains the pulse frequency but meh. If it is, I don't think it'll be too smart to flash it but idk.
Sent from my T-Mobile G2 via Words With Friends for 42 points
Someone asked what the point of the new .39 kernel is, well here's a new feature I've coded up that was made possible due to the more modern kernel.
I have modified the touchscreen driver in the kernel so that the zoom bar is now working, and it sends signals to Android that make it think you're sending a multitouch pinch-to-zoom.
I've got it set so that it sends an input from the center of the screen. As you slide right, the driver tells Android two fingers are moving apart from the center. As you slide left, the driver tells Android two fingers are sliding from the sides towards the center. The net result is that the zoom bar works in any app that supports pinch to zoom.
I've uploaded a video showing it in action:
http://www.youtube.com/watch?v=GRWUzPveU14
I'm going to submit this patch soon, and I'd like it if some people would try it out and give any feedback before I do so. I suppose things to pay attention to would be any increased wonkiness in the touch response, as well as boundaries for the zoom bar. Also, if you have a better idea on how this should work, it's now or never.
Unfortunately, this is a modification of the new .39 kernel, which means that a lot of things are not working on it, and this test kernel will most likely not be suitable for daily use if you like wifi and the other things that don't work on .39 yet.
In order to install you must do the following:
1. Replace your zImage with the one attached.
2. Use the .39 haret (included in the zip for your convenience) with the .39 startup.txt line (set initrd_offset 0x00a00000)
3. Place the included android.hardware.touchscreen.multitouch.xml under /system/etc/permissions. I tried bind-mounting it from conf, but for some reason that did not work for me. If you don't do add this permission file, the multitouch points will still be sent to Android (and will show up in the app Multitouch Test), but Google's own apps like Browser will ignore them.
Amazing.
First time, I can use this since ages.
Unfortunately, my phone has become very sluggish with this test kernel.
Tippfehler said:
Amazing.
First time, I can use this since ages.
Unfortunately, my phone has become very sluggish with this test kernel.
Click to expand...
Click to collapse
I totally agree with that!
Rhod100_nl
Nice work!
I assume pinch-to-zoom is pretty well supported in Android. Does this mean the zoom bar is now more supported (for zooming, button hacks aside) in XDAndroid than it ever was in officially baked HTC WinMo?
Impressive. Thanks for the vid.
I'm planning to give the .39 kernel a quick test run, hopefully this weekend. There's some software that crashes on me on open now and I'd like to see if its any different with .39. I'll try to give this a whirl then.
As for functionality, the p2z is cool, but not something I've been pining for. I don't know exactly what your plans are, but I'd love it if that function could be switched off easily (a line in startup.txt?), so future hacks creating, say, soft buttons on the bar instead could be more easily implemented.
fortunz said:
I'd love it if that function could be switched off easily (a line in startup.txt?), so future hacks creating, say, soft buttons on the bar instead could be more easily implemented.
Click to expand...
Click to collapse
well that bar has been designed to be a zoom bar. you can do whatever you want with it but always a zoom bar remains using it as a "virtual button" is possible but on the phone you will always have the magnifying glasses printed
What you suggest is an hack to the original zoom bar design and it's not as useful as the zoom function (that on our resistive single touch screens is missing)
LinoX said:
What you suggest is an hack to the original zoom bar design and it's not as useful as the zoom function (that on our resistive single touch screens is missing)
Click to expand...
Click to collapse
All I suggest is flexibility. I'm not trying to steal your zoom
fortunz said:
All I suggest is flexibility. I'm not trying to steal your zoom
Click to expand...
Click to collapse
All you are actually suggesting is complexity, indeed. A "soft" array button must be handled properly by the kernel / os / applications and it is a lot more than "one hack" for a function that will be probably not used because the zoom is a bit more important than a button
I'm going to have to break out the bold, aren't I? I'm not asking for soft buttons. I'm asking that this implementation be flexible enough to allow for future hacks like soft buttons, whether they are your favorite or not. I don't even know if the request is necessary, but I never imagined it would be controversial. If that flexibility really is too complex, forgive the request and ignore it.
It's "controversial" because you are asking for a strip of capacitive touch to turn into buttons. As the OP indicated, implementing this requires not only a new kernel+touch, but files in system.ext2, so the system _thinks_ you have p2z when you still have a resistive screen. So what you are asking for is to make that "flexible" when the base feature has barely been coded+tested.
If you truly want capacitive soft buttons, look at the DIAM or RAPH. Back way then (2.0ish), the LED on the bottom button-panel/scroll would light up on finger contact (not pressed) when running xdandroid. It was more of a "wow it's cool" thing because it was a strip of capacitive touch with 5+ LEDs. I don't remember if the p2z worked with the center scrolly or not...
-- Starfox
fortunz said:
I'm going to have to break out the bold, aren't I? I'm not asking for soft buttons. I'm asking that this implementation be flexible enough to allow for future hacks like soft buttons, whether they are your favorite or not. I don't even know if the request is necessary, but I never imagined it would be controversial. If that flexibility really is too complex, forgive the request and ignore it.
Click to expand...
Click to collapse
Alright, settle down children.
I think you're looking a little too far ahead fortunz, but that's just my opinion.
To manekineko - holy crap dude, that was fast! Nice work, definitely want to check it out.
But if you're on CDMA... then I'd imagine the experience is painful with data connected... still, great work. I'm sure the .39 kernel folk will gladly accept your patches, that's seriously cool!
arrrghhh said:
Alright, settle down children.
Click to expand...
Click to collapse
Bu... but... even with the bold starfox still couldn't get it Nevertheless, I am reaching out for my zen.
I think you're looking a little too far ahead fortunz, but that's just my opinion.
Click to expand...
Click to collapse
Fair enough. I was just trying to avoid any potential "now or never" deadline issues.
arrrghhh said:
Alright, settle down children.
I think you're looking a little too far ahead fortunz, but that's just my opinion.
To manekineko - holy crap dude, that was fast! Nice work, definitely want to check it out.
But if you're on CDMA... then I'd imagine the experience is painful with data connected... still, great work. I'm sure the .39 kernel folk will gladly accept your patches, that's seriously cool!
Click to expand...
Click to collapse
Yeah, after I got the .39 kernel, it took me like 30 minutes to get it working for the first time, and then a bit more time to clean up the code to look nicer.
Whereas I'd spent hours banging my head on the wall with .27, never quite sure where the problem was, since I thought I was sending all the right events in the driver. Now I know I was sending the right events (because it works in .39) which means that the problem must have been something in the kernel not passing along the multitouch sync events (I know it's that event missing from debugging the userland). That narrows things down quite a lot, but I don't think I really want to go back and spend the time fixing things up in the obsolete .27 kernel though.
Awesome work Manekineko!
I think the zoom bar code will be a fun addition to future cooks. It will be fun to see what uses people come up with. Be it soft buttons or just a zoom bar. Either way, cool stuff.
There never is and will never be a "now or never" with Android. If you want a feature and it can be coded, take the source and run with it. You may run into walls, and there will be many, but at least you can try - that's the beauty of open source.
-- Starfox
fortunz said:
I assume pinch-to-zoom is pretty well supported in Android. Does this mean the zoom bar is now more supported (for zooming, button hacks aside) in XDAndroid than it ever was in officially baked HTC WinMo?
Click to expand...
Click to collapse
Yes it does
fortunz said:
As for functionality, the p2z is cool, but not something I've been pining for. I don't know exactly what your plans are, but I'd love it if that function could be switched off easily (a line in startup.txt?), so future hacks creating, say, soft buttons on the bar instead could be more easily implemented.
Click to expand...
Click to collapse
Thanks for the suggestion. I'm not going to be implementing it at this time, but the way things are structured in the code, it wouldn't be hard for it to be done by someone interested in the future.
When I was fighting with getting .27 working, I considered at one point simply turning the zoom bar into soft buttons. However, I was never able to come up with a practical use for soft buttons on the zoom bar. The thing that makes it hard is that the list of keyevents Android understand are extremely limited.
You can see for yourself here:
http://developer.android.com/reference/android/view/KeyEvent.html
Set the filter level to API level 8 to see what's available on Froyo. Unfortunately, really useful keyevents like button zoom in/out only became available in Honeycomb (API level 11).
I'm not sure that soft buttons for things like home or power or search would be very convenient when they're not visible on the physical device, are right next to the screen, and could instantly rip you out of what you're doing.
Just in case anyone happens across this that is interested in doing so, here is how you'd probably want to do it:
Android's KeyInputQueue.java, which handles inputs from the touchscreen (and everything else). Do a search for readVirtualKeys and see that it reads from /sys/board_properties/virtualkeys.tssc_manager. Edit the driver so that it generates the virtualkeys file in the format specified in KeyInputQueue, and disable all of the topaz/rhodium zoom bar code.
manekineko said:
the way things are structured in the code, it wouldn't be hard for it to be done by someone interested in the future.
Click to expand...
Click to collapse
Flexible structure is really the only thing I was after. Glad it was already in the plan. And thanks for laying out some possible paths to additional features as well.
Thanks button activated! Great work!
whoops thanked fortunz accidentally -1 buddy
If anybody could find an app that supports touch pressure on a regular kernel on XDAndroid, that would be really helpful. I need to check how much we support pressure to start with and make sure that still is the case with this patch.
I tried Crayon Doodle Lite from the Market, which claims to support pressure, but I'm not seeing any pressure on a regular no-zoom-bar build, so that's not working as a test. Or it may simply be the case that pressure touch has always been broken.
arrrghhh said:
I think you're looking a little too far ahead fortunz, but that's just my opinion.
Click to expand...
Click to collapse
+1
Developing in a way that MAYBE, ONE DAY, SOMEONE, WILL (or just will not) adds unuseful complexity to every software.
BTW: Great work manekineko
Good job, but....
Broke my internet (is zoom tested with gprs or is it CDMA only ?)
Kernel.39+RIL2+F22 is running fine on my R100. After drop in of the Zoom-zImage, connection died.
Without zoom with working connection (SMS error is my operator NOT android):
k39_no_sms_log(537).txt
Zoom added - go to line 552
k39-zoom_no_data(552).txt
I'm putting this in themes for lack of a better idea. If there's a more appropriate forum, moderator please move it. I am loving my 360 with one exception and I'm hoping some genius dev will feel the same as I and come up with a solution, either through a custom app or otherwise. I feel like ambient mode should give you the option to keep the screen on when dimmed. What I would like specifically, is for the watch to stay exactly the same, second hand and all, only completely dim when not "active" and then when lifted to look at it, come on with the appropriate auto brightness level. Is there an app for this already that I've missed? Please feel free to discuss here if you have an opinion or suggestions of any kind. Just behave. We all know the battery consequences. Everyone has their own ideas of how they'd like their devices to work. I'd love to hear what people think, would like, or are currently doing with their new watches. I don't mind a little OT. Just stay in the general vicinity of the topic here.
Oh, let me add that I've actually come darn close using an app called swipify. It's a launcher for Android wear. Very neat little app. The only thing about it is I can't use auto brightness with it. Well I can but then it will stay bright in a bright room even when not looking at it.
Thanks for reading!