Enable Twitter’s Hidden Tweetstorm Feature and 280 Character Tweets with Xposed

Here at XDA, we’ve shown you how to unlock hidden functionality within applications on numerous occasions, such as with Facebook Messenger internals or Google Allo secret features. Today we’re here to share how to access more hidden features— including Twitter’s upcoming “Tweetstorm” feature! A tweetstorm is a series of tweets posted in rapid succession by the same user. Rather than planning how to separate your thoughts into different tweets, you can just post a very long tweet and the Twitter application will split the message and link them together in one thread for you. What’s more, you can also send 280 character Tweets! 280 character tweets are exactly as they sound, simply giving you the ability to send a twice as long message at one time, and no, the tweet doesn’t split into two messages!

For tweetstorms, this makes things easier for the end user and allows you to write as long of a message as you want, having them all linked together and easily read. Last month, Twitter began quietly testing this feature internally. But by using an Xposed Module, you too can enable tweetstorm functionality and 280 character tweets on your Android device!

Notice the new button in the bottom right-hand corner when posting a tweet. Tapping this allows one to add additional tweets to the tweetstorm. Once you’re done, just tap “tweet all” and Twitter will take care of the rest for you.

Before we get to installing this module, you’ll need a brief explanation of what Xposed is. The Xposed Framework is a modification to your Android device that allows applications called “modules” to inject their own code before, during, or in place of code in existing applications. In this case, the Xposed Module we will be installing—aptly called Tweeks—injects the code necessary to enable tweetstorms into the Twitter app itself.

Thanks to the recent release of Xposed Framework for Android Nougat, you can use Tweeks on any device that is running a version of Android before Android 8.0 Oreo.

Enable Tweetstorms and 280 Character Tweets on Android with Tweeks Xposed Module

This is a very simple addition but one that many users of Twitter may like. To use it, you’ll have to first install the Xposed Framework onto your device. We have a video tutorial up on that for you to follow.

Then, download the Tweeks Xposed Framework from below. In the Xposed Installer app, enable the module and then reboot your device. The only requirement is that you must be running one of the following versions of the Twitter app:

Select any of the above you want to download!

We doubt anything will happen to your account if you unlock this feature, but keep in mind that you are using unreleased features on a public social media platform. If you are willing to risk that, check it out down below!


Enable Tweetstorms in Twitter using the Tweeks Xposed Module

PSA: Google Assistant Voice Output Not Working? Here’s a Potential Fix.

The Google Assistant only started rolling out to Android 6.0+ smartphone users in March of this year, and only in select regions. We would expect Google to have worked out most of the kinks, but it appears that there may still be some lingering issues. Some users have reported to us that, on occasion, voice output from assistant is not working. Thankfully, XDA Senior Member muena90 spent hours researching the problem  and was able to fix it on his OnePlus 3T. For reference, he was running AOSPA 7.3.0 and was on the Google App version 7.12.24.21. The problem, as he discovered, came down to audio codecs.

Audio codecs are necessary for your device to decode certain audio stream types. Different sound files use different algorithms to store audio data, and audio codecs are needed to read this data. When muena90 discovered that Google Assistant was not speaking to him, he found errors in his device’s logs related to audio codecs.

He took a logcat which is simply a capture of the system logs on the device. Looking at these can be helpful no matter what you are having issues with, and it’s probably the first thing a developer will ask for if you are reporting a bug. Muena90 discovered through the logcat (shown below) that the MMParser-Extractor (related to Qualcomm processing of audio) threw an error every time the assistant’s voice was supposed to speak—such as when asking it to read the weather.

Once muena90 saw these, he did a few Google searches and found that MMParser-Extractor was related to audio codecs but found not much else. They however discovered that the mm.enable.qcom_parser build prop parameter actually houses the default audio codec that the device should use.

Originally the value it had was “2097151” which apparently is an incompatible audio codec to read the audio data sent by the Google Assistant app. Instead, they decided then to Google a recommended build prop file, taking the suggested audio codec instead and replacing their own with the new one. Taking things from random build prop files online is not usually recommended, but in this case it was probably the best solution to fix the issue.

