Twitter has been trying to figure out ways to maximize its 140 character limit for tweets since last year. The company earlier said that it had been working on new ways to let users express more without raising 140 character limit. As such, Twitter has already stopped counting media files such as links, polls, GIFs, photos, videos and quotes against 140 character limit. Now, the company is taking things even further with a new change. Starting today, Twitter is rolling out a new update which will stop counting usernames while replying to a conversation.
To make this happen, Twitter is making changes to the way you reply to someone in a conversation. With this update, whenever a user replies to a tweet, usernames of whom they're replying to will appear above the tweet, as opposed to inside the tweet text, so that the user have more space left for the conversation. According to Twitter, this change will make things less cluttered as it will allow you to focus on the discussion "rather than seeing lots of @usernames."
Following are the changes Twitter is making with this new update:
Who you are replying to will appear above the Tweet text rather than within the Tweet text itself, so you have more characters to have conversations.
You can tap on "Replying to…" to easily see and control who's part of your conversation.
When reading a conversation, you'll actually see what people are saying, rather than seeing lots of @usernames at the start of a Tweet.
Twitter says it has taken into consideration users' feedback and also done some research and experimentation before implementing these changes. Twitter also claims that their tests have found that with this new experience, people are engaging more with conversations on Twitter.
The new experience is already live on the web version of Twitter and an app update bringing this change should be on the way for Android and iOS.
What are your thoughts on this new experience? Have you tried it out yet? Let us know in the comments below!
Twitter has been trying to figure out ways to maximize its 140 character limit for tweets since last year. The company earlier said that it had been working on new ways to let users express more without raising 140 character limit. As such, Twitter has already stopped counting media files such as links, polls, GIFs, photos, videos and quotes against 140 character limit. Now, the company is taking things even further with a new change. Starting today, Twitter is rolling out a new update which will stop counting usernames while replying to a conversation.
To make this happen, Twitter is making changes to the way you reply to someone in a conversation. With this update, whenever a user replies to a tweet, usernames of whom they’re replying to will appear above the tweet, as opposed to inside the tweet text, so that the user have more space left for the conversation. According to Twitter, this change will make things less cluttered as it will allow you to focus on the discussion “rather than seeing lots of @usernames.”
Following are the changes Twitter is making with this new update:
Who you are replying to will appear above the Tweet text rather than within the Tweet text itself, so you have more characters to have conversations.
You can tap on “Replying to…” to easily see and control who’s part of your conversation.
When reading a conversation, you’ll actually see what people are saying, rather than seeing lots of @usernames at the start of a Tweet.
Twitter says it has taken into consideration users’ feedback and also done some research and experimentation before implementing these changes. Twitter also claims that their tests have found that with this new experience, people are engaging more with conversations on Twitter.
The new experience is already live on the web version of Twitter and an app update bringing this change should be on the way for Android and iOS.
What are your thoughts on this new experience? Have you tried it out yet? Let us know in the comments below!
The company behind the successful OnePlus 3 and OnePlus 3T is always looking to expand its range of products, and in recent months it has begun offering a number of accessories, swag and gear including clothing and bags.
Now, OnePlus feels ready to leverage its Dash Charge technology into a whole new class of product: highly-limited Energy Drinks. The new Dash Energy will become available soon, and you'll be able to get a taste of its electrolyte-infused performance this April 1st in select locations including London and India. If you have been looking for a new kind of gamer fuel, look no further. Just take a look at this sweet specs sheet:
Best Consumed By 03/2018
Servings per Container: 1
Calories:
0 cal
Total Fat:
0 g
Saturated Fat:
0 g
Trans Fat:
0 g
Cholesterol:
0 mg
Sodium:
95 mg
Total Carbohydrate:
0 g
Dietary Fiber:
0 g
Sugar:
0 g
Protein:
0 g
Vitamin A, Vitamin C, Calcium, Iron:
0%, 0%, 0%, 0%
Clearly nutritional. OnePlus claims that their energy drink technology allows the company to "unlock a person's hidden potential" by limiting their sleep cycles to just half an hour a day, inline with their Dash Charge's "A Day's Power in Half an Hour" marketing slogan. I've received one of these Dash Charge energy drinks, and while I can't say that I am sure it has passed any kind of regulation, it tasted pretty good… Well, kind of. Good enough, I guess? I've had worse in Argentina.
I know what you are thinking — what on Earth is OnePlus doing? I honestly have no clue either, but if you want to check it out for yourself, on April 1st you'll be able to get a taste in Bishops Square, Spitalfields, London from 12PM to 4PM, and you can also visit the OnePlus Experience Store in Bangalore, India should that be closer to you. If you happen to reside in the EU, you can also enter the raffle online for a chance to win a four-pack of this highly limited energy drink.
So there you go. If you saw OnePlus teasing a Dash Charge announcement yesterday and thought you'd be getting something awesome like a new power pack, I'd like to say I'm sorry. Also, hahaha, why would you expect that? Have you forgotten about the OnePlus 3T Colette Edition? In any case, we'll be doing an in-depth review of the Dash Energy later this afternoon on social media, so stay tuned for that (if you really want to waste your time).
Excited for this new OnePlus product? Fool around in the comments below and let us know what you think.
from xda-developers http://ift.tt/2nGMkgF via IFTTT
The company behind the successful OnePlus 3 and OnePlus 3T is always looking to expand its range of products, and in recent months it has begun offering a number of accessories, swag and gear including clothing and bags.
Now, OnePlus feels ready to leverage its Dash Charge technology into a whole new class of product: highly-limited Energy Drinks. The new Dash Energy will become available soon, and you’ll be able to get a taste of its electrolyte-infused performance this April 1st in select locations including London and India. If you have been looking for a new kind of gamer fuel, look no further. Just take a look at this sweet specs sheet:
Best Consumed By 03/2018
Servings per Container: 1
Calories:
0 cal
Total Fat:
0 g
Saturated Fat:
0 g
Trans Fat:
0 g
Cholesterol:
0 mg
Sodium:
95 mg
Total Carbohydrate:
0 g
Dietary Fiber:
0 g
Sugar:
0 g
Protein:
0 g
Vitamin A, Vitamin C, Calcium, Iron:
0%, 0%, 0%, 0%
Clearly nutritional. OnePlus claims that their energy drink technology allows the company to “unlock a person’s hidden potential” by limiting their sleep cycles to just half an hour a day, inline with their Dash Charge’s “A Day’s Power in Half an Hour” marketing slogan. I’ve received one of these Dash Charge energy drinks, and while I can’t say that I am sure it has passed any kind of regulation, it tasted pretty good… Well, kind of. Good enough, I guess? I’ve had worse in Argentina.
I know what you are thinking — what on Earth is OnePlus doing? I honestly have no clue either, but if you want to check it out for yourself, on April 1st you’ll be able to get a taste in Bishops Square, Spitalfields, London from 12PM to 4PM, and you can also visit the OnePlus Experience Store in Bangalore, India should that be closer to you. If you happen to reside in the EU, you can also enter the raffle online for a chance to win a four-pack of this highly limited energy drink.
So there you go. If you saw OnePlus teasing a Dash Charge announcement yesterday and thought you’d be getting something awesome like a new power pack, I’d like to say I’m sorry. Also, hahaha, why would you expect that? Have you forgotten about the OnePlus 3T Colette Edition? In any case, we’ll be doing an in-depth review of the Dash Energy later this afternoon on social media, so stay tuned for that (if you really want to waste your time).
Excited for this new OnePlus product? Fool around in the comments below and let us know what you think.
from xda-developers http://ift.tt/2nGMkgF
via IFTTT
The Android O Developer Preview has only been out for a week, but we’re quickly discovering more and more potential uses for all of the new features. One of the features we’ve been most excited about is the new navigation bar customizer found in System UI Tuner.
On initial inspection, Google’s implementation seems quite barebone. While you are able to add a new navigation key to the left and right of your existing keys, any key that you add will be permanently situated on your navigation bar. Unfortunately, that makes this feature useless for many people, as many of the keys you would want on the nav bar only work under specific circumstances. But as we’ve shown you before, it is in fact possible to enable specific nav bar keys under your own customizable conditions. In this tutorial, we’ll show you how to enable media playback control buttons in your navigation bar when Google Play Music, or any other music app, is playing music.
Thanks Eli Irvin for testing this for me, and capturing this screen recording!
Tasker is necessary because it is the automation app we’re using to detect what application we’re in and send commands through the SecureTask plug-in, which is what will handle changing our navigation bar. Once you’ve installed these applications, we need to set them up.
In order to detect when music is being played, we need to enable Notification Access for the Notification Listener plugin. Doing so is very quick, simply go to Settings and search for “notification access” in the search bar. Open the settings page, look for Notification Listener, and grant it access to read notifications.
Next, we need to grant SecureTask the ability to modify system settings on our device. In order to do so, we have to grant SecureTask a special permission known as WRITE_SECURE_SETTINGS which is normally inaccessible to regular applications, but can be granted manually by a user through the use of ADB. Thus, you’ll need to have ADB up and running on your machine to get this working. Fortunately, granting this permission is a one-time thing, and we’ll be using SecureTask in future Android O-related tutorials, so I definitely advise you doing this now. If you’ve followed my previous tutorials where I told you to install AutoTools, SecureTask is less feature-filled but it has just enough for our needs here.
Setting up ADB
The first thing you’ll need to do is download the ADB binary for your particular OS. You can do so here. Once you’ve downloaded them, you need to then make sure you have the proper driver if you’re on Windows.
Once you’ve extracted the binary to a separate folder and have installed the driver, we need to next enable USB Debugging on the smartphone. In order to do so, open up Settings and go to About Phone. Tap on Build Number 7 times until you get a dialog telling you that you’ve unlocked Developer Options. You can access Developer Options in Settings now. Apparently in Android O, you have to enter your pin/password before you can open Developer Options. Do so and look for USB Debugging, then enable it.
Now plug in your phone and open up a command prompt in the same directory where you extracted the ADB binary. (Windows users, hold shift+right-click in that folder and select “open command prompt here.”) Type adb devices into the command prompt. You’ll see a message that the ADB server is being started, then on your phone you’ll see a prompt asking you to grant your computer ADB access. Accept it. Now when you enter adb devices into the command prompt, you should see your device’s serial number, if so then you were successful.
Granting WRITE_SECURE_SETTINGS to SecureTask
With an ADB command prompt opened up, enter the following command to grant SecureTask the requisite permission.
adb shell pm grant com.balda.securetask android.permission.WRITE_SECURE_SETTINGS
SecureTask will now have the ability to modify system settings without root access! Now we’re ready to move on to Tasker.
Setting up the Tasker Profiles
We’ll be creating two separate Tasker Profiles here. One that reacts to when our music player of choice (in my example, Google Play Music) starts music playback (its notification has been posted), and one that reacts to when that same music player’s notification has been dismissed.
Open up Tasker and create a new Profile by pressing the + icon in the bottom right. We’ll start with making a Profile that triggers when the music player’s notification has been posted. Name the Profile “Enable Media Nav Keys” and select an Event Context. Go to Plugin –> Notification Listener –> Notification Listener. For the Notification Event, select Posted and under Apps select the applications that you want to monitor (eg. Google Play Music).
Once you’re done, back out and Tasker will ask you to attach a Task to this Profile. You can name the Task, but it’s not necessary. Just hit the checkmark to enter the Task editing screen. Once you’re in, we’re going to add two Actions to this Task.
A1: Plugin –> SecureTask –> Secure Settings. Action: Write. Setting: secure sysui_nav_bar_left. Value: key(88:com.android.systemui/2131230907). This is KEYCODE_MEDIA_PREVIOUS and will show up as a left arrow in your navigation bar.
A2: Plugin –> SecureTask –> Secure Settings. Action: Write. Setting: secure sysui_nav_bar_right. Value: key(87:com.android.systemui/2131231004). This is KEYCODE_MEDIA_NEXT and will show up as a right arrow in your navigation bar.
Next up, we’ll create the second Profile that triggers when the music app’s notification is dismissed. This Profile will get rid of the media control keys when the notification has been dismissed. Create a new Profile and name it “Disable Media Nav Keys.” Again create an Event Context and select the Notification Listener plugin. This time, for the Notification Event select Removed but again select the same music app you want monitored.
Again add a Task (without a name is fine) and create the following two actions:
These two actions will clear your navigation bar keys so the media playback control keys will no longer be there.
That’s it! Now when you start music playback, you’ll see additional keys on your navigation bar to control media, but when you dismiss your music player’s notification, these keys will disappear.
Download and Import
As with all Tasker related tutorials, we will be providing the XML files you can download and import. Download the prf.xml files from AndroidFileHost below and save them to your internal storage. Open up Tasker and long-press on the Profiles tab up top until you see an Import button. Tap on that and look for the XML files you just saved, then select them to import them (you’ll have to do this one by one). Make sure you have granted Notification Access to Notification Listener enabled and have granted the WRITE_SECURE_SETTINGS permission to SecureTask as mentioned in my article, otherwise these Profiles will not do anything on your phone!
If you’re wondering what else we can accomplish with SecureTask and Android O, stay tuned to the XDA Portal because we have a lot more to share. Expect more tutorials on how you can make your navigation bar in Android O accomplish many useful functions!
from xda-developers http://ift.tt/2oElDqa
via IFTTT
The Android O Developer Preview has only been out for a week, but we're quickly discovering more and more potential uses for all of the new features. One of the features we've been most excited about is the new navigation bar customizer found in System UI Tuner.
On initial inspection, Google's implementation seems quite barebone. While you are able to add a new navigation key to the left and right of your existing keys, any key that you add will be permanently situated on your navigation bar. Unfortunately, that makes this feature useless for many people, as many of the keys you would want on the nav bar only work under specific circumstances. But as we've shown you before, it is in fact possible to enable specific nav bar keys under your own customizable conditions. In this tutorial, we'll show you how to enable media playback control buttons in your navigation bar when Google Play Music, or any other music app, is playing music.
Thanks Eli Irvin for testing this for me, and capturing this screen recording!
Tasker is necessary because it is the automation app we're using to detect what application we're in and send commands through the SecureTask plug-in, which is what will handle changing our navigation bar. Once you've installed these applications, we need to set them up.
In order to detect when music is being played, we need to enable Notification Access for the Notification Listener plugin. Doing so is very quick, simply go to Settings and search for "notification access" in the search bar. Open the settings page, look for Notification Listener, and grant it access to read notifications.
Next, we need to grant SecureTask the ability to modify system settings on our device. In order to do so, we have to grant SecureTask a special permission known as WRITE_SECURE_SETTINGS which is normally inaccessible to regular applications, but can be granted manually by a user through the use of ADB. Thus, you'll need to have ADB up and running on your machine to get this working. Fortunately, granting this permission is a one-time thing, and we'll be using SecureTask in future Android O-related tutorials, so I definitely advise you doing this now. If you've followed my previous tutorials where I told you to install AutoTools, SecureTask is less feature-filled but it has just enough for our needs here.
Setting up ADB
The first thing you'll need to do is download the ADB binary for your particular OS. You can do so here. Once you've downloaded them, you need to then make sure you have the proper driver if you're on Windows.
Once you've extracted the binary to a separate folder and have installed the driver, we need to next enable USB Debugging on the smartphone. In order to do so, open up Settings and go to About Phone. Tap on Build Number 7 times until you get a dialog telling you that you've unlocked Developer Options. You can access Developer Options in Settings now. Apparently in Android O, you have to enter your pin/password before you can open Developer Options. Do so and look for USB Debugging, then enable it.
Now plug in your phone and open up a command prompt in the same directory where you extracted the ADB binary. (Windows users, hold shift+right-click in that folder and select "open command prompt here.") Type adb devices into the command prompt. You'll see a message that the ADB server is being started, then on your phone you'll see a prompt asking you to grant your computer ADB access. Accept it. Now when you enter adb devices into the command prompt, you should see your device's serial number, if so then you were successful.
Granting WRITE_SECURE_SETTINGS to SecureTask
With an ADB command prompt opened up, enter the following command to grant SecureTask the requisite permission.
adb shell pm grant com.balda.securetask android.permission.WRITE_SECURE_SETTINGS
SecureTask will now have the ability to modify system settings without root access! Now we're ready to move on to Tasker.
Setting up the Tasker Profiles
We'll be creating two separate Tasker Profiles here. One that reacts to when our music player of choice (in my example, Google Play Music) starts music playback (its notification has been posted), and one that reacts to when that same music player's notification has been dismissed.
Open up Tasker and create a new Profile by pressing the + icon in the bottom right. We'll start with making a Profile that triggers when the music player's notification has been posted. Name the Profile "Enable Media Nav Keys" and select an Event Context. Go to Plugin –> Notification Listener –> Notification Listener. For the Notification Event, select Posted and under Apps select the applications that you want to monitor (eg. Google Play Music).
Once you're done, back out and Tasker will ask you to attach a Task to this Profile. You can name the Task, but it's not necessary. Just hit the checkmark to enter the Task editing screen. Once you're in, we're going to add two Actions to this Task.
A1: Plugin –> SecureTask –> Secure Settings. Action: Write. Setting: secure sysui_nav_bar_left. Value: key(88:com.android.systemui/2131230907). This is KEYCODE_MEDIA_PREVIOUS and will show up as a left arrow in your navigation bar.
A2: Plugin –> SecureTask –> Secure Settings. Action: Write. Setting: secure sysui_nav_bar_right. Value: key(87:com.android.systemui/2131231004). This is KEYCODE_MEDIA_NEXT and will show up as a right arrow in your navigation bar.
Next up, we'll create the second Profile that triggers when the music app's notification is dismissed. This Profile will get rid of the media control keys when the notification has been dismissed. Create a new Profile and name it "Disable Media Nav Keys." Again create an Event Context and select the Notification Listener plugin. This time, for the Notification Event select Removed but again select the same music app you want monitored.
Again add a Task (without a name is fine) and create the following two actions:
These two actions will clear your navigation bar keys so the media playback control keys will no longer be there.
That's it! Now when you start music playback, you'll see additional keys on your navigation bar to control media, but when you dismiss your music player's notification, these keys will disappear.
Download and Import
As with all Tasker related tutorials, we will be providing the XML files you can download and import. Download the prf.xml files from AndroidFileHost below and save them to your internal storage. Open up Tasker and long-press on the Profiles tab up top until you see an Import button. Tap on that and look for the XML files you just saved, then select them to import them (you'll have to do this one by one). Make sure you have granted Notification Access to Notification Listener enabled and have granted the WRITE_SECURE_SETTINGS permission to SecureTask as mentioned in my article, otherwise these Profiles will not do anything on your phone!
If you're wondering what else we can accomplish with SecureTask and Android O, stay tuned to the XDA Portal because we have a lot more to share. Expect more tutorials on how you can make your navigation bar in Android O accomplish many useful functions!
from xda-developers http://ift.tt/2oElDqa via IFTTT
XDA Senior Member SyCreed has put together a few notable SystemUI modifications for the OnePlus 3/3T on OxygenOS 4.1.1. Get center clock, red and dark blue accent colors, change navigation bar dpi and more with these modifications.
from xda-developers http://ift.tt/2ommHjf
via IFTTT
