samedi 23 juin 2018

Flashtool now supports Sony Xperia XZ2 and Sony Xperia XA2

flashtool sony xperia xz2 sony xperia xa2

Users who have tried modifying their Sony device in the past will have heard of XDA Recognized Developer Androxyde's Flashtool. It's an open source S1 flashing tool which supports many Sony Xperia devices. It's often used for rooting, bootloader unlocking and, of course, firmware flashing. Back in the day before recoveries were commonplace, it was also a great way to flash a custom ROM. It's often a tool users on our forums still recommend as it fulfills a number of functions that are still useful once you unlock the bootloader. Flashtool supports devices from as far back as 2009 and it's expanding to support more every year. Version 0.9.25.0 has just been released and it now supports 2018 Sony Xperia devices such as the Sony Xperia XZ2 series and the Sony Xperia XA2 series.

flashtool sony xperia xz2 sony xperia xa2

There's a number of reasons you may still want to use Flashtool. For starters, once you unlock your device's bootloader then official Sony tools no longer work. Official Sony tools only allow upgrading, whereas with Flashtool you can downgrade. Finally, Flashtool doesn't have as many restrictions on what you can and cannot flash.

The full list of features is as follows:

  • Root your phone
  • Install recovery, busybox, custom kernels
  • Clean your ROM (remove /system/apps apps of your choice) (Be careful, unless you really know what you do, do not modify the default list. This can make your phone stuck at the SE Logo)
  • Clear Dalvik cache
  • Optimize (install of JIT v2) (plugin for 2.1 phones only from 2010 line)
  • Customize (installs apps found in the custom/apps folder of the flashtool)
  • Edit any text file on the device
  • Rebrand your device

If you'd like to download the latest version of Flashtool, you can head over to their website. All of the features listed above will now work on the Sony Xperia XZ2 and the Sony Xperia XA2 along with dozens of other Xperia smartphones and tablets.


Via: XperiaBlog



from xda-developers https://ift.tt/2Il8w77
via IFTTT

CarStream (YouTube for Android Auto) updated to bypass restrictions [Root]

carstream android auto youtube

CarStream allows you to watch YouTube videos in your Android Auto-enabled car. It, along with every other custom application, was blocked from installation back in April 2018. Thus, the only way to keep using this app was to keep an older version of Google Play Services and Android Auto installed. This is not only impractical but also insecure. Fortunately, there's a workaround. The workaround was posted by the developer of the app themselves but since the steps were pretty long, a member on our forum decided to figure out if they could be simplified. XDA Senior Member noidea24 did just that and has written a tutorial that shows you how to get CarStream back up and running so long as you have a rooted Android device.

Warning: This app is not to be used by drivers for watching YouTube videos in their car. This application should only be used to entertain passengers in the car such as small kids.

Video of CarStream in action.

If you really need to get the app working again to keep your passengers occupied, then check out the guide in the thread linked below from our Google Pixel XL forum. You'll need the latest versions of Google Play Services, Android Auto app, and version 2.0 of CarStream from GitHub.

How to get CarStream (YouTube for Android Auto)



from xda-developers https://ift.tt/2ltbkWt
via IFTTT

Tasker v5.2 Brings Custom Setting Support, Immersive Mode, Runtime Permissions and More!

tasker

When one talks about device automation on Android, it is difficult to mention Tasker in that conversation. Tasker is one of the most well-known automation apps on Android, allowing determined users to achieve almost anything that they have set their minds on. Tasker recently underwent a change in ownership, coming into the hands of the very capable João Dias. Since then, Tasker has had a few Beta releases, but the developer is finally rolling out his first public Tasker release.

A few of the notable changes are highlighted below:

Custom Settings

With Custom Settings, Tasker can now control and toggle a whole bunch of settings with one simple action. The list of settings on your device varies. We've posted multiple tutorials ourselves on tweaking hidden settings values (from the Settings.System, Settings.Global, and Settings.Secure tables). So long as you grant Tasker the WRITE_SECURE_SETTINGS permission and you know what Setting you're trying to toggle, you can automate almost any setting on your device! Finding the setting to toggle within Tasker is very easy, as demonstrated in the video above. From there on, you can change that setting using any combination of triggers and scenarios as you can imagine. Check out the full tutorial on how you can utilize this new feature to change any supported setting from anywhere.

Runtime Permissions

Considering the extent of changes Tasker could make to your system, it required a whole host of permissions to run. This new release of Tasker switches over to Runtime Permissions, making it possible to only grant those permissions that are relevant to your particular use case. Tasker, like every other app, will need to target API level 26 by August so this is one step towards meeting that requirement.

Location Mode and Immersive Mode

You can now set which location mode you wish to toggle to and from (Settings.Secure.location_mode, one of HIGH_ACCURACY, BATTERY_SAVING, SENSORS_ONLY, or OFF). You can also toggle immersive mode in this new version (Settings.Global.policy_control, one of immersive.navigation, immersive.status, or immersive.all with the option to set up a list of apps that this is applied to.)