How to Fix Google Assistant Voice Output

The next step requires you to edit the build prop file (you’ll need root access). We recommend using a simple build prop editor such as the one below. It’s simple with a nice UI and gets the job done.

BuildProp Editor (Free+, Google Play) →

Once in the build prop app, insert the value “3183219” under the “mm.enable.qcom_parser” parameter, replacing the old numeric value. Then, reboot your phone.

So what’s happening with the Google Assistant?

Presumably the number under the “mm.enable.qcom_parser” is referencing a specific audio codec set built into Android. This seems to be the default audio codec for a lot of applications, and the Google Assistant does not expect to use it. Simply downloading and analyzing a recommended build prop was the right answer here as the user was on a custom ROM which did not seem to have a common configuration as regards audio codecs.

It is noteworthy however that the Google Assistant seems to be the only affected application by this codec. Changing the number seems to change the actual range of supported codecs on the device, allowing the Google Assistant to output audio correctly.

When running into issues like these, sometimes a simple logcat is enough to find the problem without the hours of Googling that also were required for this job. If you ever run into the issue, simply changing your build prop file may be enough to fix it and be on your way.

How to Enable Google Photos Unlimited Storage and Pixel-Exclusive Wallpapers on Any Phone

One of the greatest and most useful exclusive features of the Google Pixel line, among many, is proper unlimited storage for Google Photos. This feature allows you to back up all your existing pictures and videos in original quality to Google Photos, without having them count up against your existing Google Drive storage. However, this feature is limited to the Pixel, Pixel XL, Pixel 2, Pixel 2 XL, and the Moto X4 Android One edition. If you’re rooted, though, there’s a small workaround discovered by XDA Member emime12 that will allow you to get Google Photos unlimited storage as well as exclusive wallpaper categories on the Google Wallpapers application on any Android phone running Android Nougat or higher.


Enable Unlimited Google Photos Storage & Pixel Exclusive Wallpapers on Any Android Phone

In case we haven’t made it clear before, you’re going to need root access in order to continue with the tutorial, so make sure that your phone is properly rooted before continuing. Then, follow these steps:

  1. Download nexus.xml to your phone.
  2. Open your root file manager of choice (we’ve used Solid Explorer here, but you can use pretty much any root file explorer here such as MiXplorer)
  3. Copy the nexus.xml file you just downloaded and paste it in /system/etc/sysconfig.
  4. Afterwards, set the file permissions to 644 (rw-r–r–).
  5. Reboot your phone.
  6. Once booted up, go to the Settings page for Google Photos and wipe Google Photos’ app data. You’re done!

Photos will now think that you’re using a Pixel, and as such, you should be greeted by a dialog saying that you’re now able to use unlimited storage on your Google Pixel device. Also, you should now have access to more wallpaper categories on the Google Wallpapers app, as well as access to the default Pixel 2 wallpaper on the Urbane category.

Optional Build.Prop Edits if Necessary

Just placing the file in the sysconfig directory should be enough for most devices. If, however, placing the above file didn’t work for you, you will have to get your hands even dirtier. Download BuildProp Editor and then find and change/set the following build.prop values:

ro.product.model=Pixel 2 XL
ro.product.brand=Google
ro.product.manufacturer=Google
ro.opa.eligible_device=true

BuildProp Editor (Free+, Google Play) →


Explanation

Instead of the usual (and easily copyable on other devices) approach of a simple build.prop flag, eligibility for some Pixel-exclusive services and features (like unlimited Google Photos storage) is defined in the nexus.xml file, included by default in all Google Pixel phones in the system/etc/sysconfig directory. The system partition is readable without root, meaning that all apps can easily check for a value in said system partition. And some Google apps, like Google Photos and Google Wallpapers, check for specific flags in the nexus.xml file in order to provide specific features to Pixel users. However, as long as your phone has this particular file, these apps will believe that the user is using a Google Pixel, and will, therefore, enable these exclusive features on your phone. So simply inserting it to the system partition using root access and a root file manager will do the trick.