Magisk Root Detection

Root detection with Magisk is also fixed in this version.


The full changelog for the release is as follows:

Changelog

Added

  • Custom Setting action: change/read any Global, Secure or System setting via a simple UI
  • Location Mode action: set the type of location tracking on your phone (turn GPS on and off, etc)
  • Immersive Mode action: hide status bar, navigation bar or both.
  • manifest permission WRITE_SECURE_SETTINGS: enable via adb command – adb shell pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS
  • Authentication Dialog action: ask for authentication (pin, password, pattern, fingerprint or biometric).
  • action Input/Lock Screen (Android P+)
  • action Input/System Screenshot (Android P+)
  • action Sound Mode (for Samsung-like devices which have a separate sound toggle from Do Not Disturb)
  • Actions that are new or have significant changes are now highlighted until you select them or a new version of Tasker comes out
  • icon color is now respected in the various Notify actions
  • Power Mode can now be toggled
  • Stay On action now supports wireless charging
  • Toast reminding to try "New Cell API" if scanning is not working for Cell Near

Changes

  • Moved to runtime permissions (Android 6+). Will now ask for needed permissions when your Tasker data is saved (main app tick or backing out of Tasker).
  • Call Plugins via Services if possible. Will make compatible plugins faster and more reliable.
  • Ask for root when trying to add an action that requires root and cancel if it's not granted.
  • Made Torch action available for all devices running Android Marshmallow or above.
  • Made Take Call action available for all devices running Android Oreo or above.
  • Made Power Mode action work with Secure Settings permission.
  • Changed how Kill App with root works to make it more reliable
  • Notifies user when an action without the needed permissions is ran
  • Made user notifications not show in a group so they don't bundle with the persistent Tasker notification
  • Removed unnecessary log when plugin adds a replace key for unexisting key
  • Changed help pages to tasker.joaoapps.com
  • Changed warning toast to have black text
  • App now built by João Dias for the first time so I want to check if everything's working with my build script 🙂

Bugfixes

  • Fixed root detection with Magisk
  • Fixed Wifi Tether action
  • Fixed %TETHER variable
  • Now asks for permissions as soon as you start editing a state, event or action that requires special permissions
  • Fixed Tasker notification text not changing when setting the foreground option via Tasker action
  • Fixed crashes associated with missing permissions
  • Fixed Tasker crashing if changing volume with Do Not Disturb enabled and no notification access
  • Fixed crash: menu > more > developer options > save data definitions
  • Fixed launching app as a new copy
  • Fixed kill app with root
  • Fix issue with Google Play licensing

Have you tried out the new Tasker release? Let us know your use cases in the comments below!

Tasker ($2.99, Google Play) →



from xda-developers https://ift.tt/2yBqfHP
via IFTTT

Samsung Good Lock addon brings new Always on Display/Lock Screen clock designs

Samsung released a revamped version of Good Lock last week with a new addon system for UI customization. It was first released to just South Korea, but then it was expanded into the United States on Monday. Today, Samsung Good Lock has been updated with a new app called ClockFace. It works on any Samsung Galaxy smartphone running Samsung Experience 9.0 (Android 8.0 Oreo) such as the Samsung Galaxy S7, Samsung Galaxy S8, Samsung Galaxy Note 8, or Samsung Galaxy S9.

In Samsung Experience 9.0, Samsung's version of Android 8.0, Samsung added lock screen customization. It allows you to switch the design of the Always on Display and the clock on the Lock Screen. This Samsung Good Lock addon adds 29 extra clock designs.

Samsung Good Lock for Samsung Galaxy S7, Samsung Galaxy S8, Samsung Galaxy Note 8, and Samsung Galaxy S9 Samsung Good Lock for Samsung Galaxy S7, Samsung Galaxy S8, Samsung Galaxy Note 8, and Samsung Galaxy S9
  1. To use ClockFace, sideload this APK. You will also need the latest version of the Always On Display installed which can be found here.
  2. Go to Settings then select Lock screen and security.
  3. Tap the Clock and FaceWidgets option, then select Clock style.
  4. In the options, Clock style will show all of the default options. At the end of the list, you will see a new icon (pictured below).
  5. When you select that, you will be able to select one of the 29 new designs for the clock and Always on Display.
  6. Once you select an option, you have to make sure you click Apply in the top right corner, then Done to make sure it's applied.

The clock styles also allow you to change the color of the clock. The colors can be set to adaptive, which is the default and the color will change depending on the wallpaper. It also has options for static and rainbow colors.

ClockFace is a great addition to the Samsung Good Lock family. You can follow this guide for how to install the other plugins or download Good Lock 2018 from the Galaxy Apps store. ClockFace can only be accessed through the clock style settings for now, but it should be available in the Good Lock app soon. Good Lock is available for any Galaxy smartphone running Android Oreo which as we've mentioned before includes the Samsung Galaxy S9, Samsung Galaxy Note 8, Samsung Galaxy S8, and more.



from xda-developers https://ift.tt/2KeQdSG
via IFTTT

vendredi 22 juin 2018

Samsung is reportedly testing an Android Go phone in several countries

FM

Android Go is Google's answer to the ultra low-end segment of the smartphone market and so far it has produced an interesting collection of devices. This lightweight, optimized OS is ideal for emerging markets where customers are highly sensitive to how much a product like this costs. There has been a new Android Go device from a number of different OEMs, but the most popular one has yet to release such a product. That seems to have changed as Samsung is currently testing an Android Go smartphone in a number of select markets.

Details of the device are pretty scarce right now but we do know it carries the model number SM-J260G. With this information, there have been benchmarks with this model number that could give us a clue as to what type of hardware we should expect from Samsung's first Android Go smartphone. If these benchmarks are indeed true, then the phone comes with a processor codenamed Universal7570_Go, 1GB of RAM, and Android 8.1 Oreo. SamMobile ended up digging through some trademark documents which names the SM-J260G device as the Samsung Galaxy J2 Core.

As mentioned, these Android Go devices are ideal for emerging markets and Samsung knows that quite well. Samsung began testing the Galaxy J2 Core in India, Nepal, Bangladesh, and Sri Lanka, but reports now say that the company has brought it to "dozens of new markets across the globe." There are variants of this device with the SM-J260F model being tested in the United Kingdom, Uzbekistan, Caucasus Countries, Germany, Italy, Ukraine, Russia, Kazakhstan, France, and Poland.

Then a second device with the model number SM-J260M is currently being tested in Argentina, Bolivia, Chile, Colombia, Trinidad and Tobago, Peru, Panada, and Paraguay. Lastly, Samsung has brought the original SM-J260G variant to Cambodia, Thailand, Singapore, Malaysia, and Vietnam.


Source: SamMobile



from xda-developers https://ift.tt/2KhP53V
via IFTTT

Samsung Galaxy S10 Could Replace the Iris Scanner with a 3D Sensor and an In-Display Fingerprint Sensor

samsung galaxy s9 scanner, Samsung Galaxy S10 Iris Scanner

Product development takes a lot of time, especially for devices that get as complex as the smartphones in our hand. So while the Samsung Galaxy Note 9 might still be a few weeks away, Samsung is already planning forward for the Samsung Galaxy S10. And the latest reports mention the possibility of Samsung doing away with the Iris Scanner that has been present on the line since the Samsung Galaxy Note 7.

The Galaxy S10 will be the tenth iteration in the Galaxy lineup, making it an important piece of history in the making. Samsung will definitely try to make the device as special as possible by including features like triple rear cameras, a 3D sensor, a notch-less display thanks to sound emitting OLED panels, and an in-display fingerprint scanner.

The latest report from Korean site The Bell mentions that the device, however, will ditch the iris scanner because of feature redundancy. Samsung has not ordered a sample iris scanner for the Galaxy S10 prototype that is under development, and may choose to omit this part altogether in the final product. Biometric security options on the device will include the new in-display fingerprint scanner and the 3D sensor for facial recognition, so having an often-unreliable iris scanner is an extra cost which can be avoided.

The Bell also reaffirms that the S10 lineup is codenamed "Beyond." The display size of the Galaxy S10 is expected to be 5.8-inches, while the S10 Plus is expected to be 6.3-inch. It is still early days in the development cycle of the S10, so if testing of the prototype reveals issues with the in-display fingerprint scanner or the 3D sensor, Samsung could very well reverse its decisions and make changes accordingly.

What are your thoughts on Samsung choosing to skip the iris scanner on the Galaxy S10? Will this change affect your usage? Let us know in the comments below!

Source: The Bell Story Via: Android Authority



from xda-developers https://ift.tt/2lvamcs
via IFTTT

Upgraded Samsung Chromebook Plus V2 with LTE and more powerful CPU coming

Samsung Chromebook Plus V2

A recent change in Coreboot repository suggests that Samsung is joining the race to release an always-connected ChromebookThe commit shows the introduction of a new SKU of Nautilus (the codename for the Samsung Chromebook Plus V2). This variant has configuration changes that specifically mention LTE support.

Commit proving that a second Samsung device will come with LTE support

To add a bit of context – LTE-enabled Chromebooks petered out of existence over the years. Now, no Chromebooks are released with SIM card or LTE support.

Recently, the developers started working on eSIM support for Chromebooks, signaling the return of LTE Chromebooks. We expected the Snapdragon 845-powered Chromebook codename Cheza to be the first with LTE onboard, but Samsung may be looking to beat it to market.

The Samsung Chromebook Plus V2 is pretty lackluster under the hood with 4GB RAM and a low-power processor. Along with the revelation of an LTE model, there are recent code reviews mentioning a two core, four thread model (rather than the two core/two thread Celeron 3965Y announced in the Plus V2).

We can't glean any further details, or even confirm if the LTE variant is the same as the 2C/4T device. But you want a better Samsung Plus V2 (perhaps this could even be the Pro V2), keep your wallet tucked away for now.



from xda-developers https://ift.tt/2KbGQTK
via IFTTT