So far, we have tested this on a Moto G 2015 running an unofficial Android 8.0 Oreo ROM, and we can confirm that it works. However, it’s sure to work on most Android Nougat devices. And while we cannot guarantee that it works on Marshmallow or lower, it’s possible since the app only seems to be checking for specific flags in the nexus.xml file instead of system-related values.

It’s highly possible Google will patch this in the short term – after all, it’s not the first time we find shortcuts we aren’t supposed to find. So, we encourage you to test this out and give us feedback in the comment section. And be sure to check the original tutorial, originally made for the Xiaomi Redmi Note 3, if this worked for you!

How to Increase the Edge Screen Size on Samsung Galaxy Phones Without Root

While the Edge Screen function on the Samsung Galaxy S6 Edge, S7 Edge, S8, S8+, and Note 8 provides a useful way to to access your favorite apps, tasks, and more, it can be a pain to activate especially since the newer phones are so tall! The size (and recognition area) can be tweaked in Settings, however, the maximum size you can set there is not enough for some users. If you feel like the edge handle is too small on your phone, you can easily change it to a custom value without root or much effort required, thanks to a tutorial originally made by XDA Senior Member Pedroc1999.

It was originally tested on the Samsung Galaxy S8+, however, we have also confirmed that this works on the new Samsung Galaxy Note 8 as well. It should also work on custom TouchWiz-based ROMs with edge features enabled.


Increasing the Edge Screen Handle Size on Samsung Phones (ADB)

For this tutorial, as always, you’re going to need to properly set up the Android Debug Bridge in your phone and your computer. Luckily, we’ve previously done a tutorial on how to set up ADB. Be sure to check that out before continuing, as it includes complete instructions on setting things up on Windows, Linux and macOS computers.

Once you’ve set up ADB on your computer, then, you’ll need to open a command prompt/terminal and enter the following command:

adb shell

Finally, to change the edge screen handle size to your liking, use the following command:

settings put global edge_handle_size_percent insertvaluehere

where you change “insertvaluehere” for a custom value. In this case, we want the handle to fill up the whole edge of the screen, so we’re changing that to”100.00″.

settings put global edge_handle_size_percent 100.00

The handle size is still the default, though, so in order to make this setting stick just go into the edge screen handle settings. You’ll find that the edge screen handle size has now become full-size. You’re good to go!

Increasing the Edge Screen Handle Size on Samsung Phones (Terminal + Root)

If you don’t have a computer handy, or you simply don’t feel like setting up ADB or using a computer, you can do it straight from the actual phone—only if your phone is rooted. You will need to download a terminal app like Termux beforehand and give it root permissions, so be sure to download it from the Play Store before starting.

Termux (Free, Google Play) →

Afterwards, fire up your terminal app of choice and give it root permissions using:

su

Since you’re already in the Android shell, you can simply change the handle size using:

settings put global edge_handle_size_percent insertvaluehere

again, changing “insertvaluehere” for your value of choice. Go to the handle settings to find and set your custom size.


Explanation

You can actually tweak the screen handle size in Settings, with a slider that goes small/mid/large, however, some found it to be really small even at the largest setting, which could be quite annoying given how tall the newest Samsung flagship phones are. Digging through the Settings.Global database you will be able to find the “edge_handle_size_percent” setting, which can be easily tweaked using the device’s shell interface.

While this tutorial was originally tested on the Samsung Galaxy S8+, as we said at the beginning of the article, we have also confirmed that this tutorial works on the Samsung Galaxy Note 8, and it will probably also work on both the Galaxy S7 edge and the S6 edge as they both have edged screens and, therefore, edge features. This will not work on flat-screened Samsung phones that don’t have this edge screen feature. If, however, you’re running a custom ROM which enables edge features on your flat-screened Samsung phone, you will probably be able to take advantage of this tweak as well.

Here’s How to Enable Google Lens in Google Assistant on Any Device [Root]

This week, Google announced the long-awaited second generation Pixel smartphones—the Google Pixel 2 and the Google Pixel 2 XL. As with any new smartphone, there are often new features that are exclusive to that device (at least for the time being). One such feature is Google Lens which is said to launch in a preview state on the Pixel 2 and Pixel 2 XL. Google Lens is a set of vision based computing capabilities that analyzes what you are looking at—think of it as the successor to Google Goggles.

Initially announced at Google I/O 2017, the feature was promised to eventually be integrated with two other Google products: Google Assistant and Google Photos. Despite launching in an exclusive preview state on the new Pixel phones, it has been discovered that Google Lens integration in Google Assistant can be enabled right now on any rooted Android device.

It wasn’t long ago that we discovered that Google Lens integration was fully functional in Google Photos, although Google quickly patched the method we were using when we shared an easy way to access Google Lens.

Google Lens Launcher for Google Photos Google Lens Launcher for Google Photos Google Lens Launcher for Google Photos

But a new method has been discovered by XDA Senior Member ani_me_sh which allows for rooted devices to enable Google Lens in Google Assistant. The method is similar to a previous trick used last year to enable Google Assistant on non-Google devices. We’ll walk you through in a step-by-step tutorial how to enable Google Lens integration with Google Assistant.

Enable Google Lens in Google Assistant Enable Google Lens in Google Assistant Enable Google Lens in Google Assistant

Tutorial – How to Enable Google Lens in Google Assistant

Before we begin, you’ll need to have a rooted device using either SuperSU or Magisk. Then, you will need either a rooted file explorer such as MiXplorer from our forums. Alternatively, you can download BuildProp Editor from the Play Store.

BuildProp Editor (Free+, Google Play) →

Then, follow these steps to enable Google Lens:

  1. Install the latest Google App (version 7.13.21 beta)
  2. Open up BuildProp Editor and tap on the pencil icon in the top right. This will let you edit the build.prop file in /system.
  3. Find (or add if it’s not there) ro.product.manufacturer and change whatever is there to equal ‘Google
  4. Find (or add if it’s not there) ro.product.model and change it to ‘Pixel 2 XL
  5. Finally, add the following line anywhere: ro.opa.eligible_device=true
  6. Tap the save button to save all of your changes
  7. Reboot your phone
  8. Open up Google Assistant by pressing the home button, and you should now see the Google Lens button in the bottom right (as shown in the earlier screenshots!)
Enable Google Lens in Google Assistant Enable Google Lens in Google Assistant Enable Google Lens in Google Assistant Enable Google Lens in Google Assistant

Basically, you are tricking the Google App into thinking your device is actually a Google Pixel 2 XL. It appears that the Google App reads these system property values to determine what device it is running on, and enables Google Lens if it returns the Pixel 2 XL.

We don’t expect this workaround to work forever considering how quickly Google shut down the prior method, so if you want to try out Lens right now we recommend you play around with it as soon as you can! I tested it briefly on my OnePlus 5 running the latest OxygenOS, and can confirm it does work.

What can Google Lens do?

As a reminder, here’s what Lens should be able to do according to an APK teardown of Google Photos that we did earlier.

Can identify:

  • Artwork
  • Barcodes
  • Books
  • Buildings
  • Landmarks
  • Media covers
  • Movies
  • Music albums
  • Paintings
  • Places
  • Points of Interest
  • Statues
  • Video games

Can perform:

  • Add contacts from a business card
  • Language translation
  • Look up product information
  • Open web addresses in your browser
  • Plant and animal identification
  • Save dates to your calendar from a poster

We presume that Google will add more features as time passes considering the fact that Google Lens is an avenue for Google to show off their machine learning technology. We just hope that they don’t make this feature a Pixel 2 exclusive for too much longer. For now, this unofficial workaround is the best chance you’ll get at trying out Google Lens!